-
Notifications
You must be signed in to change notification settings - Fork 26
build: Enable npm publish packages via Changesets #73
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
base: main
Are you sure you want to change the base?
build: Enable npm publish packages via Changesets #73
Conversation
Signed-off-by: Gabriel Mata <[email protected]>
Signed-off-by: Gabriel Mata <[email protected]>
Signed-off-by: Gabriel Mata <[email protected]>
Signed-off-by: Gabriel Mata <[email protected]>
Signed-off-by: Gabriel Mata <[email protected]>
Signed-off-by: Gabriel Mata <[email protected]>
Signed-off-by: Gabriel Mata <[email protected]>
genaris
left a comment
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.
Thanks @gabrielmatau79! Overall it looks good to me. Not too much to say but surely there are things we are missing and will need to iterate a bit to get it working, as usual with these tricky CI/CD PRs...
@TimoGlastra do you know what's the procedure to ask for the NPM token to be added to this repo secrets?
With trusted publishing it's now actually easier. I just need to know the package names and I can link them to this github repository (I think) |
Signed-off-by: Gabriel Mata <[email protected]>
Signed-off-by: Gabriel Mata <[email protected]>
Summary
This PR introduces automated versioning and publishing NPM for the didcomm-mediator-credo monorepo using Changesets
and pnpm.
Notes
A valid npm automation token must be configured in repository secrets:
Close #61