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.5.0 #2906

Merged
merged 2 commits into from
Jan 2, 2025
Merged

Release for v0.5.0 #2906

merged 2 commits into from
Jan 2, 2025

Conversation

github-actions[bot]
Copy link
Contributor

@github-actions github-actions bot commented Sep 4, 2024

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

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

💪 Improvements

💥 Breaking Changes

🐛 Bug Fixes

📖 Documentation improvements

🧪 Test improvements and Misc Fixes

Other Changes

New Contributors

Full Changelog: v0.4.1...v0.5.0

@github-actions github-actions bot added the tagpr label Sep 4, 2024
@github-actions github-actions bot force-pushed the tagpr-from-v0.4.1 branch 6 times, most recently from 84b3a30 to 6e157c8 Compare September 26, 2024 05:19
@github-actions github-actions bot force-pushed the tagpr-from-v0.4.1 branch 7 times, most recently from 45e7408 to 48bf1b0 Compare October 1, 2024 04:38
@github-actions github-actions bot force-pushed the tagpr-from-v0.4.1 branch 4 times, most recently from d2f4563 to c38e1a8 Compare October 13, 2024 04:53
@github-actions github-actions bot force-pushed the tagpr-from-v0.4.1 branch 2 times, most recently from 40ebc3d to 5fc0a16 Compare October 22, 2024 12:33
@github-actions github-actions bot force-pushed the tagpr-from-v0.4.1 branch 6 times, most recently from e2a4b44 to 97cd549 Compare November 3, 2024 12:39
@github-actions github-actions bot force-pushed the tagpr-from-v0.4.1 branch 3 times, most recently from a17f262 to d06a1ad Compare November 12, 2024 13:11
@github-actions github-actions bot force-pushed the tagpr-from-v0.4.1 branch 4 times, most recently from 5238057 to 031a076 Compare November 26, 2024 05:13
@github-actions github-actions bot force-pushed the tagpr-from-v0.4.1 branch 2 times, most recently from 6d809fb to e03b386 Compare December 9, 2024 11:35
@YJDoc2 YJDoc2 mentioned this pull request Dec 9, 2024
@github-actions github-actions bot changed the title Release for v0.4.2 Release for v0.5.0 Dec 14, 2024
@github-actions github-actions bot force-pushed the tagpr-from-v0.4.1 branch 3 times, most recently from 2bfa73d to 2f32d14 Compare December 18, 2024 04:50
@github-actions github-actions bot changed the title Release for v0.5.0 Release for v0.5.1 Dec 31, 2024
@utam0k utam0k changed the title Release for v0.5.1 Release for v0.5.0 Dec 31, 2024
@github-actions github-actions bot changed the title Release for v0.5.0 Release for v0.5.1 Jan 1, 2025
@github-actions github-actions bot force-pushed the tagpr-from-v0.4.1 branch 3 times, most recently from ffe1f64 to 071bd4e Compare January 2, 2025 04:58
@github-actions github-actions bot changed the title Release for v0.5.1 Release for v0.5.0 Jan 2, 2025
@utam0k
Copy link
Member

utam0k commented Jan 2, 2025

@YJDoc2 it looks fine. Thanks for your review 🙏

@utam0k utam0k merged commit dcb299f into main Jan 2, 2025
1 check passed
@utam0k utam0k deleted the tagpr-from-v0.4.1 branch January 2, 2025 10:27
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