Skip to content
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

command that tags the most recently published version to npm as "legacy" #352

Open
bcoe opened this issue Jan 9, 2020 · 2 comments
Open
Labels
type: feature request ‘Nice-to-have’ improvement, new feature or different behavior or design.

Comments

@bcoe
Copy link
Contributor

bcoe commented Jan 9, 2020

For the Node.js version support policy I'm drafting, we need a command that creates a legacy dist-tag, based on the most recently published version of all of our libraries.

We would run this command immediately before dropping support for an EOL version of Node.js.

@bcoe bcoe added the type: feature request ‘Nice-to-have’ improvement, new feature or different behavior or design. label Jan 9, 2020
@JustinBeckwith
Copy link
Contributor

Do we need to add a new command here? For most things you'd do on the cmdline, you can follow the pattern:

repo sync
repo exec -- git some-command do-stuff
repo exec -- git push origin blergh

@bcoe
Copy link
Contributor Author

bcoe commented Jan 9, 2020

@JustinBeckwith the annoying thing is you need to pass the package version to npm dist-tag add, so I think it would be nice to have a script that parses the package.json, takes the most recently published version, and generates the npm dist-tag add command.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: feature request ‘Nice-to-have’ improvement, new feature or different behavior or design.
Projects
None yet
Development

No branches or pull requests

2 participants