Skip to content

Release for v0.3.0#14

Merged
buty4649 merged 3 commits intomainfrom
tagpr-from-v0.2.0
Jun 18, 2025
Merged

Release for v0.3.0#14
buty4649 merged 3 commits intomainfrom
tagpr-from-v0.2.0

Conversation

@github-actions
Copy link
Copy Markdown
Contributor

@github-actions github-actions bot commented Jun 18, 2025

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

You can modify this branch "tagpr-from-v0.2.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: v0.2.0...v0.3.0

@github-actions github-actions bot added the tagpr label Jun 18, 2025
@github-actions github-actions bot changed the title Release for v0.2.1 Release for v0.3.0 Jun 18, 2025
@github-actions github-actions bot force-pushed the tagpr-from-v0.2.0 branch from f2707ee to 58f0dc1 Compare June 18, 2025 04:55
@pepabo-pr-maker pepabo-pr-maker bot force-pushed the tagpr-from-v0.2.0 branch from 58f0dc1 to 1970fb1 Compare June 18, 2025 05:13
@buty4649 buty4649 enabled auto-merge June 18, 2025 06:22
@buty4649 buty4649 merged commit a630f97 into main Jun 18, 2025
2 checks passed
@buty4649 buty4649 deleted the tagpr-from-v0.2.0 branch June 18, 2025 06:23
@pepabo-pr-maker pepabo-pr-maker bot mentioned this pull request Jun 18, 2025
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