Skip to content

Improve start release#4800

Open
Saviq wants to merge 11 commits intoactions-security-reviewfrom
improve-start-release
Open

Improve start release#4800
Saviq wants to merge 11 commits intoactions-security-reviewfrom
improve-start-release

Conversation

@Saviq
Copy link
Copy Markdown
Contributor

@Saviq Saviq commented Mar 26, 2026

What's new?

This makes for a streamlined release process, where "Start release":

  1. updates all the changelogs for the coming release
  2. tags the RC commit
  3. (if the source is main) open a PR
  4. (if the source is main's tip) bump the development version

And "Finalize release":

  1. updates the changelogs with release notes
  2. tags the release
  3. publishes the GitHub release

How to test

Check out the runs in my repo:

  1. 2.27.0
  2. 2.27.1 into the existing release/2.27

Notice the nicely looking releases, all signed and green at:

https://github.com/Saviq/mir/releases

NB: bugfix release for a merged release/X.YY branch is not supported (yet).

Checklist

  • Tests added and pass
  • Adequate documentation added
  • (optional) Added Screenshots or videos

@Saviq Saviq requested a review from a team as a code owner March 26, 2026 15:22
Comment on lines +35 to 51
## Mir 2.27.0~dev

- New upstream release 2.27.0

- ABI summary:

- miral ABI unchanged at 7
- mircommon ABI unchanged at 12
- mircore ABI unchanged at 2
- miroil ABI unchanged at 8
- mirplatform ABI unchanged at 34
- mirserver ABI unchanged at 67
- mirwayland ABI unchanged at 5
- mirplatformgraphics ABI unchanged at 23
- mirinputplatform ABI unchanged at 10

## Mir 2.25.2
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Did 2.26 disappear?

Copy link
Copy Markdown
Contributor Author

@Saviq Saviq Mar 26, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The ~dev one did, it will come back when we merge tha final release in.

We can only really have a single ~dev at a time, so didn't make sense to leave it, and it wouldn't actually help with conflicts.

Copy link
Copy Markdown
Contributor

@AlanGriffiths AlanGriffiths left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks reasonable

@Saviq
Copy link
Copy Markdown
Contributor Author

Saviq commented Mar 26, 2026

Looks reasonable

NB: this comes after #4782

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants