Skip to content

chore: release v0.4.35 - #746

Merged
KodrAus merged 2 commits into
mainfrom
release-plz-2026-10-28T19-09-16Z
Oct 30, 2026
Merged

KodrAus merged 2 commits into
mainfrom
release-plz-2026-10-28T19-09-16Z

Conversation

@github-actions

@github-actions github-actions Bot commented Oct 28, 2026 •

Copy link
Copy Markdown
Contributor

🤖 New release

  • log: 0.4.34 -> 0.4.35
Changelog

0.4.35 - 2026-10-30

Other

  • run fmt
  • simplify some crate release tasks for easier automation
  • Disable release-plz semver check
  • Fix Zizmor lints
  • Setup trusted publishing
  • Change default branch name to main
  • Add simple concurrency limits
  • Bump actions/checkout to 7.0.1 hash
  • Replace dtolnay/rust-toolchain with rustup
  • 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


This PR was generated with release-plz.

@KodrAus

KodrAus commented Oct 28, 2026

Copy link
Copy Markdown
Contributor

Looks like this is working now. Should we try push a release through and make sure the whole thing works @Kobzol?

@Kobzol

Kobzol commented Oct 28, 2026

Copy link
Copy Markdown
Member

Up to you. It seems that the # remember to update html_root_url comment is being removed by release-plz, probably it should be moved above the version line, rather than at its end. And also html_root_url should be updated (by pushing to this branch.. that might be a bit annoying, not sure how it was handled before).

@KodrAus

KodrAus commented Oct 28, 2026

Copy link
Copy Markdown
Contributor

We should just remove the explicit html_root_url. It hasn’t been necessary for a long time. I’ll fix that.

Comment thread CHANGELOG.md Outdated
- 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

@Thomasdezeeuw Thomasdezeeuw Oct 29, 2026 •

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

View changes since the review

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

@github-actions
github-actions Bot force-pushed the release-plz-2026-10-28T19-09-16Z branch from c8e75f6 to a715f17 Compare October 30, 2026 00:16
@KodrAus
KodrAus merged commit 75fcb86 into main Oct 30, 2026
27 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants