Skip to content

chore: release v0.4.0#53

Merged
jdx merged 1 commit intomainfrom
release-plz-2026-03-25T23-10-00Z
Mar 25, 2026
Merged

chore: release v0.4.0#53
jdx merged 1 commit intomainfrom
release-plz-2026-03-25T23-10-00Z

Conversation

@jdx
Copy link
Copy Markdown
Owner

@jdx jdx commented Mar 25, 2026

🤖 New release

  • pklr: 0.3.0 -> 0.4.0 (⚠ API breaking changes)

pklr breaking changes

--- failure enum_tuple_variant_field_added: pub enum tuple variant field added ---

Description:
An enum's exhaustive tuple variant has a new field, which has to be included when constructing or matching on this variant.
        ref: https://doc.rust-lang.org/reference/attributes/type_system.html#the-non_exhaustive-attribute
       impl: https://github.com/obi1kenobi/cargo-semver-checks/tree/v0.46.0/src/lints/enum_tuple_variant_field_added.ron

Failed in:
  field 2 of variant Expr::New in /tmp/.tmproz423/pklr/src/parser.rs:101
Changelog

0.4.0 - 2026-03-25

Fixed

  • extract converters from amends/extends base modules (#52)


This PR was generated with release-plz.

@gemini-code-assist
Copy link
Copy Markdown

Summary of Changes

Hello, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request automates the release of version 0.4.0 for the pklr crate. The update includes a critical bug fix concerning converter extraction from module extensions and introduces a backward-incompatible API change related to enum tuple variant fields. This release ensures improved functionality and reflects necessary structural adjustments within the library.

Highlights

  • Version Bump: The pklr crate has been updated from version 0.3.0 to 0.4.0.
  • API Breaking Change: This release introduces an API breaking change related to enum_tuple_variant_field_added, specifically affecting the Expr::New enum variant in pklr/src/parser.rs.
  • Bug Fix: Converters are now correctly extracted from amended/extended base modules, addressing an issue tracked in #52.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

@greptile-apps
Copy link
Copy Markdown

greptile-apps Bot commented Mar 25, 2026

Greptile Summary

This is an automated release PR generated by release-plz, bumping pklr from 0.3.0 to 0.4.0. The sole functional change driving this release (PR #52) fixes converter extraction from amends/extends base modules.

  • Version incremented from 0.3.00.4.0 in both Cargo.toml and Cargo.lock (consistent).
  • The minor-version bump correctly signals a breaking API change under semver pre-1.0 conventions: a new field was added to the Expr::New enum tuple variant (enum_tuple_variant_field_added), making exhaustive match patterns on that variant a compile error for downstream consumers.
  • CHANGELOG.md accurately documents the single fix included in this release.

Confidence Score: 5/5

  • This PR is safe to merge — it is a routine release bump with no logic changes.
  • All three changed files are mechanical release artifacts (version strings and changelog). The version bump correctly reflects the breaking change introduced in PR fix: extract converters from amends/extends base modules #52 using pre-1.0 semver conventions. No logic, dependencies, or configuration were altered beyond the version number itself.
  • No files require special attention.

Important Files Changed

Filename Overview
CHANGELOG.md Adds v0.4.0 entry documenting the breaking change fix for extracting converters from amends/extends base modules.
Cargo.toml Version bumped from 0.3.0 to 0.4.0; consistent with the breaking API change (enum tuple variant field added) and semver pre-1.0 conventions.
Cargo.lock Lock file updated to reflect the new pklr version (0.3.0 → 0.4.0); no dependency changes.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A["PR #52 merged\nextract converters from amends/extends"] --> B["release-plz detects\nbreaking change\n(enum_tuple_variant_field_added)"]
    B --> C["Minor version bump\n0.3.0 → 0.4.0\n(pre-1.0 semver: minor = breaking)"]
    C --> D["Cargo.toml updated\nversion = '0.4.0'"]
    C --> E["Cargo.lock updated\npklr 0.4.0"]
    C --> F["CHANGELOG.md updated\nv0.4.0 entry added"]
    D & E & F --> G["Release PR #53\nReady to merge"]
Loading

Reviews (1): Last reviewed commit: "chore: release v0.4.0" | Re-trigger Greptile

Copy link
Copy Markdown

@gemini-code-assist gemini-code-assist Bot left a comment

Choose a reason for hiding this comment

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

Code Review

This pull request updates the project version from 0.3.0 to 0.4.0 across Cargo.toml, Cargo.lock, and CHANGELOG.md. The changelog entry for version 0.4.0 currently lists a breaking API change under 'Fixed', which should be re-categorized under a 'Changed' section to adhere to the 'Keep a Changelog' standard.

Comment thread CHANGELOG.md
Comment on lines +12 to +14
### Fixed

- extract converters from amends/extends base modules ([#52](https://github.com/jdx/pklr/pull/52))
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

medium

The pull request description indicates that this release contains breaking API changes. According to the Keep a Changelog standard, which this project follows, breaking changes should be listed under a Changed section, not Fixed.

Please update the changelog to accurately reflect the breaking change and categorize the items correctly. This helps users understand the impact of upgrading.

Suggested change
### Fixed
- extract converters from amends/extends base modules ([#52](https://github.com/jdx/pklr/pull/52))
### Changed
- **BREAKING CHANGE**: The `Expr::New` enum variant has a new field.
- Fixed: extract converters from amends/extends base modules ([#52](https://github.com/jdx/pklr/pull/52)).

@jdx jdx merged commit a36f8f4 into main Mar 25, 2026
6 checks passed
@jdx jdx deleted the release-plz-2026-03-25T23-10-00Z branch March 25, 2026 23:17
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