Is it really deprecated forever and We should migrate to another solution?
tomavic opened this issue · 5 comments
Why there is no more information about the deprecation and more solutions as alternatives?
I've forked to commit-and-tag-version here https://github.com/absolute-version/commit-and-tag-version , which is tested on all current releases of node, and also contains merges of all the working PRs that didn't seem to require extra discussion or change the purpose of the tool. You're welcome to use that if you like.
I can also tell you that having used release-please, it really is excellent and requires less work than this (also excellent) tool. The primary difference is that release-please comes with the problem of "ok now how do I get this release commit into a protected master branch" completely solved. If it works for you, great. If not, you're welcome to use commit-and-tag-version as a drop-in replacement. I plan to continue maintaining it (and of course contributions welcome).
@TimothyJones Thanks for that. I will definitely try to release-please first on a sample app, and will check if it satisfies my needs.
For me I didn't find a solution yet to update my protected (master or dev) branches after each release on any release/* branch. I am allowing pipelines to force push of dev after each pre-release or release, so that dev branch is up-to-date with the latest commit all the time. But it is not recommended.
Any ideas on best way to do it without braking the rules of the protected branch? or any out-of-box idea on the whole workflow?
It's a little off topic for this issue, but it's also an easy answer - the way release-please works is to separate the commit and the tag. It maintains a PR that contains the release commit with the current changelog. Once you merge the PR, release-please then tags the commit in master. It's a pretty clever solution.
I am going to close the issue as it was an open discussion only. I hope it could help people coming from "Google Search Results" too 🤖