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.3.1 #62

Merged
merged 2 commits into from
Feb 11, 2025
Merged

Release for v1.3.1 #62

merged 2 commits into from
Feb 11, 2025

Conversation

github-actions[bot]
Copy link
Contributor

@github-actions github-actions bot commented Feb 10, 2025

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

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

Others

New Contributors

Full Changelog: v1.3.0...v1.3.1

@github-actions github-actions bot added the tagpr Used by tagpr for managing the release label Feb 10, 2025
@github-actions github-actions bot force-pushed the tagpr-from-v1.3.0 branch 2 times, most recently from 5f531a9 to fc49fb9 Compare February 11, 2025 12:25
@babarot babarot merged commit 0c2fdf0 into main Feb 11, 2025
1 check passed
@babarot babarot deleted the tagpr-from-v1.3.0 branch February 11, 2025 12:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
tagpr Used by tagpr for managing the release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant