Skip to content

chore: release v0.3.2 - #50

Closed
github-actions[bot] wants to merge 1 commit into
mainfrom
release-plz-2026-07-31T11-48-46Z
Closed

chore: release v0.3.2#50
github-actions[bot] wants to merge 1 commit into
mainfrom
release-plz-2026-07-31T11-48-46Z

Conversation

@github-actions

@github-actions github-actions Bot commented Jul 31, 2026

Copy link
Copy Markdown
Contributor

🤖 New release

  • dit: 0.3.1 -> 0.3.2
Changelog

What's in 0.3.2

Bug Fixes

  • release: stop shipping an empty changelog on the tag-push route (#49)
  • ci: give release-plz the ALSA dev package that git_only now needs (#47)
  • ci: wake release-plz back up with git_only, and make idling loud (#46)

Chores

  • release v0.3.2 (#48)


This PR was generated with release-plz.


View with [code]smith Autofix with [code]smith
Need help on this PR? Tag @codesmith-bot with what you need. Autofix is disabled.

@filipeforattini

Copy link
Copy Markdown
Contributor

Closing as a duplicate produced by the release loop, not a real change.

release-plz release returned {"releases":[]} and created no v0.3.2 tag, so release-plz still considers 0.3.2 unreleased and regenerated the changelog — this diff adds a second ## What's in 0.3.2 section plus a Chores: release v0.3.2 (#48) entry, i.e. the changelog consuming its own release commit. Merging it would corrupt CHANGELOG.md.

main already carries the correct 0.3.2 section. Cutting the tag manually breaks the loop.

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.

1 participant