-
Notifications
You must be signed in to change notification settings - Fork 1
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
Adding common release pipeline #69
Conversation
This reverts commit 270e4fb.
name: Package release to NPM | ||
on: | ||
workflow_call: | ||
inputs: | ||
working_directory: | ||
required: true | ||
type: string | ||
package_name: | ||
required: true | ||
type: string | ||
secrets: | ||
npm_token: | ||
required: true | ||
|
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.
If it works, I will update api-common
release and add the pipeline for all the other packages
The base pipeline is failing, putting as draft in the meantime we apply the required changes |
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.
Kudos @CarlosGamero, you're the best ❤️
Changes
Adding a common pipeline to avoid boilerplate code needed on release pipelines, also, using it with
websockets-common
to be able to test it and check if it is really workingChecklist
major
,minor
,patch
orskip-release