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 v0.4.1 #93

Merged
merged 1 commit into from
May 10, 2024
Merged

Release for v0.4.1 #93

merged 1 commit into from
May 10, 2024

Conversation

github-actions[bot]
Copy link
Contributor

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

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

🧰 Bug Fixes

📖 Documentation Changes

🧹 Refactoring

🎽 CI

⛓️ Dependency Updates

Full Changelog: v0.4.0...v0.4.1

@github-actions github-actions bot added the tagpr label May 10, 2024
@auto-assign auto-assign bot requested a review from 5ouma May 10, 2024 08:10
@5ouma 5ouma closed this May 10, 2024
@5ouma 5ouma reopened this May 10, 2024
@5ouma 5ouma merged commit 948b196 into main May 10, 2024
3 checks passed
@5ouma 5ouma deleted the tagpr-from-v0.4.0 branch May 10, 2024 08:15
@5ouma 5ouma added the 🚀 Release Related to release process label Jun 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🚀 Release Related to release process
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant