Skip to content

Version bump after release & release tool change - #2450

Merged
vojtapolasek merged 2 commits into
OpenSCAP:maint-1.3from
jan-cerny:after_release_maint-1.3
Oct 20, 2026
Merged

vojtapolasek merged 2 commits into
OpenSCAP:maint-1.3from
jan-cerny:after_release_maint-1.3

Conversation

@jan-cerny

Copy link
Copy Markdown
Member

Version bump after release

Next release from the maint-1.3 branch will be 1.3.16

Remove check of the previous commit

We started to require submitting all changes via pull requests.
If the release commit goes via pull request, it won't be the latest
commit in the history, the latest will be the merge commit.
Also, if the release workflow fails, we need to modify it again
by a pull request.

We started to require submitting all changes via pull requests.
If the release commit goes via pull request, it won't be the latest
commit in the history, the latest will be the merge commit.
Also, if the release workflow fails, we need to modify it again
by a pull request.
Next release from the maint-1.3 branch will be 1.3.16
@jan-cerny jan-cerny added this to the 1.3.16 milestone Oct 13, 2026
@sonarqubecloud

Copy link
Copy Markdown

@jan-cerny jan-cerny changed the title After release maint 1.3 Version bump after release & release tool change Oct 20, 2026

@vojtapolasek vojtapolasek 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.

LGTM

@vojtapolasek
vojtapolasek merged commit 9e56d6f into OpenSCAP:maint-1.3 Oct 20, 2026
11 checks passed
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