Repository navigation
chore: release v0.4.35 - #746
Conversation
|
Looks like this is working now. Should we try push a release through and make sure the whole thing works @Kobzol? |
|
Up to you. It seems that the |
|
We should just remove the explicit |
| - Fix pin hash for `actions/checkout` 6.0.2 | ||
| - clean up workflow jobs | ||
| - remove win32 build target | ||
| - split MSRV used to build from MSRV used to test |
There was a problem hiding this comment.
I think we should do manual filtering of these change logs. For example the setting up of release-plz is not interesting to people who read this change log to determine what changed code wise to determine if they should update or not.
There was a problem hiding this comment.
I've tried updating the changelog manually, just to see what happens. It seems like we could push a commit to the branches release-plz makes to include notes and filter commits
There was a problem hiding this comment.
Yeah, you can push to this branch, that's expected. Though I think that if something gets pushed to main in the meantime, release-plz will repush to the PR, or open a new one.
c8e75f6 to
a715f17
Compare
🤖 New release
log: 0.4.34 -> 0.4.35Changelog
This PR was generated with release-plz.