Skip to content

Conversation

@Thijss
Copy link
Member

@Thijss Thijss commented Apr 18, 2025

Last minor release (1.2) it was difficult to group multiple PRs into one minor release using a merge queue. Reason: the queue only works if you merge PRs quick enough after another, which can be difficult when dealing with merge conflicts.

Therefore, I've altered the release workflow so that major and minor releases can only be triggered manually.

Should work! 😅

Thijss added 2 commits April 18, 2025 15:49
Signed-off-by: Thijs Baaijen <[email protected]>
@Thijss Thijss force-pushed the feat/prevent-auto-major-minor-release branch from 18bb6dc to 0d9eaca Compare April 18, 2025 13:51
Thijss added 4 commits April 18, 2025 15:55
Signed-off-by: Thijs Baaijen <[email protected]>
Signed-off-by: Thijs Baaijen <[email protected]>
Signed-off-by: Thijs Baaijen <[email protected]>
Signed-off-by: Thijs Baaijen <[email protected]>
@sonarqubecloud
Copy link

Copy link
Member

@jaapschoutenalliander jaapschoutenalliander left a comment

Choose a reason for hiding this comment

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

How would you then forse a manually triggered major/minor release? I think it is good to document this, and lets try it to see if it works now

@Thijss
Copy link
Member Author

Thijss commented Apr 18, 2025

How would you then forse a manually triggered major/minor release? I think it is good to document this, and lets try it to see if it works now

Documentation is a good suggestion.
You can do a major/minor release by starting the workflow from the main branch

@Thijss Thijss merged commit 22cc3e0 into main Apr 18, 2025
19 checks passed
@Thijss Thijss deleted the feat/prevent-auto-major-minor-release branch April 18, 2025 18:52
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