Skip to content
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

Update Rust crate bitflags to 1.3.2 #61

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Jun 1, 2023

This PR contains the following updates:

Package Type Update Change
bitflags dependencies minor 1.0 -> 1.3.2

Release Notes

bitflags/bitflags (bitflags)

v1.3.2

Compare Source

  • Allow non_snake_case in generated flags types (#​256)

v1.3.1

Compare Source

  • Revert unconditional #[repr(transparent)] (#​252)

v1.3.0

Compare Source

This release bumps the Minimum Supported Rust Version to 1.46.0

  • Add #[repr(transparent)] (#​187)

  • End empty doc comment with full stop (#​202)

  • Fix typo in crate root docs (#​206)

  • Document from_bits_unchecked unsafety (#​207)

  • Let is_all ignore extra bits (#​211)

  • Allows empty flag definition (#​225)

  • Making crate accessible from std (#​227)

  • Make from_bits a const fn (#​229)

  • Allow multiple bitflags structs in one macro invocation (#​235)

  • Add named functions to perform set operations (#​244)

  • Fix typos in method docs (#​245)

  • Modernization of the bitflags macro to take advantage of newer features and 2018 idioms (#​246)

  • Fix regression (in an unreleased feature) and simplify tests (#​247)

  • Use Self and fix bug when overriding stringify! (#​249)

v1.2.1

Compare Source

  • Remove extraneous #[inline] attributes (#​194)

v1.2.0

Compare Source

  • Fix typo: {Lower, Upper}Exp - {Lower, Upper}Hex (#​183)

  • Add support for "unknown" bits (#​188)

v1.1.0

Compare Source

This is a re-release of 1.0.5, which was yanked due to a bug in the RLS.

v1.0.5

Compare Source

  • Use compiletest_rs flags supported by stable toolchain (#​171)

  • Put the user provided attributes first (#​173)

  • Make bitflags methods const on newer compilers (#​175)


Configuration

📅 Schedule: Branch creation - "before 3am on the first day of the month" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

Rebasing: Whenever PR is behind base branch, 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 bot force-pushed the renovate/bitflags-1.x branch from e22c13f to e8b93ee Compare May 1, 2024 09:52
@renovate renovate bot changed the title Update Rust crate bitflags to 1.3 Update Rust crate bitflags to 1.3.2 May 1, 2024
Copy link
Author

renovate bot commented May 1, 2024

⚠ Artifact update problem

Renovate failed to update an artifact 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: native/Cargo.lock
Command failed: cargo update --config net.git-fetch-with-cli=true --manifest-path native/src/rusqlite/Cargo.toml --package bitflags@1.0.4 --precise 1.3.2
error: package ID specification `bitflags@1.0.4` did not match any packages
Did you mean one of these?

  bitflags@1.3.2

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.

0 participants