chore: release 7.3.8 #486
Merged
chore: release 7.3.8 #486
Conversation
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
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
Release Manager
|
github-actions
bot
force-pushed
the
release-please--branches--main
branch
2 times, most recently
from
84bfde8 to
57eb908
Compare
github-actions
bot
force-pushed
the
release-please--branches--main
branch
from
57eb908 to
0a8ce31
Compare
|
CI failures here are because of the way we are calling |
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.
🤖 I have created a release beep boop
7.3.8 (2022-10-04)
Bug Fixes
d8ef32c#383 add support for node.js esm auto exports (fix: add support for node.js esm auto exports #383) (@MylesBorins)Documentation
7209b14#477 update range.js comments to clarify the caret ranges examples (docs: update range.js comments to clarify the caret ranges examples #477) (@amitse)This PR was generated with Release Please. See documentation.