-
Notifications
You must be signed in to change notification settings - Fork 206
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
[DO NOT MERGE]Changeset testing #4959
Open
blunteshwar
wants to merge
33
commits into
main
Choose a base branch
from
changeset-testing
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Conversation
This file contains 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
Co-authored-by: [ Cassondra ] <castastrophe@users.noreply.github.com>
Co-authored-by: [ Cassondra ] <castastrophe@users.noreply.github.com>
…nents into feat/changesets
…nents into feat/changesets
🦋 Changeset detectedLatest commit: 1e440bf The changes in this PR will be included in the next version bump. This PR includes changesets to release 81 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
Tachometer resultsChromecolor-field permalinkbasic-test
Firefoxcolor-field permalinkbasic-test
|
Pull Request Test Coverage Report for Build 12064700090Details
💛 - Coveralls |
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
This PR migrates our release pipeline from using Lerna to Change Sets. The goal is to streamline the release process and leverage the flexibility and simplicity offered by Change Sets for versioning and publishing.
Changes Introduced
Added Change Sets
Integrated the Change Sets workflow for managing versioning and changelogs.
Configured Change Sets to align with our monorepo structure and release requirements.
Removed Lerna
Replaced Lerna commands and configurations with native npm/yarn workflows.
Removed Lerna-related dependencies and scripts from the codebase.
Updated CI/CD Pipeline
Modified the release pipeline to use Change Sets for version bumping and publishing.
Ensured compatibility with existing tooling and workflows.
Documentation Updates
Added guidance for using Change Sets in the contributing documentation.
Updated the release process documentation to reflect the removal of Lerna.
Motivation and context
How has this been tested?
Test case 1
Test case 2
Did it pass in Desktop?
Did it pass in Mobile?
Did it pass in iPad?
Screenshots (if appropriate)
Types of changes
Checklist
Best practices
This repository uses conventional commit syntax for each commit message; note that the GitHub UI does not use this by default so be cautious when accepting suggested changes. Avoid the "Update branch" button on the pull request and opt instead for rebasing your branch against
main
.