Bump hashbrown from 0.11.2 to 0.12.1 #8201
Merged
Conversation
This file contains 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
![dependabot[bot]](https://avatars.githubusercontent.com/in/29110?s=60&v=4){kind=small}
Bumps [hashbrown](https://github.com/rust-lang/hashbrown) from 0.11.2 to 0.12.1. - [Release notes](https://github.com/rust-lang/hashbrown/releases) - [Changelog](https://github.com/rust-lang/hashbrown/blob/master/CHANGELOG.md) - [Commits](rust-lang/hashbrown@v0.11.2...v0.12.1) --- updated-dependencies: - dependency-name: hashbrown dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
bot
added
the
dependencies
|
Thank you for opening a new pull request. Before your PR can be merged it will first need to pass continuous integration tests and be reviewed. Sometimes the review process can be slow, so please be patient. While you're waiting, please feel free to review other open PRs. While only a subset of people are authorized to approve pull requests for merging, everyone is encouraged to review open pull requests. Doing reviews helps reduce the burden on the core team and helps make the project's code better for everyone. One or more of the the following people are requested to review this:
|
mtreinish
approved these changes
Jun 17, 2022
Pull Request Test Coverage Report for Build 2517632787
💛 - Coveralls |
mtreinish
added a commit
to mtreinish/qiskit-core
that referenced
this pull request
Jul 11, 2022
In Qiskit#8201 I added a release note as part of the PR which documented the change in behavior. However, I accidentally committed this file in the wrong location (by running reno new outside of the repo root). This meant the file was never actually included in the release notes for the 0.21.0 release. This commit corrects this oversight and moves it back to the proper location. However, since this isn't my first time making this mistake and I can expect that others will make it too in the future. This commit also adds a new script to detect this and raise an error when release notes are present outside of the proper location. By running this as part of lint jobs we'll block this mistake from happening again.
mtreinish
added a commit
to mtreinish/qiskit-core
that referenced
this pull request
Jul 11, 2022
In Qiskit#8201 I added a release note as part of the PR which documented the change in behavior. However, I accidentally committed this file in the wrong location (by running reno new outside of the repo root). This meant the file was never actually included in the release notes for the 0.21.0 release. This commit corrects this oversight and moves it back to the proper location. However, since this isn't my first time making this mistake and I can expect that others will make it too in the future. This commit also adds a new script to detect this and raise an error when release notes are present outside of the proper location. By running this as part of lint jobs we'll block this mistake from happening again.
mergify bot
added a commit
that referenced
this pull request
Jul 12, 2022
* Move release note in wrong location and add script to block this In #8201 I added a release note as part of the PR which documented the change in behavior. However, I accidentally committed this file in the wrong location (by running reno new outside of the repo root). This meant the file was never actually included in the release notes for the 0.21.0 release. This commit corrects this oversight and moves it back to the proper location. However, since this isn't my first time making this mistake and I can expect that others will make it too in the future. This commit also adds a new script to detect this and raise an error when release notes are present outside of the proper location. By running this as part of lint jobs we'll block this mistake from happening again. * Fix lint Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>
mergify bot
pushed a commit
that referenced
this pull request
Jul 12, 2022
* Move release note in wrong location and add script to block this In #8201 I added a release note as part of the PR which documented the change in behavior. However, I accidentally committed this file in the wrong location (by running reno new outside of the repo root). This meant the file was never actually included in the release notes for the 0.21.0 release. This commit corrects this oversight and moves it back to the proper location. However, since this isn't my first time making this mistake and I can expect that others will make it too in the future. This commit also adds a new script to detect this and raise an error when release notes are present outside of the proper location. By running this as part of lint jobs we'll block this mistake from happening again. * Fix lint Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com> (cherry picked from commit bb4d52a)
mergify bot
added a commit
that referenced
this pull request
Jul 12, 2022
…) (#8327) * Move release note in wrong location and add script to block this In #8201 I added a release note as part of the PR which documented the change in behavior. However, I accidentally committed this file in the wrong location (by running reno new outside of the repo root). This meant the file was never actually included in the release notes for the 0.21.0 release. This commit corrects this oversight and moves it back to the proper location. However, since this isn't my first time making this mistake and I can expect that others will make it too in the future. This commit also adds a new script to detect this and raise an error when release notes are present outside of the proper location. By running this as part of lint jobs we'll block this mistake from happening again. * Fix lint Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com> (cherry picked from commit bb4d52a) Co-authored-by: Matthew Treinish <mtreinish@kortar.org>
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 hashbrown from 0.11.2 to 0.12.1.
Changelog
Sourced from hashbrown's changelog.
Commits
fe06a93Version 0.12.1fcca2d6Auto merge of #321 - JustForFun88:JustForFun88-patch-1, r=Amanieu5e3df22Update map.rsaac453fAuto merge of #323 - dtolnay-contrib:checkoutv3, r=Amanieua41bd76Auto merge of #325 - Amanieu:fix_size_hint, r=Amanieucf1602aFix underflow in RawIterRange::size_hint79ce3d4Update GitHub Actions actions/checkout@v2 to v3fb7e3b1Correct the implementation of Debug for ValuesMut and IntoValues structures21bfd9aAuto merge of #314 - RalfJung:miri, r=Amanieu8ac6721Auto merge of #317 - Amanieu:no_pedantic, r=AmanieuDependabot 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 mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@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)