Skip to content

fix finish_release.py on the 5.2.x point release branch - #10507

Merged
bmw merged 1 commit into
5.2.xfrom
5.2.x-finish-release
Dec 8, 2025
Merged

bmw merged 1 commit into
5.2.xfrom
5.2.x-finish-release

Conversation

@bmw

@bmw bmw commented Dec 8, 2025

Copy link
Copy Markdown
Member

this PR just cherry picks #10503 to the 5.2.x branch in case we need to do a point release to fix #10506 or any other issues

in canonical/snapcraft#5720, snapcraft made a
change. `snapcraft status certbot` output changed from something like
this:
```
Track    Arch    Channel    Version     Revision    Progress
latest   amd64   stable     5.1.0       5057        -
                 candidate  ↑           ↑           -
                 beta       5.2.1       5214        -
                 edge       5.2.0.dev0  5210        -
         arm64   stable     5.1.0       5058        -
                 candidate  ↑           ↑           -
                 beta       5.2.1       5215        -
                 edge       5.2.0.dev0  5211        -
         armhf   stable     5.1.0       5056        -
                 candidate  ↑           ↑           -
                 beta       5.2.1       5213        -
                 edge       5.2.0.dev0  5212        -
```
to this:
```
Track    Arch    Channel    Version     Revision    Progress
latest   amd64   stable     5.1.0       5057        -
latest   amd64   candidate  ↑           ↑           -
latest   amd64   beta       5.2.1       5214        -
latest   amd64   edge       5.2.0.dev0  5210        -
latest   arm64   stable     5.1.0       5058        -
latest   arm64   candidate  ↑           ↑           -
latest   arm64   beta       5.2.1       5215        -
latest   arm64   edge       5.2.0.dev0  5211        -
latest   armhf   stable     5.1.0       5056        -
latest   armhf   candidate  ↑           ↑           -
latest   armhf   beta       5.2.1       5213        -
latest   armhf   edge       5.2.0.dev0  5212        -
```
when its output is captured like it is in finish_release.py in the lines
above the code i'm modifying here

not matching on the beginning of lines makes this pattern a little less
strict, but based on the rest of the pattern and the output here, i
personally think this is fine

after carefully verifying this works with the current state of things, i
went ahead and finished the release with this change and it worked just
fine. instead, this PR proposes a way to fix things going forward

(cherry picked from commit 9e7a98f)
@bmw
bmw requested review from a team and ohemorange and removed request for a team December 8, 2025 16:45

@ohemorange ohemorange left a comment

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.

I don't think this needs a second review

@bmw

bmw commented Dec 8, 2025

Copy link
Copy Markdown
Member Author

samesies. merging now

@bmw
bmw merged commit d3c30cf into 5.2.x Dec 8, 2025
18 checks passed
@bmw
bmw deleted the 5.2.x-finish-release branch December 8, 2025 17:03
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