Skip to content

chore: release 1.31.1 - #611

Merged
Trott merged 1 commit into
mainfrom
release-v1.31.1
Mar 17, 2022
Merged

Trott merged 1 commit into
mainfrom
release-v1.31.1

Conversation

@github-actions

Copy link
Copy Markdown
Contributor

🤖 I have created a release *beep* *boop*

1.31.1 (2022-03-17)

Bug Fixes

  • comply with markdown style guidelines (13d7b2d)

This PR was generated with Release Please. See documentation.

@Trott
Trott merged commit 4d28185 into main Mar 17, 2022
@Trott
Trott deleted the release-v1.31.1 branch March 17, 2022 12:24
@github-actions

Copy link
Copy Markdown
Contributor Author

@Trott
Trott restored the release-v1.31.1 branch March 17, 2022 12:32
@targos
targos deleted the release-v1.31.1 branch March 17, 2022 12:55
@targos

targos commented Mar 17, 2022

Copy link
Copy Markdown
Member

@Trott I just saw you deleted and then restored the branch. Any reason for keeping it?

@Trott

Trott commented Mar 17, 2022

Copy link
Copy Markdown
Member

@Trott I just saw you deleted and then restored the branch. Any reason for keeping it?

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!

@Trott

Trott commented Mar 17, 2022

Copy link
Copy Markdown
Member

(I published manually to npm.)

@Trott

Trott commented Mar 17, 2022

Copy link
Copy Markdown
Member

(I published manually to npm.)

(From the tag.)

@targos

targos commented Mar 17, 2022

Copy link
Copy Markdown
Member

npm publish is not setup yet: #511

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants