Skip to content

deps: update rust crate schemars to 0.9 #15

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
Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

deps: update rust crate schemars to 0.9 #15

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Jun 1, 2025 •
edited
Loading

This PR contains the following updates:

Package Type Update Change
schemars (source) dependencies minor 0.8 -> 0.9

Release Notes

GREsau/schemars (schemars)

v0.9.0

Compare Source

This version is identical to 1.0.0-alpha.18, but is available for those who are unable to unwilling to use a pre-release version.

Those upgrading from Schemars 0.8 may want to consult the migration guide, which also applies when migrating from 0.8 to 0.9.

v0.8.22

Compare Source

Fixed:
  • Fix compatibility with rust 2024 edition (#​378)

v0.8.21

Compare Source

Fixed:
  • Fix null default not being set on generated schemas (#​295 / #​296)

v0.8.20

Compare Source

Fixed:
  • Revert unintentional change in behaviour when combining default and required attributes (#​292)

v0.8.19

Compare Source

Fixed:
  • Regression that caused a compile error when deriving JsonSchema on an enum with no variants (#​287)

v0.8.18

Compare Source

Fixed:
  • Reduce size of MIR output (and improve release-mode compile time) when deriving JsonSchema on enums (#​266 / #​286)

v0.8.17

Compare Source

Changed:
  • Update to syn 2.0, which should improve compile times in many cases (#​281)

v0.8.16

Compare Source

Fixed:
  • Reduce size of MIR output (and improve release-mode compile time) when deriving JsonSchema

v0.8.15

Compare Source

Added:
  • Implement JsonSchema for BigDecimal from bigdecimal 0.4 (#​237)

v0.8.14

Compare Source

Added:
  • Add #[schemars(inner(...)] attribute to specify schema for array items (#​234)
Changed:
  • New optional associated function on JsonSchema trait: schema_id(), which is similar to schema_name(), but does not have to be human-readable, and defaults to the type name including module path. This allows schemars to differentiate between types with the same name in different modules/crates (#​62 / #​247)
Fixed:
  • Schemas for rust_decimal::Decimal and bigdecimal::BigDecimal now match how those types are serialized by default, i.e. as numeric strings (#​248)

v0.8.13

Compare Source

Added:
  • Implement JsonSchema for semver::Version (#​195 / #​238)
  • Include const generics in generated schema names (#​179 / #​239)
  • Implement JsonSchema for types from indexmap v2 (#​226 / #​240)
  • Implement JsonSchema for serde_json::value::RawValue (#​183)
Changed:
  • Minimum supported rust version is now 1.60.0

v0.8.12

Compare Source

Added:
  • Implement JsonSchema for smol_str::SmolStr (#​72)
Changed:
  • Change serde_json dependency min version to 1.0.25 (was 1.0.0) (#​192)

v0.8.11

Compare Source

Added:
  • Replace auto-inferred trait bounds with bounds specified in #[schemars(bound = "...")] attribute
Changed:
  • Derived JsonSchema now respects attributes on unit enum variants (#​152)
  • Minimum supported rust version is now 1.45.0

v0.8.10

Compare Source

  • Undo "Support generic default values in default attributes (#​83)" as it inadvertently introduced a breaking change (#​144)

v0.8.9

Compare Source

Added:
  • Support generic default values in default attributes (#​83)
    • This inadvertently introduced a breaking change and was removed in 0.8.10
  • Add missing MIT licence text for usage of code from regex_syntax crate (#​132)
  • Support uuid v1 and arrayvec 0.7 via feature flags uuid1 and arrayvec07 (#​142)
    • This also adds uuid08 and arrayvec05 feature flags for the previously supported versions of these crates. The existing uuid and arrayvec flags are still supported for backward-compatibility, but they are deprecated.
    • Similarly, indexmap1 feature flag is added, and indexmap flag is deprecated.

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate Renovate
Copy link
Author

renovate bot commented Jun 1, 2025 •
edited
Loading

⚠️ Artifact update problem

Renovate failed to update artifacts related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: Cargo.lock
Command failed: cargo update --config net.git-fetch-with-cli=true --manifest-path api/source/github-keys/Cargo.toml --package [email protected] --precise 0.9.0
warning: virtual workspace defaulting to `resolver = "1"` despite one or more workspace members being on edition 2021 which implies `resolver = "2"`
note: to keep the current resolver, specify `workspace.resolver = "1"` in the workspace root's manifest
note: to use the edition 2021 resolver, specify `workspace.resolver = "2"` in the workspace root's manifest
note: for more details see https://doc.rust-lang.org/cargo/reference/resolver.html#resolver-versions
error: failed to acquire package cache lock

Caused by:
  failed to open: /home/ubuntu/.cargo/.package-cache

Caused by:
  failed to create directory `/home/ubuntu/.cargo`

Caused by:
  File exists (os error 17)
File name: Cargo.lock
Command failed: cargo update --config net.git-fetch-with-cli=true --manifest-path libs/acl/Cargo.toml --package [email protected] --precise 0.9.0
warning: virtual workspace defaulting to `resolver = "1"` despite one or more workspace members being on edition 2021 which implies `resolver = "2"`
note: to keep the current resolver, specify `workspace.resolver = "1"` in the workspace root's manifest
note: to use the edition 2021 resolver, specify `workspace.resolver = "2"` in the workspace root's manifest
note: for more details see https://doc.rust-lang.org/cargo/reference/resolver.html#resolver-versions
error: failed to acquire package cache lock

Caused by:
  failed to open: /home/ubuntu/.cargo/.package-cache

Caused by:
  failed to create directory `/home/ubuntu/.cargo`

Caused by:
  File exists (os error 17)
File name: Cargo.lock
Command failed: cargo update --config net.git-fetch-with-cli=true --manifest-path libs/meta/Cargo.toml --package [email protected] --precise 0.9.0
warning: virtual workspace defaulting to `resolver = "1"` despite one or more workspace members being on edition 2021 which implies `resolver = "2"`
note: to keep the current resolver, specify `workspace.resolver = "1"` in the workspace root's manifest
note: to use the edition 2021 resolver, specify `workspace.resolver = "2"` in the workspace root's manifest
note: for more details see https://doc.rust-lang.org/cargo/reference/resolver.html#resolver-versions
error: failed to acquire package cache lock

Caused by:
  failed to open: /home/ubuntu/.cargo/.package-cache

Caused by:
  failed to create directory `/home/ubuntu/.cargo`

Caused by:
  File exists (os error 17)
File name: Cargo.lock
Command failed: cargo update --config net.git-fetch-with-cli=true --manifest-path libs/utils/cap/Cargo.toml --package [email protected] --precise 0.9.0
warning: virtual workspace defaulting to `resolver = "1"` despite one or more workspace members being on edition 2021 which implies `resolver = "2"`
note: to keep the current resolver, specify `workspace.resolver = "1"` in the workspace root's manifest
note: to use the edition 2021 resolver, specify `workspace.resolver = "2"` in the workspace root's manifest
note: for more details see https://doc.rust-lang.org/cargo/reference/resolver.html#resolver-versions
error: failed to acquire package cache lock

Caused by:
  failed to open: /home/ubuntu/.cargo/.package-cache

Caused by:
  failed to create directory `/home/ubuntu/.cargo`

Caused by:
  File exists (os error 17)
File name: Cargo.lock
Command failed: cargo update --config net.git-fetch-with-cli=true --manifest-path libs/utils/cops/Cargo.toml --package [email protected] --precise 0.9.0
warning: virtual workspace defaulting to `resolver = "1"` despite one or more workspace members being on edition 2021 which implies `resolver = "2"`
note: to keep the current resolver, specify `workspace.resolver = "1"` in the workspace root's manifest
note: to use the edition 2021 resolver, specify `workspace.resolver = "2"` in the workspace root's manifest
note: for more details see https://doc.rust-lang.org/cargo/reference/resolver.html#resolver-versions
error: failed to acquire package cache lock

Caused by:
  failed to open: /home/ubuntu/.cargo/.package-cache

Caused by:
  failed to create directory `/home/ubuntu/.cargo`

Caused by:
  File exists (os error 17)

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

automerge dependencies

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants