Docs: add release workflow guide for dbcss #3

Closed
opened 2026-06-23 16:46:20 +00:00 by mik-tf · 1 comment
Owner

Context

The 0.5.4 release proved the full Forge-primary and GitHub-mirror flow:

  • bump crate version
  • update changelog
  • run local release checks
  • push development to Forge primary and GitHub mirror
  • tag release
  • Forge publishes crates.io
  • GitHub creates mirror release and rebuilds Pages

This should be captured in the repo so future releases follow the same path.

Acceptance criteria

  • Add a concise release guide under docs/.
  • Include the exact high-level sequence for branch push, tag push, Forge publish workflow, GitHub mirror release, and Pages verification.
  • Include verification commands/checkpoints, but no credentials, secrets, or machine-local details.
  • Link the release guide from README or docs index where it is easy to find.

Signed-by: mik-tf mik-tf@noreply.invalid

## Context The 0.5.4 release proved the full Forge-primary and GitHub-mirror flow: - bump crate version - update changelog - run local release checks - push `development` to Forge primary and GitHub mirror - tag release - Forge publishes crates.io - GitHub creates mirror release and rebuilds Pages This should be captured in the repo so future releases follow the same path. ## Acceptance criteria - Add a concise release guide under `docs/`. - Include the exact high-level sequence for branch push, tag push, Forge publish workflow, GitHub mirror release, and Pages verification. - Include verification commands/checkpoints, but no credentials, secrets, or machine-local details. - Link the release guide from README or docs index where it is easy to find. Signed-by: mik-tf <mik-tf@noreply.invalid>
Author
Owner

Implemented in c07af87: added docs/RELEASE.md and linked it from the README. The guide documents the public Forge-primary/GitHub-mirror release flow, release checks, tag flow, and post-release verification without credentials or private operational details.

Forge CI run 13 is green.

Signed-by: mik-tf mik-tf@noreply.invalid

Implemented in `c07af87`: added `docs/RELEASE.md` and linked it from the README. The guide documents the public Forge-primary/GitHub-mirror release flow, release checks, tag flow, and post-release verification without credentials or private operational details. Forge CI run 13 is green. Signed-by: mik-tf <mik-tf@noreply.invalid>
Sign in to join this conversation.
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
lhumina_code/dioxus-bootstrap-css#3
No description provided.