Skip to content

Add ReleaseCandidate releases feature#7

Merged
alecslupu merged 36 commits intomainfrom
feature/release-candidate-version
Mar 3, 2025
Merged

Add ReleaseCandidate releases feature#7
alecslupu merged 36 commits intomainfrom
feature/release-candidate-version

Conversation

@andreslucena
Copy link
Copy Markdown
Member

@andreslucena andreslucena commented Jul 16, 2024

Until now, the decidim-releaser script only was working for Patch versions (i.e. from v0.28.0 to v0.28.1).

This PR introduces the feature to make Release Candidates using this same tool (i.e. from v0.29.0.dev to v0.29.0.rc1).

For doing that, what I've done is:

  1. Extract the Patch code to its own class (ReleasePatchVersion)
  2. Make a ReleaseCandidateVersion class
  3. Move the common logic to the ReleaserUtils module

After this is merged, the next iteration would be to have a new class from ReleaseMinorVersion (from v0.29.0.rcX to v0.29.0)

As it is specially tricky to actually run this script without making a release, I can confirm that I've used this to create the branches for:

To check that I didn't break anything with the ReleasePatchVersion refactor, I've used this to create the branches for:

I think this is ready for a merge.

@andreslucena andreslucena changed the title Run webpack rake task for v0.27 Add ReleaseCandidate releases feature Jul 16, 2024
@andreslucena andreslucena marked this pull request as ready for review July 16, 2024 16:39
Copy link
Copy Markdown
Contributor

@alecslupu alecslupu left a comment

Choose a reason for hiding this comment

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

One small change, and i think is good to go.

@andreslucena
Copy link
Copy Markdown
Member Author

@alecslupu this is ready for another round (I forget about this PR and it'd be nice to have it for the v0.30 release :D)

alecslupu
alecslupu previously approved these changes Feb 13, 2025
Copy link
Copy Markdown
Contributor

@alecslupu alecslupu left a comment

Choose a reason for hiding this comment

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

👍
LGTM . let's see how it behaves ..

@andreslucena
Copy link
Copy Markdown
Member Author

andreslucena commented Feb 18, 2025

@alecslupu this is ready for another round!

I try it out with #14096 and #14109, and apart from some missing requires (like using the present? method from ActiveSupport without doing the require in the file that was necessary) I also found another bug related to the tests: we were doing the tests execution once the release branch was prepared and we should do it at the begging of the process, so it's much easier to restart and try again. This is fixed too.

About the documentation, the instructions are available at #14066, so we can merge that after this is merged.

Copy link
Copy Markdown
Contributor

@alecslupu alecslupu left a comment

Choose a reason for hiding this comment

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

I haven't managed to test it, but reading through it, LGTM

@alecslupu alecslupu merged commit 1042e13 into main Mar 3, 2025
@alecslupu alecslupu deleted the feature/release-candidate-version branch March 3, 2025 09:01
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