Repository navigation
fix(CI): exclude private packages from prerelease versioning - #12724
rebeccaalpert merged 1 commit into
Conversation
|
No actionable comments were generated in the recent review. WalkthroughThe prerelease preparation command now passes ChangesPrerelease versioning
Estimated code review effort: 2 (Simple) | ~5 minutes Change: Bug fix Possibly related PRs
Suggested reviewers: Merge Risk:
|
|
Preview: https://pf-react-pr-12724.surge.sh A11y report: https://pf-react-pr-12724-a11y.surge.sh |
|
Your changes have been released in: - @patternfly/react-charts@8.7.1-prerelease.0
Thanks for your contribution! 🎉 |
What: Fixes the prerelease preparation failure after #12694, as part of FELT-143.
Lerna attempted to create
demo-app-ts@6.5.0-prerelease.139, which already exists from a Felt release. Add--no-privateto prerelease versioning so private integration/demo packages do not create release tags. Update the regression test to require the flag.Validation
--no-privateavoids the collision while selecting all 10 public React packages.Additional issues: The failed release stopped before pushing release updates or publishing to npm. No existing tags are deleted or moved. Stable Promote remains disabled and unchanged.
Summary by CodeRabbit