Repository navigation
Backfill release tags for 0.1.0 to 0.5.0 and replace the duplicated release checklist with a pointer #9
Description
Background
torrust-server-lib 0.6.0 was published manually and tagged v0.6.0 on the published commit. Releases 0.1.0 to 0.5.0 have no tags. Separately, docs/release_process.md still ends with a three-step checklist (version-bump PR, publish, signed tag) that repeats the steps of the source of truth, now Releasing Workspace Packages in the Torrust Tracker (torrust/torrust-tracker#2808). The old anchor docs/release_process.md#publishing-a-workspace-package keeps working there, because the index document redirects to the new document.
1. Backfill signed tags v<semver> (the maintainer pushes the tags)
Each published crate records the commit it was built from in .cargo_vcs_info.json. The table below comes from downloading each .crate from static.crates.io and reading that file; each commit exists on main.
| Version | Published commit (.cargo_vcs_info.json) |
Commit date | Subject |
|---|---|---|---|
| 0.1.0 | b87f6fa927ff1d7bb23d906a8011a2da451fcb41 |
2026-06-19 | chore: fix CI - add yamllint config, fix TOML formatting, add CI badge |
| 0.2.0 | d17fdb1989cfe8dda989c63950920ce767b55191 |
2026-07-31 | feat(registry)!: add runtime service metadata |
| 0.3.0 | 2b3f8ec6e20a81fcd0c25dcc1c4e3a29fe4fea17 |
2026-09-16 | Merge pull request #1 from torrust/2234-token-aware-shutdown-wait |
| 0.4.0 | f3690ed2cac700870c4825fdf63a102d9029fc51 |
2026-10-26 | feat(registry): add Registar::deregister |
| 0.5.0 | 0ad8ca094d2a32d111c7c21c57bfb8d3b15ebfa5 |
2026-11-06 | Merge #4: feat(signals): deprecate legacy shutdown API |
v0.6.0 already points to 2dd04f494722b126b1dba8a65006cb4dfa335384, which matches the commit recorded in the 0.6.0 crate.
Note: the earlier guess from commit history (the commit that bumped version) was wrong for 0.3.0 and 0.5.0, where the published commit is the merge commit, and ambiguous for 0.1.0 (86e233a or b87f6fa). Use the table above.
Tag command, per version (signed, on the published commit):
git tag --sign v<semver> <published-commit>
git push <upstream-remote> refs/tags/v<semver>2. Replace the duplicated checklist
In docs/release_process.md, delete the "Checklist" section and keep the pointer plus the differences (no develop branch, no workflow, tag v<semver>), as the "Pointing to This Process from Package Documentation" section of Releasing Workspace Packages prescribes.
Acceptance criteria
- Signed tags
v0.1.0tov0.5.0exist, each on the published commit in the table. -
docs/release_process.mdhas no copy of the release steps.
Activity
Merge #2837: docs(issues): [#2808] correct the torrust-server-lib bac…
Merge #10: docs: replace the release checklist with the pointer to th…
josecelano-bot commentedon Nov 13, 2026
Done: signed tags
v0.1.0tov0.5.0were pushed on the published commits listed above (verified upstream), and #10 replaced the duplicated checklist indocs/release_process.mdwith the pointer to the Tracker process. Two non-blocking review comments on #10 (link the section directly; mention raising dependents'versionrequirements) were deliberately not followed up.