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.1.0 #2

Merged
merged 2 commits into from
Jul 13, 2024
Merged

Release for v0.1.0 #2

merged 2 commits into from
Jul 13, 2024

Conversation

arthur1-bot[bot]
Copy link

@arthur1-bot arthur1-bot bot commented Jul 12, 2024

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

You can modify this branch "tagpr-from-v0.0.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: https://github.com/Arthur1/http-client-cache/commits/v0.1.0

@arthur1-bot arthur1-bot bot added the tagpr label Jul 12, 2024
@arthur1-bot arthur1-bot bot force-pushed the tagpr-from-v0.0.0 branch 2 times, most recently from 7062d32 to cbe1998 Compare July 13, 2024 02:02
@arthur1-bot arthur1-bot bot changed the title Release for v0.0.1 Release for v0.1.0 Jul 13, 2024
@Arthur1 Arthur1 merged commit e61a38a into main Jul 13, 2024
4 checks passed
@Arthur1 Arthur1 deleted the tagpr-from-v0.0.0 branch July 13, 2024 02:20
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