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

chore(deps): bump gix-path from 0.10.9 to 0.10.11 #14489

Merged
merged 1 commit into from
Oct 8, 2024

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Sep 3, 2024

Bumps gix-path from 0.10.9 to 0.10.10.

Release notes

Sourced from gix-path's releases.

gix-path v0.10.10

A maintenance release without user-facing changes.

Commit Statistics

  • 6 commits contributed to the release over the course of 12 calendar days.
  • 35 days passed between releases.
  • 0 commits were understood as conventional.
  • 0 issues like '(#ID)' were seen in commit messages

Commit Details

  • Uncategorized
    • Prepare changelogs prior to release (0f25841)
    • Merge pull request #1523 from martinvonz/push-xmsuurxprnnw (83c9de0)
    • Remove --system from git config call as it fails on MacOS (6b1c243)
    • Run git config -l in temp dir when looking up system config (20ef4e9)
    • Merge branch 'push-ysnqkzlzwuwq' (e2c747d)
    • Don't show console on Windows (087594c)
Commits
  • d19af16 Release gix-date v0.9.0, gix-actor v0.31.6, gix-validate v0.9.0, gix-object v...
  • 0f25841 prepare changelogs prior to release
  • 9ed2b24 Merge branch 'improvements'
  • 6990afd fix: similarity detection
  • f8c5d9c fix similarity detection
  • 25a3f1b Merge pull request #1531 from EliahKagan/progress-typos
  • ba72ee0 fix!: better peeling performance for reference traversal.
  • 9f9feb6 add progress report for July
  • b31d6b7 Fix typos in config support info
  • 242fedc Merge branch 'improvements'
  • Additional commits viewable in compare view

Dependabot compatibility score

You can trigger a rebase of this PR 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 show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @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)
    You can disable automated security fix PRs for this repo from the Security Alerts page.

Note
Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

@dependabot dependabot bot added the A-build-dependencies Area: [build-dependencies] label Sep 3, 2024
@rustbot
Copy link
Collaborator

rustbot commented Sep 3, 2024

Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @weihanglo (or someone else) some time within the next two weeks.

Please see the contribution instructions for more information. Namely, in order to ensure the minimum review times lag, PR authors and assigned reviewers should ensure that the review label (S-waiting-on-review and S-waiting-on-author) stays updated, invoking these commands when appropriate:

  • @rustbot author: the review is finished, PR author should check the comments and take action accordingly
  • @rustbot review: the author is ready for a review, this PR will be queued again in the reviewer's queue

@rustbot rustbot added the S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. label Sep 3, 2024
Copy link
Contributor Author

dependabot bot commented on behalf of github Sep 10, 2024

Dependabot encountered an unknown error. Because of this, Dependabot cannot update this pull request.

@bors
Copy link
Contributor

bors commented Sep 10, 2024

☔ The latest upstream changes (presumably #14493) made this pull request unmergeable. Please resolve the merge conflicts.

@weihanglo weihanglo force-pushed the dependabot/cargo/gix-path-0.10.10 branch from 5bbf7ff to 011bde9 Compare October 7, 2024 23:24
Bumps [gix-path](https://github.com/Byron/gitoxide) from 0.10.9 to 0.10.11.
- [Release notes](https://github.com/Byron/gitoxide/releases)
- [Changelog](https://github.com/Byron/gitoxide/blob/main/CHANGELOG.md)
- [Commits](GitoxideLabs/gitoxide@gix-path-v0.10.9...gix-path-v0.10.11)

---
updated-dependencies:
- dependency-name: gix-path
  dependency-type: indirect
...

Signed-off-by: dependabot[bot] <support@github.com>
@weihanglo weihanglo force-pushed the dependabot/cargo/gix-path-0.10.10 branch from 011bde9 to 7a58e6f Compare October 7, 2024 23:24
@Muscraft Muscraft changed the title chore(deps): bump gix-path from 0.10.9 to 0.10.10 chore(deps): bump gix-path from 0.10.9 to 0.10.11 Oct 7, 2024
@weihanglo
Copy link
Member

@bors r+

@bors
Copy link
Contributor

bors commented Oct 8, 2024

📌 Commit 7a58e6f has been approved by weihanglo

It is now in the queue for this repository.

@bors bors added S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. and removed S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. labels Oct 8, 2024
@bors
Copy link
Contributor

bors commented Oct 8, 2024

⌛ Testing commit 7a58e6f with merge 2e309bd...

@bors
Copy link
Contributor

bors commented Oct 8, 2024

☀️ Test successful - checks-actions
Approved by: weihanglo
Pushing 2e309bd to master...

@bors bors merged commit 2e309bd into master Oct 8, 2024
24 checks passed
@bors bors deleted the dependabot/cargo/gix-path-0.10.10 branch October 8, 2024 00:44
bors added a commit to rust-lang-ci/rust that referenced this pull request Oct 9, 2024
Update cargo

8 commits in ad074abe3a18ce8444c06f962ceecfd056acfc73..15fbd2f607d4defc87053b8b76bf5038f2483cf4
2024-10-04 18:18:15 +0000 to 2024-10-08 21:08:11 +0000
- initial version of checksum based freshness (rust-lang/cargo#14137)
- feat: Add custom completer for completing registry name (rust-lang/cargo#14656)
- Document build-plan as being deprecated (rust-lang/cargo#14657)
- fix(complete): Don't complete files for any value (rust-lang/cargo#14653)
- Add more SAT resolver tests (rust-lang/cargo#14614)
- fix: avoid inserting duplicate `dylib_path_envvar` when calling `cargo run` recursively (rust-lang/cargo#14464)
- chore(deps): bump gix-path from 0.10.9 to 0.10.11 (rust-lang/cargo#14489)
- improve error reporting when feature not found in `activated_features` (rust-lang/cargo#14647)

---

This also adds three license exceptions to Cargo.

* arrayref — BSD-2-Clause
* blake3 — CC0-1.0 OR Apache-2.0 OR Apache-2.0 WITH LLVM-exception
* constant_time_eq — CC0-1.0 OR MIT-0 OR Apache-2.0

These exceptions were added to rustc in rust-lang#126930, so should be fine for Cargo as well.
@rustbot rustbot added this to the 1.83.0 milestone Oct 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-build-dependencies Area: [build-dependencies] S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants