-
Notifications
You must be signed in to change notification settings - Fork 2.9k
chore(web-components): run manually bump to fix failed CI release #26498
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
chore(web-components): run manually bump to fix failed CI release #26498
Conversation
📊 Bundle size report🤖 This report was generated against 1322f3f962e8a850fe104cc2ba9b12b2bc2f2842 |
|
This pull request is automatically built and testable in CodeSandbox. To see build info of the built libraries, click here or the icon next to each commit SHA. Latest deployment of this branch, based on commit b170f3b:
|
Asset size changesSize Auditor did not detect a change in bundle size for any component! Baseline commit: 1322f3f962e8a850fe104cc2ba9b12b2bc2f2842 (build) |
…crosoft#26498) * chore: run manually bump to fix failed CI release * generate changefile
…crosoft#26498) * chore: run manually bump to fix failed CI release * generate changefile
…crosoft#26498) * chore: run manually bump to fix failed CI release * generate changefile
…6498) * chore: run manually bump to fix failed CI release * generate changefile
…crosoft#26498) * chore: run manually bump to fix failed CI release * generate changefile
…crosoft#26498) * chore: run manually bump to fix failed CI release * generate changefile
…crosoft#26498) * chore: run manually bump to fix failed CI release * generate changefile
…6498) * chore: run manually bump to fix failed CI release * generate changefile
…6498) * chore: run manually bump to fix failed CI release * generate changefile
…6498) * chore: run manually bump to fix failed CI release * generate changefile
…6498) * chore: run manually bump to fix failed CI release * generate changefile
…6498) * chore: run manually bump to fix failed CI release * generate changefile
…6498) * chore: run manually bump to fix failed CI release * generate changefile
…6498) * chore: run manually bump to fix failed CI release * generate changefile
…6498) * chore: run manually bump to fix failed CI release * generate changefile
…6498) * chore: run manually bump to fix failed CI release * generate changefile
Previous Behavior
Automated nightly releases have been blocked since Dec 26th, which created lot of on hold pipelines.
Enabling those this week caused probably npm release parallel race conditions leading into not release pipeline failing

New Behavior
I manually ran bump on local machine via command
yarn beachball bump -b origin/web-components-v3 --access public --no-fetch --no-publish --no-push --no-git-tags --verbose --config ./scripts/beachball/release-web-components.config.jsThis PR are changes created by bump. This should hopefully resolve any upcoming releases
Related Issue(s)