-
Notifications
You must be signed in to change notification settings - Fork 235
fix: fix snapshot and preview releases #5906
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?
Conversation
|
📚 Branch Preview Links🔍 First Generation Visual Regression Test ResultsWhen a visual regression test fails (or has previously failed while working on this branch), its results can be found in the following URLs:
Deployed to Azure Blob Storage: If the changes are expected, update the |
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 was flagged my adobe secruity because the action isnt approved and no longer runs. we are safe to remove this.
cdransf
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.
✨
Description
previewreleases workflow needed to be updated with new version command now that we support two generations.fix:fix(feat:feat(and!:in the squash and merge commit message when PRs are merged in to mainsnapshotrelease script.Motivation and context
Let the people play with our code!
Author's checklist
Reviewer's checklist
patch,minor, ormajorfeaturesManual review test cases
Check preview release on NPM
Check snapshot release
node ./scripts/publish.js --tag snapshotenter your npm auth passwordCheck preview release post merge
fix:in the message