Closed chrsmith closed 4 years ago
This is fine to trigger this initial NPM publish, but we're not planning to use release branches to do that going forward are we? Usually we just tag a commit as v0.1.0
or whatever, and the NPM publish of version 0.1.0
would happen off that. And then subsequent commits to master are tagged as dev versions of the next version increment like 0.1.1-dev.1574307610
.
See https://www.npmjs.com/package/@pulumi/policy?activeTab=versions
This is fine to trigger this initial NPM publish, but we're not planning to use release branches to do that going forward are we?
@justinvp yes, we'll do the "standard thing". I just wanted to avoid tagging some experiment I was planning on unpublishing.
Closing out-of-date PR that's no longer needed.
I do not plan on merging this. This PR is just to trigger the Travis job to publish a package to NPM, so I can then work on consuming it within the Pulumi Service repo. (To start on docs/guides for how to share and customize policy packs.)