Repository navigation
chore: release 1.31.1 - #611
Merged
Merged
Conversation
Trott
approved these changes
Mar 17, 2022
Contributor
Author
|
🤖 Release is at https://github.com/nodejs/node-core-utils/releases/tag/v1.31.1 🌻 |
Member
|
@Trott I just saw you deleted and then restored the branch. Any reason for keeping it? |
Member
release-please wasn't publishing to npm (maybe it's not supposed to?) and a probably-unrelated error in a GitHub Action somewhere made me wonder if that was why. You can delete it again if it's the right thing to do! |
Member
|
(I published manually to npm.) |
Member
(From the tag.) |
Member
|
npm publish is not setup yet: #511 |
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
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*
1.31.1 (2022-03-17)
Bug Fixes
This PR was generated with Release Please. See documentation.