Repository navigation
Generate git tags for private packages #218
Description
For our project all of our packages are private, so running yarn changeset publish is essentially a no-op. However, I’d really like to get the git tags. Is there a way to tell changesets to generate the tags even for private packages?
Affected Packages
@changesets/cli
Problem
For our project all of our packages are private, so running yarn changeset publish is essentially a no-op. However, I’d really like to get the git tags. Is there a way to tell changesets to generate the tags even for private packages?
Proposed solution
Maybe something like the ability to do:
yarn changeset tag --private=true
Not too fussed on how it ends up being run.
Reacted by Ian Walter, Ricardo Casares, some1chan, cjohannessen-qualtrics, Vedegis and karteekiitg
Activity
Noviny commentedon Nov 5, 2019
Couple of additional thoughts
I would like if
publishjust added new tags for private packages by default, no config needed.This means complicating the check in general - it's also more fault-likely. We need to check if the tag exists in git - if it doesn't add it. So a different check.
I'm unsure for totally private repos. Running
publishfeels odd, but maybe it's fine still?Noviny commentedon Nov 5, 2019
There's a slight tension around making
publishextra-complicated. We probably want to refactor some of that code to make it easier for future code-maintainers, as this might tip us over into 'unintelligible garbage'timleslie commentedon Nov 6, 2019
As a user, I could get behind this 👍
emberist commentedon Oct 18, 2023
Hey guys, If someone is still searching for a solution, here is documented something interesting
bluwy commentedon Jun 8, 2026
I believe the
privatePackages.tagoption address this