Skip to content
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

Merged
merged 3 commits into from
Apr 19, 2024

Conversation

jeanregisser
Copy link
Member

@jeanregisser jeanregisser commented Apr 17, 2024

Publish automatically to NPM using semantic-release

Similar to what we did in valora-inc/logging#5

Fixes RET-1037

Comment on lines 86 to 87
NPM_TOKEN:valora-viem-hsm-test/NPM_TOKEN
SLACK_WEBHOOK_URL:valora-viem-hsm-test/SLACK_ONCALL_WEBHOOK_URL
Copy link
Member Author

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.

Copy link
Member Author

@jeanregisser jeanregisser Apr 18, 2024

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.

Base automatically changed from jeanregisser/readme to main April 19, 2024 09:29
Copy link

@kathaypacific kathaypacific left a 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",

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?

Copy link
Member Author

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.

@jeanregisser jeanregisser merged commit c07c154 into main Apr 19, 2024
6 checks passed
@jeanregisser jeanregisser deleted the jeanregisser/semantic-release branch April 19, 2024 10:11
Copy link

🎉 This PR is included in version 1.0.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

This pull request was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants