build(deps): bump schemars from 0.8.22 to 1.2.2 - #59
Merged
Merged
Conversation
Greptile SummaryUpdates the schemars dependency to 1.2 and completes the associated protocol and OpenAPI migration. The custom conversation identifier schema uses the current public API, generated nested schemas are placed under OpenAPI components with valid references, and the contract documentation identifies the updated generator version. Confidence Score: 5/5Safe to merge. The previously reported build-breaking schema API usage is fully migrated, and the contract documentation now matches the resolved schemars version. No outstanding findings remain. Reviews (2): Last reviewed commit: "fix(deps): migrate schemars 0.8 to 1.2 A..." | Re-trigger Greptile |
Bumps [schemars](https://github.com/GREsau/schemars) from 0.8.22 to 1.2.2. - [Release notes](https://github.com/GREsau/schemars/releases) - [Changelog](https://github.com/GREsau/schemars/blob/master/CHANGELOG.md) - [Commits](GREsau/schemars@v0.8.22...v1.2.2) --- updated-dependencies: - dependency-name: schemars dependency-version: 1.2.2 dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
The 1.2 bump changes two things the workspace relied on:
- `JsonSchema::schema_name` returns `Cow<'static, str>`, and the
`r#gen` / `schema` modules are gone. `ConversationId`'s manual impl
now returns a borrowed name and builds its schema with the
`json_schema!` macro, which is the 1.x replacement for
`SchemaObject { instance_type, format, .. }`.
- `schema_for!` emits nested schemas under `$defs` (JSON Schema
2020-12, the dialect OpenAPI 3.1 uses) instead of draft 7's
`definitions`. The app-server's OpenAPI builder unwraps both keys and
rewrites either `$ref` prefix into `#/components/schemas/`, so
`ToolCallResponse` and the other nested models stay in the document.
The checked-in contract is regenerated (numeric `minimum` values lose
their `.0`, `required` ordering follows the structs) and the
`app-server.md` note names the version that generates it.
Co-authored-by: factory-droid[bot] <138933559+factory-droid[bot]@users.noreply.github.com>
echobt
force-pushed
the
dependabot/cargo/schemars-1.2.2
branch
from
September 16, 2026 13:37
fabc063 to
30b28f4
Compare
Contributor
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bumps schemars from 0.8.22 to 1.2.2.
Release notes
Sourced from schemars's releases.
... (truncated)
Changelog
Sourced from schemars's changelog.
... (truncated)
Commits
ed61863v1.2.2ae618c3Updatesynto v3 (#528)c072ea0docs: add missing attributes to table of contents (#517)015272fClippy fix (#512)944f727Bump bytes from 1.10.1 to 1.11.1 (#507)5ef5da1v1.2.14081b98Applyextend/transformattributes after any other attributes (#506)5bfec04v1.2.0f6b1f4cAddsmol_str03feature (#486)18826cdAdd test for changes from #452Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)