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 v1.6.0 #380

Merged
merged 2 commits into from
Apr 4, 2024
Merged

Release for v1.6.0 #380

merged 2 commits into from
Apr 4, 2024

Conversation

github-actions[bot]
Copy link
Contributor

@github-actions github-actions bot commented Apr 4, 2024

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

You can modify this branch "tagpr-from-v1.5.0" 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: v1.5.0...v1.6.0

@github-actions github-actions bot added the tagpr label Apr 4, 2024
@github-actions github-actions bot force-pushed the tagpr-from-v1.5.0 branch 4 times, most recently from fbcf351 to eaa6913 Compare April 4, 2024 02:31
@github-actions github-actions bot changed the title Release for v1.5.1 Release for v1.6.0 Apr 4, 2024
@Songmu Songmu merged commit 7e11957 into master Apr 4, 2024
@Songmu Songmu deleted the tagpr-from-v1.5.0 branch April 4, 2024 05:59
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