pnpm dlx create-release-plan-setup@latest --update #2334
Conversation
| @@ -97,7 +97,7 @@ | |||
| "npm-package-json-lint": "^7.0.0", | |||
| "npm-run-all": "^4.1.5", | |||
| "prettier": "^3.0.3", | |||
| "release-plan": "^0.11.0", | |||
There was a problem hiding this comment.
woah, this was quite old!
| - run: pnpm install --frozen-lockfile | ||
| - run: pnpm release-plan publish --provenance | ||
| - name: Publish to NPM | ||
| run: NPM_CONFIG_PROVENANCE=true pnpm release-plan publish |
There was a problem hiding this comment.
we get provenance now
There was a problem hiding this comment.
provenance was working successfully as of 12.7.3.
Why the need to use NPM_CONFIG_PROVENANCE=true instead of just --provenance now?
There was a problem hiding this comment.
Not a question for here, but for the release-plan-setup -- none of these choices are "mine" but just "boilerplate so I don't have to maintain anything"
| runs-on: ubuntu-latest | ||
| outputs: | ||
| command: ${{ steps.check-release.outputs.command }} | ||
|
|
||
| steps: | ||
| - uses: actions/checkout@v5 | ||
| - uses: actions/checkout@v4 |
There was a problem hiding this comment.
Is it necessary to downgrade actions/checkout and actions/setup-node?
There was a problem hiding this comment.
Not a question for here, but for the release-plan-setup -- none of these choices are "mine" but just "boilerplate so I don't have to maintain anything"
There was a problem hiding this comment.
real answer: v5 came out like.. this week, ya?
No description provided.