Skip to content

Release for v3.1.3#76

Open
github-actions[bot] wants to merge 2 commits into
mainfrom
tagpr-from-v3.1.2
Open

Release for v3.1.3#76
github-actions[bot] wants to merge 2 commits into
mainfrom
tagpr-from-v3.1.2

Conversation

@github-actions
Copy link
Copy Markdown

@github-actions github-actions Bot commented May 21, 2026

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

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

Full Changelog: v3.1.2...tagpr-from-v3.1.2

@github-actions github-actions Bot added the tagpr label May 21, 2026
@github-actions github-actions Bot force-pushed the tagpr-from-v3.1.2 branch 2 times, most recently from 45981cc to 5b16aab Compare May 26, 2026 23:40
@github-actions github-actions Bot force-pushed the tagpr-from-v3.1.2 branch 2 times, most recently from e1a9828 to 08a8e22 Compare June 4, 2026 12:21
@github-actions github-actions Bot requested a review from shamaton as a code owner June 4, 2026 12:21
@github-actions github-actions Bot force-pushed the tagpr-from-v3.1.2 branch 2 times, most recently from bf2fccc to cc789fe Compare June 4, 2026 13:30
@github-actions github-actions Bot force-pushed the tagpr-from-v3.1.2 branch from cc789fe to de79548 Compare June 4, 2026 13:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants