Publish Next Version #393
Merged
Publish Next Version #393
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}
github-actions
bot
force-pushed
the
changeset-release/main
branch
from
1a03989 to
04bba17
Compare
github-actions
bot
force-pushed
the
changeset-release/main
branch
from
04bba17 to
0e558aa
Compare
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
pleasantest@1.6.0
Minor Changes
19c7cbbThanks @renovate! - Update puppeteer to 13.1.2Patch Changes
#391
55a7d42Thanks @renovate! - Updatedom-accessibility-apito 0.5.11<input type="number" />now maps to rolespinbutton(wastextboxbefore).This is technically a breaking change for users which depended on the incorrect behavior of
getAccessibilityTreewithinput[type="number"]previously mapping totextbox.