Conversation
added 2 commits
September 1, 2026 15:36
acasazza
added
the
ignore-for-release
✅ Deploy Preview for commercelayer-react-components ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
pfferrari
approved these changes
Sep 1, 2026
Contributor
|
🚀 🚀 🚀 |
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
3 participants
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.
Graduates the three packages from
5.0.0-beta.13to5.0.0.Produced with
lerna version 5.0.0 --no-private --force-publish, so all three moved together even though not all had changes of their own:@commercelayer/react-components@commercelayer/core-components@commercelayer/react-hooks-componentsThe commit touches four files and one line each — the three
package.jsonversion fields andlerna.json. Cross-package dependencies stay onworkspace:*and are resolved at publish time.Release state
The
v5.0.0tag is pushed, andrelease.yamlhas already opened the corresponding GitHub release as a draft (prerelease: false, correctly, since the tag carries nobeta.). Nothing is on npm yet:publish.yamlonly runs onrelease: published.Worth knowing before that draft is published:
publish.yamlrunspnpm -r publish --access publicwithout--tag nextfor a non-prerelease, so 5.0.0 becomeslateston npm, moving the default install away from 4.29.7.Note
This branch does not include
2818e850("create/update merge check") frommain, so 5.0.0 is cut from a tree one commit behind it. Flagged rather than silently merged in, since the tag is already pushed and rewriting it would be worse.