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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Release for v0.109.0 #930

Merged
merged 2 commits into from
May 23, 2024
Merged

Release for v0.109.0 #930

merged 2 commits into from
May 23, 2024

Conversation

github-actions[bot]
Copy link
Contributor

@github-actions github-actions bot commented May 20, 2024

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

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

Breaking Changes 馃洜

New Features 馃帀

Full Changelog: v0.108.1...v0.109.0

@github-actions github-actions bot added the tagpr label May 20, 2024
@github-actions github-actions bot changed the title Release for v0.108.2 Release for v0.109.0 May 20, 2024
@github-actions github-actions bot force-pushed the tagpr-from-v0.108.1 branch 4 times, most recently from 9111d39 to b549043 Compare May 22, 2024 04:17
@k1LoW k1LoW merged commit a378a8a into main May 23, 2024
@k1LoW k1LoW deleted the tagpr-from-v0.108.1 branch May 23, 2024 12:10
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.

None yet

1 participant