chore: release v0.3.0 by jdx · Pull Request #50 · jdx/pklr

jdx · 2026-03-24T21:24:49Z

🤖 New release

pklr: 0.2.2 -> 0.3.0 (⚠ API breaking changes)

⚠ `pklr` 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.46.0/src/lints/constructible_struct_adds_field.ron

Failed in:
  field ObjectSource.type_name in /tmp/.tmpJNeWZq/pklr/src/value.rs:20

Changelog

0.3.0 - 2026-03-24

Added

implement output.renderer.converters support (#49)

This PR was generated with release-plz.

gemini-code-assist · 2026-03-24T21:25:02Z

Summary of Changes

Hello, I'm Gemini Code Assist¹! 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 serves as a release chore, updating the pklr package to its new major version 0.3.0. This release incorporates a significant new feature, output.renderer.converters support, and includes API breaking changes that require attention from consumers.

Highlights

pklr package release: The pklr package has been updated to version 0.3.0, introducing API breaking changes and implementing support for output.renderer.converters.

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.

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 · 2026-03-24T21:26:05Z

Greptile Summary

This is an automated release PR generated by release-plz, bumping pklr from 0.2.2 to 0.3.0. The version increment correctly follows semver convention for a pre-1.0 crate with a breaking API change (minor version bump). The sole functional change shipped in this release is output.renderer.converters support from PR #49.

Key points:

Version bump in Cargo.toml and Cargo.lock from 0.2.2 → 0.3.0 is correct given the confirmed breaking change.
The CHANGELOG.md entry for v0.3.0 is missing documentation of the breaking change (ObjectSource gains a new pub field type_name), which was detected by cargo-semver-checks and noted in the PR description. Downstream users reading the changelog will not be warned that struct-literal constructions of ObjectSource need to be updated.

Confidence Score: 4/5

Safe to merge; only concern is a missing breaking-change note in the CHANGELOG.
The version bump is mechanically correct and all three files are consistent. The only gap is that the documented changelog entry does not surface the confirmed API breaking change for users upgrading.
CHANGELOG.md — should document the ObjectSource.type_name breaking change.

Important Files Changed

Filename	Overview
CHANGELOG.md	Adds v0.3.0 entry with an `Added` section, but the confirmed API breaking change (`ObjectSource.type_name` field addition) is not documented.
Cargo.toml	Version bumped from `0.2.2` to `0.3.0`; correct minor-version bump for a pre-1.0 crate with a breaking change.
Cargo.lock	Lock file updated to reflect the new `pklr` version `0.3.0`; no other dependency changes.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[release-plz triggers release] --> B[Bump version 0.2.2 → 0.3.0]
    B --> C[Update Cargo.toml]
    B --> D[Update Cargo.lock]
    B --> E[Update CHANGELOG.md]
    C & D & E --> F[PR #50 merged]
    F --> G[Publish pklr v0.3.0 to crates.io]
    G --> H{Downstream users upgrade}
    H -->|Read CHANGELOG| I[See only 'Added: converters support']
    H -->|Compile code| J[⚠ ObjectSource struct literal breaks if type_name missing]

_{Reviews (1): Last reviewed commit: "chore: release v0.3.0" | Re-trigger Greptile}

greptile-apps · 2026-03-24T21:26:08Z

+## [0.3.0](https://github.com/jdx/pklr/compare/v0.2.2...v0.3.0) - 2026-03-24
+
+### Added
+
+- implement output.renderer.converters support ([#49](https://github.com/jdx/pklr/pull/49))


Breaking change not documented in CHANGELOG

The PR description and cargo-semver-checks output confirm there is an API breaking change in this release — a new pub field type_name was added to the ObjectSource struct in src/value.rs, which is a source-incompatible change for users constructing that struct with literal syntax.

However, the v0.3.0 changelog entry only includes an ### Added section and makes no mention of this breaking change. Downstream users relying on CHANGELOG.md to understand upgrade requirements will not be aware that their code may fail to compile after upgrading.

Consider adding a ### Breaking Changes (or ### Changed) section, for example:

Suggested change

## [0.3.0](https://github.com/jdx/pklr/compare/v0.2.2...v0.3.0) - 2026-03-24

### Added

- implement output.renderer.converters support ([#49](https://github.com/jdx/pklr/pull/49))

## [0.3.0](https://github.com/jdx/pklr/compare/v0.2.2...v0.3.0) - 2026-03-24

### Breaking Changes

- `ObjectSource` struct has a new `pub` field `type_name`; existing struct-literal constructions must be updated ([#49](https://github.com/jdx/pklr/pull/49))

### Added

- implement output.renderer.converters support ([#49](https://github.com/jdx/pklr/pull/49))

gemini-code-assist

Code Review

This pull request updates the project version to 0.3.0 across Cargo.toml, Cargo.lock, and CHANGELOG.md, and adds an entry for output.renderer.converters support. The primary feedback is to document a breaking API change related to the ObjectSource struct in the CHANGELOG.md under a new Changed section, adhering to Keep a Changelog conventions.

gemini-code-assist · 2026-03-24T21:26:26Z

+### Added
+
+- implement output.renderer.converters support ([#49](https://github.com/jdx/pklr/pull/49))


This release includes breaking API changes, as noted in the pull request description. It would be beneficial for users to have these documented in the changelog. According to Keep a Changelog conventions, breaking changes are typically listed under a Changed section.

I suggest adding a Changed section to highlight the breaking change related to the ObjectSource struct.

Suggested change

### Added

- implement output.renderer.converters support ([#49](https://github.com/jdx/pklr/pull/49))

### Added

- implement output.renderer.converters support ([#49](https://github.com/jdx/pklr/pull/49))

### Changed

- **(breaking)** The `ObjectSource` struct has a new public field `type_name`. This is an API breaking change for consumers constructing this struct directly.

chore: release v0.3.0

0de2122

greptile-apps Bot reviewed Mar 24, 2026

View reviewed changes

gemini-code-assist Bot reviewed Mar 24, 2026

View reviewed changes

jdx merged commit df91408 into main Mar 24, 2026
6 checks passed

jdx deleted the release-plz-2026-03-24T21-24-47Z branch March 24, 2026 21:30

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

chore: release v0.3.0#50

chore: release v0.3.0#50
jdx merged 1 commit intomainfrom
release-plz-2026-03-24T21-24-47Z

jdx commented Mar 24, 2026

Uh oh!

gemini-code-assist Bot commented Mar 24, 2026

Uh oh!

greptile-apps Bot commented Mar 24, 2026

Uh oh!

greptile-apps Bot Mar 24, 2026

Uh oh!

gemini-code-assist Bot left a comment

Uh oh!

gemini-code-assist Bot Mar 24, 2026

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

		### Added

		- implement output.renderer.converters support ([#49](https://github.com/jdx/pklr/pull/49))

Conversation

jdx commented Mar 24, 2026

🤖 New release

⚠ pklr breaking changes

0.3.0 - 2026-03-24

Added

Uh oh!

gemini-code-assist Bot commented Mar 24, 2026

Summary of Changes

Highlights

Footnotes

Uh oh!

greptile-apps Bot commented Mar 24, 2026

Greptile Summary

Confidence Score: 4/5

Important Files Changed

Flowchart

Uh oh!

greptile-apps Bot Mar 24, 2026

Choose a reason for hiding this comment

Uh oh!

gemini-code-assist Bot left a comment

Choose a reason for hiding this comment

Code Review

Uh oh!

gemini-code-assist Bot Mar 24, 2026

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

⚠ `pklr` breaking changes