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 v1.59.0 #408

Merged
merged 2 commits into from
Jan 22, 2023
Merged

Release for v1.59.0 #408

merged 2 commits into from
Jan 22, 2023

Conversation

github-actions[bot]
Copy link
Contributor

@github-actions github-actions bot commented Jan 19, 2023

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

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

Full Changelog: v1.58.0...v1.59.0

@github-actions github-actions bot added the tagpr label Jan 19, 2023
@github-actions github-actions bot changed the title Release for v1.58.1 Release for v1.59.0 Jan 19, 2023
@github-actions github-actions bot force-pushed the tagpr-from-v1.58.0 branch 7 times, most recently from 2e4592c to 754e391 Compare January 22, 2023 14:28
@k1LoW k1LoW merged commit fb53f48 into main Jan 22, 2023
@k1LoW k1LoW deleted the tagpr-from-v1.58.0 branch January 22, 2023 15:06
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