Skip to content

Release for v2.5.4#385

Open
MH4GF wants to merge 2 commits intomainfrom
tagpr-from-v2.5.3
Open

Release for v2.5.4#385
MH4GF wants to merge 2 commits intomainfrom
tagpr-from-v2.5.3

Conversation

@MH4GF
Copy link
Owner

@MH4GF MH4GF commented Jan 6, 2025

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

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

Maintenance 👨‍💻

Full Changelog: v2.5.3...v2.5.4

@MH4GF MH4GF added the tagpr label Jan 6, 2025
@github-actions github-actions bot force-pushed the tagpr-from-v2.5.3 branch 3 times, most recently from d33ea79 to 469f614 Compare February 4, 2025 18:28
@github-actions github-actions bot force-pushed the tagpr-from-v2.5.3 branch from 469f614 to 8f7e3d0 Compare March 1, 2025 02:40
@github-actions github-actions bot force-pushed the tagpr-from-v2.5.3 branch from 8f7e3d0 to b5b91e9 Compare April 1, 2025 02:14
@github-actions github-actions bot force-pushed the tagpr-from-v2.5.3 branch 6 times, most recently from caa11ab to 496c836 Compare March 6, 2026 03:43
@MH4GF MH4GF force-pushed the tagpr-from-v2.5.3 branch from 496c836 to 200fda1 Compare March 6, 2026 03:52
@MH4GF MH4GF force-pushed the tagpr-from-v2.5.3 branch from 200fda1 to 72a45fa Compare March 6, 2026 04:46
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.

1 participant