chore(core): add publish guards and auto-publish workflow#285
Open
harishsundar-okta wants to merge 1 commit into
Open
chore(core): add publish guards and auto-publish workflow#285harishsundar-okta wants to merge 1 commit into
harishsundar-okta wants to merge 1 commit into
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #285 +/- ##
=======================================
Coverage 89.41% 89.41%
=======================================
Files 159 159
Lines 13334 13334
Branches 1828 1750 -78
=======================================
Hits 11923 11923
Misses 1411 1411 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds automated version parity enforcement, pre-flight publish guards, and an auto-publish workflow to eliminate manual publish steps and prevent version drift between core and react packages.
Why
The current npm publish process has three gaps: publishing is manual-only (risk of forgetting or publishing stale versions), there's no early check for duplicate versions on npm (wasting CI time before failing), and nothing prevents core and react package versions from drifting apart (causing broken consumer installs).
What
Packages
packages/corepackages/reactexamplesReferences
Testing
Checklist
Contributing