-
Notifications
You must be signed in to change notification settings - Fork 0
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
chore: publish automatically to NPM #4
Conversation
.github/workflows/workflow.yaml
Outdated
NPM_TOKEN:valora-viem-hsm-test/NPM_TOKEN | ||
SLACK_WEBHOOK_URL:valora-viem-hsm-test/SLACK_ONCALL_WEBHOOK_URL |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For now I've copied these secrets from celo-mobile-mainnet
to the new GCP project valora-viem-hsm-test
.
But to limit duplication, we could grant access to the service account I created for the new project.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok I've updated it to access the specific secrets needed and avoid duplication.
d344859
to
111e123
Compare
042f120
to
8bd1d3b
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
"main": "dist/index.js", | ||
"repository": "git@github.com:valora-inc/typescript-starter.git", | ||
"name": "@valora/viem-account-hsm-gcp", | ||
"version": "0.0.0-semantic-release", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
woah, is this a special version number for the initial release?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No it's just to denote that the version is managed by semantic-release. And hopefully avoid confusion.
🎉 This PR is included in version 1.0.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Publish automatically to NPM using semantic-release
Similar to what we did in valora-inc/logging#5
Fixes RET-1037