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

Release for v2.5.0 #709

Merged
merged 3 commits into from
May 31, 2024
Merged

Release for v2.5.0 #709

merged 3 commits into from
May 31, 2024

Conversation

github-actions[bot]
Copy link
Contributor

@github-actions github-actions bot commented May 30, 2024

This pull request is for the next release as v2.5.0 created by tagpr. Merging it will tag v2.5.0 to the merge commit and create a GitHub release.

You can modify this branch "tagpr-from-v2.4.2" directly before merging if you want to change the next version number or other files for the release.

How to change the next version as you like

There are two ways to do it.

  • Version file
    • Edit and commit the version file specified in the .tagpr configuration file to describe the next version
    • If you want to use another version file, edit the configuration file.
  • Labels convention
    • Add labels to this pull request like "tagpr:minor" or "tagpr:major"
    • If no conventional labels are added, the patch version is incremented as is.

What's Changed

New Contributors

Full Changelog: v2.4.2...v2.5.0

@github-actions github-actions bot added the tagpr label May 30, 2024
@github-actions github-actions bot changed the title Release for v2.4.3 Release for v2.5.0 May 30, 2024
@github-actions github-actions bot force-pushed the tagpr-from-v2.4.2 branch 2 times, most recently from df30d59 to 1647c27 Compare May 30, 2024 20:33
@YumNumm YumNumm merged commit 81e9bb2 into develop May 31, 2024
1 of 3 checks passed
@YumNumm YumNumm deleted the tagpr-from-v2.4.2 branch May 31, 2024 16:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant