-
-
Notifications
You must be signed in to change notification settings - Fork 297
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
Is there a way to publish minor/patch release of old major version? #154
Comments
In my opinion, no. I have addressed this a couple of times already but currently |
I think you can already do this: |
I've had no problem with: git checkout -b backport-the-things v2.0.0 # (2.0.0 being previous major)
# make some changes
git commit -m "backporting changes"
git push -u origin backport-the-things
np --any-branch Then selecting 'patch' like normal would release |
Okay, cool. Nice to know that it works :). |
@jesstelford Don't forget the |
Forgetting the it could ensure the use of Great that it's already doable to do older releases, but as shown it's easy to do a mistake, and I don't like to tell my team mates to do something that is easy to mess up, then I rather tell them to try to avoid it. So could be neat if it was supported, but of course also neat with a lean tool. |
I think that we should mention @jesstelford's suggestion above in the |
Just came across a case where I needed to back port a patch to a previous major version as I'm not yet able to update all of my projects to the new major version of my module, but I'm getting the impression that
np
doesn't support releasing any minor or patch versions of previous major releases?Would be great to have such support within
np
, especially as it's so easy to accidentally publish that minor/patch version aslatest
tag (pretty common by even very large modules when they do an occasional maintenance release)Am I understanding the current state of
np
correctly? And if so: Is it something that you would be interested in supporting? (Maybe as--maintenance
or such?)The text was updated successfully, but these errors were encountered: