Version Packages #2394
Merged
Version Packages #2394
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
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
|
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 f8d7f18:
|
github-actions
bot
force-pushed
the
changeset-release/main
branch
from
f4efb6a
to
376e3dc
Compare
github-actions
bot
force-pushed
the
changeset-release/main
branch
2 times, most recently
from
5a39346
to
21abf1a
Compare
github-actions
bot
force-pushed
the
changeset-release/main
branch
from
21abf1a
to
f8d7f18
Compare
jandrade
added a commit
to Khan/wonder-blocks
that referenced
this pull request
Dec 6, 2021
## Summary: - Introduces `changesets` to the repository. - Adds a new workflow to handle releases. This will be triggered after the "release coordinator" (one of WB's admins) has approved the release (by hitting the `Merge` button). - Creates a new `release` script to handle releases using `changesets` instead of `lerna`. (keeping `lerna/publish` for backwards compatibility). More info about the new release process here: https://www.figma.com/file/xaYyzIuKLxqXAJVAl3y1S4/Wonder-Blocks-Web-Eng-process?node-id=50%3A400 <img width="2890" alt="Wonder Blocks Web Eng process" src="https://user-images.githubusercontent.com/843075/142078849-75ec28bf-98b5-4c55-b3f6-de2d63a4d90d.png"> NOTE: To include a regular PR in the release PR, the PR's author will need to run `yarn changesets` to include the changes for each package they have changed. More info about using it on this part of the process here: https://www.figma.com/file/xaYyzIuKLxqXAJVAl3y1S4/Wonder-Blocks-Web-Eng-process?node-id=81%3A549 Issue: WB-586 ## Test plan: Merge this PR and verify that the "Release PR" gets created after a contributor lands a PR (merges it into `master`). Here's an example of how the `Release PR` will look: emotion-js/emotion#2394 Author: jandrade Reviewers: kevinbarabash, jandrade Required Reviewers: Approved By: kevinbarabash Checks: ✅ codecov/project, ✅ Mixed content, ⚪️ Redirect rules, ⚪️ Header rules, ⚪️ Pages changed, ✅ gerald, ✅ lint_and_test (ubuntu-latest, 12), ⏭ dependabot, ✅ chromatic (ubuntu-latest, 12) Pull Request URL: #1221
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.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@emotion/react@11.4.1
Patch Changes
#2441
24557d9dThanks @garronej! - Exposed__unsafe_useEmotionCachewhich can be used to access the current Emotion's cache in an easier way than before. Using this might break 0-config SSR and is not recommended to be used unless there you know what you are doing and you are OK with the mentioned downside.#2424
cd25b62dThanks @tills13! - Use theme context when rendering components at all times. This removes a conditional usage of a React hook that could break Rules of Hooks in some scenarios.#2428
a69929d6Thanks @eps1lon! - Added display names to public React contexts in development builds. This helps to recognize them in React Developer Tools.Updated dependencies [
405af5ca]:@emotion/sheet@1.0.2
Patch Changes
405af5caThanks @layershifter! - Do not log failed rule insertions in the speedy mode for even more vendor-prefixed pseudo-elements/classes like:-moz-focus-inner,:-moz-focusring, and:-ms-clear.