-
Notifications
You must be signed in to change notification settings - Fork 3
Initial implementation of v3 #26
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: v3-staging
Are you sure you want to change the base?
Conversation
@@ -0,0 +1,14 @@ | |||
{ |
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 local-publish
like in the corelibrary? 🤔
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.
I forgot about that, I will add it shortly
"local-publish": { | ||
"command": "npx nx run-many -t publish --registry=http://localhost:4873/ --ver={args.ver} --tag={args.tag}" |
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.
This by itself is not enough. You also have to update publish
target in package's project.json
and update (use corelibrary version) publish.mjs
in tools/scripts
run: npx nx run-many -t test | ||
- name: Build & Publish | ||
run: | ||
npx nx run-many -t publish --registry=npm --ver=${{ format('{0}', | ||
steps.package-version.outputs.current-version)}} --tag=latest |
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.
You might want to match current release workflow from corelibrary, but there is only one package in this repo so there shouldn't be any issues with current version.
No description provided.