10000 chore: release v0.12.0 by SwabbieBosun · Pull Request #358 · bosun-ai/kwaak · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

chore: release v0.12.0 #358

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
wants to merge 1 commit into from
Closed

chore: release v0.12.0 #358

wants to merge 1 commit into from

Conversation

SwabbieBosun
Copy link
Contributor
@SwabbieBosun SwabbieBosun commented Feb 28, 2025 •
edited
Loading

🤖 New release

  • kwaak: 0.11.2 -> 0.12.0 (⚠ API breaking changes)

⚠ kwaak breaking changes

--- failure constructible_struct_adds_field: externally-constructible struct adds field ---

Description:
A pub struct constructible with a struct literal has a new pub field. Existing struct literals must be updated to include the new field.
        ref: https://doc.rust-lang.org/reference/expressions/struct-expr.html
       impl: https://github.com/obi1kenobi/cargo-semver-checks/tree/v0.39.0/src/lints/constructible_struct_adds_field.ron

Failed in:
  field GitConfiguration.generate_commit_message in /tmp/.tmpv4FLaD/kwaak/src/config/config.rs:267
Changelog

[0.12.0] - 2025-02-28

🚀 Features

🐛 Bug Fixes

⚙️ Miscellaneous Tasks

This PR was generated with release-plz.

@SwabbieBosun SwabbieBosun changed the title chore: release v0.11.3 chore: release v0.12.0 Feb 28, 2025
@SwabbieBosun SwabbieBosun force-pushed the release-plz-2025-02-28T17-05-06Z branch from f791ad4 to 874cad1 Compare February 28, 2025 19:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
1 participant
@SwabbieBosun
0