-
Notifications
You must be signed in to change notification settings - Fork 155
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 v1.0.5 #116
Comments
Hey, for Java software I like to use the maven-release-plugin. Basically, the version is always something like 1.0.5-SNAPSHOT, and when you execute the prepare goal of this plugin it will automatically change the version to 1.0.5, make a commit and a new tag, from which artifacts can be build. Then, it will make a new commit to go to 1.0.6-SNAPSHOT. Would be nice to also have #112 and #113 in this release :D. |
Let me see what I can do - thanks |
Any word on this? We would really like to use this tool without failing on the issue in PR #113 |
I've forked this repository to have my own build pipeline. I've merged some of the PR here and update dependencies : |
hi - just checking in. Is there any plan on release v1.0.5? |
Hi,
Thank you for merging #114 - is there any chance you can cut a new release? I did a quick look at the process and raised a VERY naive PR: #115 - not advocating for that solution in any way but I think would trigger a new release to be cut.
If you have a different process and can cut a new release to remove the vulnerability from the library would very much appreciate it. Also happy to contribute to the release process if you have a pattern in mind.
Thank you!
The text was updated successfully, but these errors were encountered: