Everything still says 0.1.0 - package.json, nobilis/Cargo.toml - and PKGBUILD's pkgver is r1.<sha>. The only published build is the rolling latest release, named after a commit.
For 1.0:
1.0.0 in package.json and Cargo.toml, and a PKGBUILD that reports it.
The version, and the commit, visible in the app (Settings), so a bug report can say what it was filed against.
A tagged v1.0.0 release with its own notes, beside latest rather than replacing it - the rolling workflow keeps going; this is a second trigger on tags.
Gitea's release kept in step, or retired in favour of GitHub's - decide which.
Everything still says 0.1.0 - package.json, nobilis/Cargo.toml - and PKGBUILD's pkgver is `r1.<sha>`. The only published build is the rolling `latest` release, named after a commit.
For 1.0:
- 1.0.0 in package.json and Cargo.toml, and a PKGBUILD that reports it.
- The version, and the commit, visible in the app (Settings), so a bug report can say what it was filed against.
- A tagged `v1.0.0` release with its own notes, beside `latest` rather than replacing it - the rolling workflow keeps going; this is a second trigger on tags.
- Gitea's release kept in step, or retired in favour of GitHub's - decide which.
Salastil
added this to the v1.0 milestone 2026-10-01 23:59:57 -04:00
Progress, 4 October. The mechanics are done; the decisions are yours.
Done
Settings › About already shows moho's and nobilis's version, commit and build date. Nothing was needed there.
A pushed v* tag now publishes a release of its own beside latest. Its files are named after the version (moho-1.0.0.AppImage, .deb, .exe), it has its own notes, and it's published as GitHub's "latest" once its files are attached. The rolling release carries on as before for branch pushes.
The build fails at the start if the tag isn't v + package.json's version.
PKGBUILD's pkgver now leads with the version (0.1.0.r493.5a8d7f7), which sorts above the old r… form, so existing installs upgrade.
When to bump to 1.0.0: package.json and nobilis/Cargo.toml, then tag v1.0.0 on master and push the tag to GitHub.
Whether the Gitea release stays, kept in step by hand, or is retired in favour of GitHub's.
master keeps its own PKGBUILD through merges, so the pkgver change needs copying across by hand at the next merge.
After the first versioned release, the rolling job's "date the release to now" step may make latest GitHub's "Latest" again. If that matters, pass make_latest=false there.
Progress, 4 October. The mechanics are done; the decisions are yours.
**Done**
- Settings › About already shows moho's and nobilis's version, commit and build date. Nothing was needed there.
- A pushed `v*` tag now publishes a release of its own beside `latest`. Its files are named after the version (`moho-1.0.0.AppImage`, `.deb`, `.exe`), it has its own notes, and it's published as GitHub's "latest" once its files are attached. The rolling release carries on as before for branch pushes.
- The build fails at the start if the tag isn't `v` + package.json's version.
- PKGBUILD's pkgver now leads with the version (`0.1.0.r493.5a8d7f7`), which sorts above the old `r…` form, so existing installs upgrade.
https://git.salastil.com/Salastil/moho/commit/a0e9445
**Your decisions**
- When to bump to 1.0.0: package.json and nobilis/Cargo.toml, then tag `v1.0.0` on master and push the tag to GitHub.
- Whether the Gitea release stays, kept in step by hand, or is retired in favour of GitHub's.
- master keeps its own PKGBUILD through merges, so the pkgver change needs copying across by hand at the next merge.
- After the first versioned release, the rolling job's "date the release to now" step may make `latest` GitHub's "Latest" again. If that matters, pass `make_latest=false` there.
Progress, 4 October. The release process is now built to the decisions made today.
Done (on development)
The rolling "Latest build" is retired. release.yml (renamed from rolling-release.yml) still builds and tests every push to master, but publishes only for v* tags. -rc.N tags publish as pre-releases.
The release page is the version's section of CHANGELOG.md: major features first, then fixes, patches and changes, one line each linked to its commit, then the downloads. A version with no section isn't published.
CHANGELOG.md has a drafted ## [1.0.0] section with the major features, and the fixes since the first public build (55 commit links, all checked).
scripts/changelog-deps.mjs lists direct dependency updates between two releases, each linked to its commit.
scripts/mirror-release.sh, run by hand, copies the GitHub release to Gitea and makes nobilis's release on both hosts with its daemon binaries.
A newer moho appears at the top of the mentions inbox until it's dismissed. It's checked through the daemon, so it follows Tor and proxy settings, and Settings › General › Updates turns it off.
README: versioning scheme, and downloads from the latest release.
Remove the old "Latest build" release and latest tag on GitHub. Waiting for confirmation, since it's a public removal.
Merge to master, then rehearse with v1.0.0-rc.1, which also gives the mirror script its first real run.
1.0.0 itself, after the remaining v1.0 issues (#249, #222, #181) are confirmed.
Progress, 4 October. The release process is now built to the decisions made today.
**Done (on development)**
- The rolling "Latest build" is retired. `release.yml` (renamed from `rolling-release.yml`) still builds and tests every push to master, but publishes only for `v*` tags. `-rc.N` tags publish as pre-releases.
- The release page is the version's section of `CHANGELOG.md`: major features first, then fixes, patches and changes, one line each linked to its commit, then the downloads. A version with no section isn't published.
- `CHANGELOG.md` has a drafted `## [1.0.0]` section with the major features, and the fixes since the first public build (55 commit links, all checked).
- `scripts/changelog-deps.mjs` lists direct dependency updates between two releases, each linked to its commit.
- `scripts/mirror-release.sh`, run by hand, copies the GitHub release to Gitea and makes nobilis's release on both hosts with its daemon binaries.
- A newer moho appears at the top of the mentions inbox until it's dismissed. It's checked through the daemon, so it follows Tor and proxy settings, and Settings › General › Updates turns it off.
- README: versioning scheme, and downloads from the latest release.
- moho: https://git.salastil.com/Salastil/moho/commit/d9a9d0c
- nobilis: https://git.salastil.com/Salastil/nobilis/commit/b697fbb
**Next**
- Remove the old "Latest build" release and `latest` tag on GitHub. Waiting for confirmation, since it's a public removal.
- Merge to master, then rehearse with `v1.0.0-rc.1`, which also gives the mirror script its first real run.
- 1.0.0 itself, after the remaining v1.0 issues (#249, #222, #181) are confirmed.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Everything still says 0.1.0 - package.json, nobilis/Cargo.toml - and PKGBUILD's pkgver is
r1.<sha>. The only published build is the rollinglatestrelease, named after a commit.For 1.0:
v1.0.0release with its own notes, besidelatestrather than replacing it - the rolling workflow keeps going; this is a second trigger on tags.Progress, 4 October. The mechanics are done; the decisions are yours.
Done
v*tag now publishes a release of its own besidelatest. Its files are named after the version (moho-1.0.0.AppImage,.deb,.exe), it has its own notes, and it's published as GitHub's "latest" once its files are attached. The rolling release carries on as before for branch pushes.v+ package.json's version.0.1.0.r493.5a8d7f7), which sorts above the oldr…form, so existing installs upgrade.https://git.salastil.com/Salastil/moho/commit/a0e9445
Your decisions
v1.0.0on master and push the tag to GitHub.latestGitHub's "Latest" again. If that matters, passmake_latest=falsethere.Progress, 4 October. The release process is now built to the decisions made today.
Done (on development)
The rolling "Latest build" is retired.
release.yml(renamed fromrolling-release.yml) still builds and tests every push to master, but publishes only forv*tags.-rc.Ntags publish as pre-releases.The release page is the version's section of
CHANGELOG.md: major features first, then fixes, patches and changes, one line each linked to its commit, then the downloads. A version with no section isn't published.CHANGELOG.mdhas a drafted## [1.0.0]section with the major features, and the fixes since the first public build (55 commit links, all checked).scripts/changelog-deps.mjslists direct dependency updates between two releases, each linked to its commit.scripts/mirror-release.sh, run by hand, copies the GitHub release to Gitea and makes nobilis's release on both hosts with its daemon binaries.A newer moho appears at the top of the mentions inbox until it's dismissed. It's checked through the daemon, so it follows Tor and proxy settings, and Settings › General › Updates turns it off.
README: versioning scheme, and downloads from the latest release.
moho: https://git.salastil.com/Salastil/moho/commit/d9a9d0c
nobilis: https://git.salastil.com/Salastil/nobilis/commit/b697fbb
Next
latesttag on GitHub. Waiting for confirmation, since it's a public removal.v1.0.0-rc.1, which also gives the mirror script its first real run.