Skip to content
This repository has been archived by the owner on May 1, 2020. It is now read-only.

Automate publishing and dependencies #11

Closed
rarkins opened this issue Dec 20, 2017 · 2 comments
Closed

Automate publishing and dependencies #11

rarkins opened this issue Dec 20, 2017 · 2 comments
Labels
pri3-normal ready Ready to begin work on

Comments

@rarkins
Copy link
Collaborator

rarkins commented Dec 20, 2017

e.g. group depends on monorepo

@rarkins rarkins added needs-requirements Needs further requirements before implementation can start pri3-normal labels Apr 5, 2018
@rarkins rarkins added ready Ready to begin work on and removed needs-requirements Needs further requirements before implementation can start labels Sep 21, 2018
@ChristianMurphy
Copy link

Lerna could be a good option, https://lernajs.io
It's specialty is managing linked dependencies.

the workflow would look something like

$ lerna publish
? Select a new version (currently 1.1.4) 
❯ Patch (1.1.5) 
  Minor (1.2.0) 
  Major (2.0.0) 
  Prepatch (1.1.5-alpha.0) 
  Preminor (1.2.0-alpha.0) 
  Premajor (2.0.0-alpha.0) 
  Custom Prerelease 
  Custom Version 

select the version, the lerna builds a dependency tree of code in the monorepo, releasing leaf nodes/projects first, and working up the tree to parent nodes/projects.

The only gotcha I've run into so far is with two factor authentication, see lerna/lerna#1091
where the OTP currently needs to be added as an ENV variable.

NPM_CONFIG_OTP=123456 lerna publish

@viceice
Copy link
Member

viceice commented Apr 28, 2020

superseeded by #202, so can be closed

@rarkins rarkins closed this as completed Apr 28, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
pri3-normal ready Ready to begin work on
Projects
None yet
Development

No branches or pull requests

3 participants