fm1-build
What the badge means: the file you install is exactly the one GitHub built from that commit, and anyone can check it. What it does not mean: that the firmware is safe.
- Custom firmware
- Stable
- Low brick risk
This project hasn't been claimed by its maintainer yet, so its details come from the community. Is it yours? Claim it
Before you start
- How hard is it?
- EasyWith Slipway.
- What you need
- Comfort with the command line
- A computer
- Can it break my device?
- Very unlikely to break anything.
- Can I undo it?
- The project doesn't say. Assume you can't.
Did it work for you?
Did fm1-build work on your M-VAVE FM-1?
No reports yet.
One-tap reports from owners. Bricked reports are checked before they count.
Compatibility
Devices: M-VAVE FM-1.
No compatibility information yet.
Getting started
From the project's README ("Use it"):
In your firmware repository, add .github/workflows/release.yml:
name: release on: push: tags: ['v'] jobs: build: uses: zvenson/fm1-build/.github/workflows/build.yml@v1 permissions: contents: write id-token: write attestations: write …
Push a tag (e.g. v1.2): GitHub builds, attests and releases the packages. The hub picks the release up and shows the badge on your firmware's card. Verify a package yourself with the GitHub CLI:
gh attestation verify your-firmware.fwsc --repo <owner>/<repo>
--signer-workflow zvenson/fm1-build/.github/workflows/build.yml
Risk and recovery
- Brick risk
- Low
- Requires opening the device
- No
Credits, license and support
- License
- MIT