Skip to content

chore(deps): update cargo-semver-checks to v0.40.0 #15282

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.

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

Merged
merged 1 commit into from
Mar 8, 2025

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Mar 8, 2025

This PR contains the following updates:

Package Update Change
cargo-semver-checks minor 0.39.0 -> 0.40.0

Release Notes

obi1kenobi/cargo-semver-checks (cargo-semver-checks)

v0.40.0

Compare Source

In this release

  • 21 new lints, for a total of 148!
  • Spotlight: #[doc(hidden)] and sealed lints

This release requires Rust 1.83+ both to install (MSRV) and at runtime. Future releases will require Rust 1.84+.

Spotlight: #[doc(hidden)] and sealed lints

When is "this trait can be implemented" part of the trait's public API?

At a high level, the answer is: when writing an impl of that trait for our own type doesn't require using any #[doc(hidden)] items. But you've been following cargo-semver-checks long enough to know the full answer is much more complex. And getting the right answer here affects the correctness of a ton of lints!

Good news! This cargo-semver-checks release ships with a much more sophisticated system for analyzing whether traits can be implemented or are instead "sealed." The new system is more thorough, more nuanced, and faster to boot!

Read more about it here: https://predr.ag/blog/when-is-trait-can-be-implemented-public-api/

New lints

We added new 21 lints across several categories. Some of the new lints are error-by-default, while others are merely warnings meant to flag changes deserving closer review.

API breakage:

  • static_became_unsafe

ABI and FFI breakage due to changed repr(C) type layout:

  • repr_c_enum_struct_variant_fields_reordered
  • repr_c_plain_struct_fields_reordered

Item deprecations, which cause lints in downstream use:

  • function_marked_deprecated
  • global_value_marked_deprecated
  • macro_marked_deprecated
  • proc_macro_marked_deprecated
  • struct_field_marked_deprecated
  • trait_associated_const_marked_deprecated
  • trait_associated_type_marked_deprecated
  • trait_marked_deprecated
  • trait_method_marked_deprecated
  • type_associated_const_marked_deprecated
  • type_method_marked_deprecated

Code behavior changes, such as changes to sort order of existing types:

  • partial_ord_enum_struct_variant_fields_reordered
  • partial_ord_enum_variants_reordered
  • partial_ord_struct_fields_reordered

Compatibility risks, such as changes that may require a SemVer major bump to revert, or may otherwise represent unintended API changes without being SemVer-major themselves:

  • pub_api_sealed_trait_became_unconditionally_sealed
  • unconditionally_sealed_trait_became_pub_api_sealed
  • unconditionally_sealed_trait_became_unsealed
  • pub_api_sealed_trait_became_unsealed

Thanks to @​Frank-III, @​geetanshjuneja, and @​lovelindhoni for contributing lints to this release!

All merged PRs

New Contributors

Full Changelog: obi1kenobi/cargo-semver-checks@v0.39.0...v0.40.0


Configuration

📅 Schedule: Branch creation - "* * * * *" (UTC), 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.

@rustbot
Copy link
Collaborator

rustbot commented Mar 8, 2025

r? @weihanglo

rustbot has assigned @weihanglo.
They will have a look at your PR within the next two weeks and either review your PR or reassign to another reviewer.

Use r? to explicitly pick a reviewer

@rustbot rustbot added A-infrastructure Area: infrastructure around the cargo repo, ci, releases, etc. S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. labels Mar 8, 2025
@weihanglo weihanglo added this pull request to the merge queue Mar 8, 2025
Merged via the queue into master with commit 0fe0d89 Mar 8, 2025
21 checks passed
@weihanglo weihanglo deleted the renovate/cargo-semver-checks-0.x branch March 8, 2025 19:10
@epage
Copy link
Contributor

epage commented Mar 8, 2025

It worked!

bors added a commit to rust-lang-ci/rust that referenced this pull request Mar 14, 2025
Update cargo

15 commits in ab1463d632528e39daf35f263e10c14cbe590ce8..6cf8267012570f63d6b86e85a2ae5627de52df9e
2025-03-08 01:45:05 +0000 to 2025-03-14 15:25:36 +0000
- feat(package): add --exclude-lockfile flag (rust-lang/cargo#15234)
- Redox OS is part of the unix family (rust-lang/cargo#15307)
- docs(ref): Mention `x.y.*` as a kind of version requirement to avoid. (rust-lang/cargo#15310)
- fix(run): Disambiguate bins from different packages that share a name (rust-lang/cargo#15298)
- cargo vendor: Add context which workspace failed to resolve (rust-lang/cargo#15297)
- docs(ref): Note that target-edition is deprecated (rust-lang/cargo#15292)
- refactor(toml): Centralize target descriptions (rust-lang/cargo#15291)
- docs(refs): Add `unsafe` to `extern` while using build scripts in Cargo Book (rust-lang/cargo#15294)
- Replace unmaintained humantime crate with jiff (rust-lang/cargo#15290)
- Add terminal integration via ANSI OSC 9;4 sequences (rust-lang/cargo#14615)
- feat: add completions for add --path (rust-lang/cargo#15288)
- Allow `term.progress.when` to default (rust-lang/cargo#15287)
- docs: spelling and grammar fixes (rust-lang/cargo#15284)
- chore(deps): update cargo-semver-checks to v0.40.0 (rust-lang/cargo#15282)
- Typo fixes (rust-lang/cargo#15280)

r? ghost
@rustbot rustbot added this to the 1.87.0 milestone Mar 15, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-infrastructure Area: infrastructure around the cargo repo, ci, releases, etc. S-waiting-on-review Status: Awaiting review from the assignee but also interested parties.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants