You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If I first run the bump script it will create a commit like "ci(bump): bumped version to v1.1.4" and then it will run the tag script but it will responde with "no change in version needed commit=ci(bump): bumped version to v1.1.4" so the commit never gets a tag.
Steps to reproduce it
1. run uplift bump
2. run uplift tag
Your uplift configuration
firstVersion: v1.0.0annotatedTags: falsecommitAuthor:
name: "..."email: "..."bumps:
- # The path of the file relative to where uplift is executedfile: ./pubspec.yamlregex: "version: $VERSION"semver: true
Which version?
1.2.0
Which operating system(s) are you using?
Linux, Windows
Optional debug output
No response
Code of Conduct
I agree to follow this project's Code of Conduct
The text was updated successfully, but these errors were encountered:
Thanks, @emilrowland for raising the issue. I was looking to include an additional release command to the CLI which would remove the need to run a single operation in turn. I am in the process of adding the ability to create a changelog, which will also be exposed through a new changelog command. I'll park that and focus on adding this release capability.
I have added a new release command. I have kept it basic for now. It effectively combines the workflow of both bumping files and tagging the changes in a combined operation
What happened?
If I first run the bump script it will create a commit like "ci(bump): bumped version to v1.1.4" and then it will run the tag script but it will responde with "no change in version needed commit=ci(bump): bumped version to v1.1.4" so the commit never gets a tag.
Steps to reproduce it
Your uplift configuration
Which version?
1.2.0
Which operating system(s) are you using?
Linux, Windows
Optional debug output
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: