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

Bump bitflags from 1.3.2 to 2.3.1 #238

Closed
wants to merge 1 commit into from

Conversation

dependabot[bot]
Copy link

@dependabot dependabot bot commented on behalf of github May 21, 2023

Bumps bitflags from 1.3.2 to 2.3.1.

Release notes

Sourced from bitflags's releases.

2.3.1

What's Changed

Full Changelog: bitflags/bitflags@2.3.0...2.3.1

2.3.0

Major changes

BitFlags trait deprecated in favor of Flags trait

This release introduces the Flags trait and deprecates the BitFlags trait. These two traits are semver compatible so if you have public API code depending on BitFlags you can move to Flags without breaking end-users. This is possible because the BitFlags trait was never publicly implementable, so it now carries Flags as a supertrait. All implementations of Flags additionally implement BitFlags.

The Flags trait is a publicly implementable version of the old BitFlags trait. The original BitFlags trait carried some macro baggage that made it difficult to implement, so a new Flags trait has been introduced as the One True Trait for interacting with flags types generically. See the the macro_free and custom_derive examples for more details.

Bits trait publicly exposed

The Bits trait for the underlying storage of flags values is also now publicly implementable. This lets you define your own exotic backing storage for flags. See the custom_bits_type example for more details.

What's Changed

Full Changelog: bitflags/bitflags@2.2.1...2.3.0

2.2.1

What's Changed

Full Changelog: bitflags/bitflags@2.2.0...2.2.1

2.2.0 (yanked)

What's Changed

New Contributors

Full Changelog: bitflags/bitflags@2.1.0...2.2.0

2.1.0

... (truncated)

Changelog

Sourced from bitflags's changelog.

2.3.1

What's Changed

Full Changelog: bitflags/bitflags@2.3.0...2.3.1

2.3.0

What's Changed

Full Changelog: bitflags/bitflags@2.2.1...2.3.0

2.2.1

What's Changed

Full Changelog: bitflags/bitflags@2.2.0...2.2.1

2.2.0

What's Changed

New Contributors

Full Changelog: bitflags/bitflags@2.1.0...2.2.0

2.1.0

What's Changed

New Contributors

Full Changelog: bitflags/bitflags@2.0.2...2.1.0

2.0.2

What's Changed

... (truncated)

Commits
  • cf01ab0 Merge pull request #358 from KodrAus/cargo/2.3.1
  • 3d0c558 prepare for 2.3.1 release
  • 32d406a Merge pull request #355 from KodrAus/fix/self-in-flags
  • 64fc276 fix up example feature
  • 8872a64 fix up clippy in CI
  • 748d88c fix up clippy lints and flag exprs referring to Self
  • a4b8c99 fix up custom bits test
  • 4aa03b8 add regression test for Self in flags values
  • 31d3e4a Merge pull request #352 from KodrAus/cargo/2.3.0
  • 51e8197 prepare for 2.3.0 release
  • Additional commits viewable in compare view

Dependabot compatibility score

Dependabot 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 rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot ignore this major version will 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 version will 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 dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Bumps [bitflags](https://github.com/bitflags/bitflags) from 1.3.2 to 2.3.1.
- [Release notes](https://github.com/bitflags/bitflags/releases)
- [Changelog](https://github.com/bitflags/bitflags/blob/main/CHANGELOG.md)
- [Commits](bitflags/bitflags@1.3.2...2.3.1)

---
updated-dependencies:
- dependency-name: bitflags
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot added dependencies Pull requests that update a dependency file rust Pull requests that update Rust code labels May 21, 2023
@dependabot @github
Copy link
Author

dependabot bot commented on behalf of github May 21, 2023

Dependabot tried to add @codingllama, @rosstimothy and @zmb3 as reviewers to this PR, but received the following error from GitHub:

POST https://api.github.com/repos/alexatcanva/teleport/pulls/238/requested_reviewers: 422 - Reviews may only be requested from collaborators. One or more of the users or teams you specified is not a collaborator of the alexatcanva/teleport repository. // See: https://docs.github.com/rest/reference/pulls#request-reviewers-for-a-pull-request

@dependabot @github
Copy link
Author

dependabot bot commented on behalf of github Jun 18, 2023

Superseded by #267.

@dependabot dependabot bot closed this Jun 18, 2023
@dependabot dependabot bot deleted the dependabot/cargo/bitflags-2.3.1 branch June 18, 2023 10:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file rust Pull requests that update Rust code
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants