Skip to content

ci: improve the release workflows after the 2.23.6 release - #2812

Merged
tonyandrewmeyer merged 4 commits into
canonical:mainfrom
tonyandrewmeyer:release-feedback-2-23-6
Oct 19, 2026
Merged

tonyandrewmeyer merged 4 commits into
canonical:mainfrom
tonyandrewmeyer:release-feedback-2-23-6

Conversation

@tonyandrewmeyer

@tonyandrewmeyer tonyandrewmeyer commented Oct 9, 2026 •

Copy link
Copy Markdown
Collaborator

Changes to the release workflows from what came up in the 2.23.6 release.

  • The version-bump pull request opens as a draft, so whoever ran the workflow can resolve the Unsure notes before asking for a review. Its description now lists the next steps, with its own number ready for Create the draft release.
  • On a maintenance branch, the changelog lists the fixes a squash-merged batch of cherry-picks brought in, as we did by hand on chore: update changelog and versions for 2.23.6 release #2809. The release-notes model is also told the newest release, so it can say which series the fixes came from.
  • GitHub ticks "Set as the latest release" on every draft, whatever the draft was created with, and the 2.23.6 draft came up with it ticked. The pull request and the draft summary now say to untick it for a maintenance release.
  • The release tools are pinned to feat: list backported fixes and improve maintenance release notes charm-tech-code#17, which adds the backport listing and the maintenance-release guidance in the notes prompt.

tonyandrewmeyer and others added 2 commits October 9, 2026 20:49
* The version-bump pull request opens as a draft, so whoever ran the workflow can resolve the Unsure notes before asking for a review. Its description now lists the next steps, with its own number ready for Create the draft release.
* On a maintenance branch, the changelog lists the fixes a squash-merged batch of cherry-picks brought in, as we did by hand on canonical#2809. The release-notes model is also told the newest release, so it can say which series the fixes came from.
* GitHub ticks "Set as the latest release" on every draft, whatever the draft was created with, and the 2.23.6 draft came up with it ticked. The pull request and the draft summary now say to untick it for a maintenance release.
* The release tools are pinned to canonical/charm-tech-code#17, which adds the backport listing and the maintenance-release guidance in the notes prompt.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@tonyandrewmeyer
tonyandrewmeyer marked this pull request as ready for review October 9, 2026 07:54
tonyandrewmeyer added a commit to tonyandrewmeyer/charmlint that referenced this pull request Oct 9, 2026
Port canonical/operator#2812, apart from the parts for maintenance
branches: the version-bump PR opens as a draft, its description lists the
next steps with its own number filled in, and the release tools are pinned
to canonical/charm-tech-code#17, which improves the release-notes prompt.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
tonyandrewmeyer and others added 2 commits October 15, 2026 14:09
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Get the checks running before asking for a review, sort pull request
numbers as numbers, only read the subjects on a maintenance branch, leave
a usable body if the number substitution fails, and drop a placeholder-
free f-string.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
@tonyandrewmeyer
tonyandrewmeyer merged commit 7064ccd into canonical:main Oct 19, 2026
60 checks passed
@tonyandrewmeyer
tonyandrewmeyer deleted the release-feedback-2-23-6 branch October 19, 2026 23:12
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.

3 participants