ci: support npm trusted publishers #733
Conversation
| [ | ||
| "@semantic-release/exec", | ||
| { | ||
| "execCwd": "components/client/typescript", | ||
| "prepareCmd": "npm ci" | ||
| } | ||
| ], |
There was a problem hiding this comment.
Does this package also need to be built to publish it? Not all packages do.
There was a problem hiding this comment.
This client is actually not integrated into semantic release yet and we've had to do the publishing by hand. We won't be able to integrate it into this file as easily because it has a completely different version than the repo release package.
We're deprecating this repo very soon so I think we should just keep it as is for now, what do you think?
There was a problem hiding this comment.
Keeping it as-is would be ok in that context. This effort is mostly to prevent CI from breaking from NPM removes all tokens in early December. If this release has not been integrated with CI, then there's nothing to break :)
Will close this one out.
CharlieC3
requested a deployment
to
Development-mainnet
GitHub Actions
Waiting
CharlieC3
requested a deployment
to
Development-testnet
GitHub Actions
Waiting
Related https://github.com/hirosystems/devops/issues/2230