Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ci(major-release): support run major release [0-9]+.0.0 #15329

Merged
merged 4 commits into from
Jan 27, 2025

Conversation

v1v
Copy link
Member

@v1v v1v commented Jan 22, 2025

Motivation/summary

Support an automated process to create new major releases from main.

At the moment, we use 8.x for running minor releases, but we will eventually won't need to do that but run patch releases from 8.x and minor releases from main.

This is just an automated process to help with the major releases, it behaves as minor releases but with the difference in the branch where things should be branched off or the support for the changelog/mergify thingy.

Checklist

For functional changes, consider:

  • Is it observable through the addition of either logging or metrics?
  • Is its use being published in telemetry to enable product improvement?
  • Have system tests been added to avoid regression?

How to test these changes

Major release

Given this PR, let's run the major-release target using my forked repository for the hypothetical release of 9.0.0.

$ gh pr checkout 15329
$ export GITHUB_TOKEN=$(gh auth token)
$ make major-release RELEASE_VERSION=9.0.0 PROJECT_OWNER=v1v RELEASE_TYPE=major

It created two PRs:

and updated 9.0 -> main...v1v:apm-server:9.0

Minor release

Then I ran the same for a new minor release 8.19.0 - but i required to sync up 8.x

$ git checkout 8.x
$ git cherry-pick 4fb3bbaf749d93518bfae48dccb859d475107c09
$ gh pr checkout 15329
$ export GITHUB_TOKEN=$(gh auth token)
$ make minor-release RELEASE_VERSION=8.19.0 PROJECT_OWNER=v1v RELEASE_TYPE=minor

It created three PRs:

Related issues

Part of #13968

Copy link
Contributor

mergify bot commented Jan 22, 2025

This pull request does not have a backport label. Could you fix it @v1v? 🙏
To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

  • backport-7.17 is the label to automatically backport to the 7.17 branch.
  • backport-8./d is the label to automatically backport to the 8./d branch. /d is the digit.
  • backport-8.x is the label to automatically backport to the 8.x branch.

Copy link
Contributor

mergify bot commented Jan 22, 2025

backport-8.x has been added to help with the transition to the new branch 8.x.
If you don't need it please use backport-skip label.

@mergify mergify bot added the backport-8.x Automated backport to the 8.x branch with mergify label Jan 22, 2025
@v1v v1v force-pushed the feature/support-major-release branch from 7529128 to 7f32abe Compare January 22, 2025 18:07
@v1v v1v self-assigned this Jan 22, 2025
@v1v v1v requested a review from a team January 22, 2025 18:12
@v1v v1v marked this pull request as ready for review January 22, 2025 18:12
@v1v v1v requested a review from a team as a code owner January 22, 2025 18:12
Co-authored-by: Ivan Fernandez Calvo <[email protected]>
@v1v v1v enabled auto-merge (squash) January 27, 2025 15:29
@v1v v1v merged commit 5bab00e into elastic:main Jan 27, 2025
16 checks passed
mergify bot pushed a commit that referenced this pull request Jan 27, 2025
mergify bot added a commit that referenced this pull request Jan 27, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport-8.x Automated backport to the 8.x branch with mergify
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants