Skip to content

chore: release 0.6.3 - #82

Closed
github-actions[bot] wants to merge 1 commit into
masterfrom
release-v0.6.3
Closed

chore: release 0.6.3#82
github-actions[bot] wants to merge 1 commit into
masterfrom
release-v0.6.3

Conversation

@github-actions

@github-actions github-actions Bot commented Nov 25, 2020

Copy link
Copy Markdown
Contributor

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

0.6.3 (2020-11-27)

Bug Fixes


This PR was generated with Release Please.

@ryzokuken

Copy link
Copy Markdown
Contributor

Should we wait for #78?

@cclauss

cclauss commented Nov 27, 2020

Copy link
Copy Markdown
Contributor

Add #83 for Python 3.9?

@ryzokuken

Copy link
Copy Markdown
Contributor

Doesn't it do it automatically? Maybe it will make a new PR if we close this one.

@targos

targos commented Nov 27, 2020

Copy link
Copy Markdown
Member

There's nothing to "add" to this PR. The release is cut when we merge to master, including everything that is on master at that point. #83 just won't be in the changelog because the commit message doesn't have a valid format.

@ryzokuken

ryzokuken commented Nov 28, 2020

Copy link
Copy Markdown
Contributor

Aw, shucks. I shouldn't have merged it as-is. Should we rename the commit or manually update the CHANGELOG?

@gengjiawen

Copy link
Copy Markdown
Member

Aw, shucks. I shouldn't have merged it as-is. Should we rename the commit or manually update the CHANGELOG?

@targos Is it okay we fix the commit msg and force push ?

@targos

targos commented Nov 30, 2020

Copy link
Copy Markdown
Member

I think it's a bit late for a force push. We can try to update the changelog in this PR just before we merge.

@github-actions github-actions Bot closed this Dec 16, 2020
@gengjiawen
gengjiawen deleted the release-v0.6.3 branch December 16, 2020 08:53
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.

4 participants