censor/Censor
1
37
Fork
You've already forked Censor
3

chore: release workflow #29

Closed
opened 2025年12月03日 20:22:11 +01:00 by mahlzahn · 0 comments

Current steps for semi-automated release publication

1. Manual release notes drafting

During preparation, while merging PRs, etc.:

  • manually create milestone vX.Y.Z.
  • manually assign milestone to merged PRs, optionally also to solved and blocking issues
  • draft release notes in milestone description with up to four bullets, preferably in imperative form

2. Automatic release preparation

On workflow_dispatch with milestone ID or version number:

  • extract release version, title, and description from milestone
  • create release preparation pull request with changes to
    • meson.build: update version
    • Appstream metadata: add release information
    • edit path of screenshot(s) pointing to the tag
  • create draft release in releases tab with
    • additional bullet point
      - See [this milestone](link) for associated pull requests and issues and [this tag](link) for included commits
      

3. Publish release (manually)

  • check that edited files and draft release look good (check all checkboxes in PR)
  • merge PR
  • make draft release public
  • manually add flatpak package to release

TODO

  • create PR on flathub repository pointing to latest commit
    • this will build the flatpak bundles on Github
    • update after push to the release preparation PR
    • update after final release/tag creation
    • manually approve/merge flathub PR
  • add the flathub PR link to the release preparation PR
  • add the flathub link to the release draft
  • automate steps after merge of the PR
  • fix markdown parsing using pre-installed markdown_py
## Current steps for semi-automated release publication ### 1. Manual release notes drafting During preparation, while merging PRs, etc.: - manually create milestone vX.Y.Z. - manually assign milestone to merged PRs, optionally also to solved and blocking issues - draft release notes in milestone description with up to four bullets, preferably in imperative form ### 2. Automatic release preparation On `workflow_dispatch` with milestone ID or version number: - [x] extract release version, title, and description from milestone - [x] create release preparation pull request with changes to - [x] meson.build: update version - [x] Appstream metadata: add release information - [x] edit path of screenshot(s) pointing to the tag - [x] create draft release in releases tab with - [x] additional bullet point ``` - See [this milestone](link) for associated pull requests and issues and [this tag](link) for included commits ``` ### 3. Publish release (manually) - [x] check that edited files and draft release look good (check all checkboxes in PR) - [x] merge PR - [x] make draft release public - [x] manually add flatpak package to release ### TODO - [ ] create PR on flathub repository pointing to latest commit - this will build the flatpak bundles on Github - [x] update after push to the release preparation PR - [x] update after final release/tag creation - manually approve/merge flathub PR - [x] add the flathub PR link to the release preparation PR - [x] add the flathub link to the release draft - [x] automate steps after merge of the PR - [x] fix markdown parsing using pre-installed markdown_py
Sign in to join this conversation.
No Branch/Tag specified
main
v0.7.3
v0.7.2
v0.7.1
v0.7.0
v0.6.0
v0.5.0
v0.4.0
v0.3.0
v0.2.0
v0.1.0
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
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
censor/Censor#29
Reference in a new issue
censor/Censor
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?