-
Notifications
You must be signed in to change notification settings - Fork 15
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
use @node-core
#36
base: main
Are you sure you want to change the base?
use @node-core
#36
Conversation
We already have a release workflow in .github/workflows/test-and-release.yml using semantic-release (which also looks to support npm provenance). |
Ok I'll read that I'm not 100% aware on this tool. Thanks for mentioning that |
@richardlau DONE ! |
any news ? |
I think this repo might have an npm api key for me in it, so a new one might need to be inserted to publish to this new scope as I don't think I have access to it. |
also, a package.json conflict needs to be resolved |
@rvagg any news ? (I know I have to fix conflict again) |
🤷 I don't care too much but this would have to be plumbed through to the server that uses it. I also don't know if I have access to publish to that scope, the auto-publish workflow might break on this so in terms of friction I wouldn't bother but it depends on who's pushing for it and how much effort they want to go to |
#21
@node-core
npm scope