starred/komorebi
1
0
Fork 0
mirror of https://github.com/LGUG2Z/komorebi.git synced 2026-01-11 14:40:25 +01:00
Code Issues 87 Packages Projects Releases 10 Wiki Activity

[PR #136] [MERGED] chore(deps): bump clap from 3.1.10 to 3.1.14 #767

New Issue
Closed
opened 2026-01-05 14:52:55 +01:00 by adam · 0 comments
adam commented 2026-01-05 14:52:55 +01:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/LGUG2Z/komorebi/pull/136
Author: @dependabot[bot]
Created: 5/1/2022
Status: ✅ Merged
Merged: 5/4/2022
Merged by: @LGUG2Z

Base: master ← Head: dependabot/cargo/clap-3.1.14

📝 Commits (1)

  • 0d6cfcc chore(deps): bump clap from 3.1.10 to 3.1.14

📊 Changes

1 file changed (+4 additions, -4 deletions)

View changed files

📝 Cargo.lock (+4 -4)

📄 Description

Bumps clap from 3.1.10 to 3.1.14.

Release notes

Sourced from clap's releases.

v3.1.14

[3.1.14] - 2022-05-01

Fixes

  • Panic when calling Command::build with a required positional argument nested several layers in subcommands

v3.1.13

[3.1.13] - 2022-04-30

Fixes

  • Help subcommand and Command::write_help now report required arguments in usage in more circumstances
  • Unknown subcommand for help subcommand flag now reports an error with more context
  • More details reported when using debug feature
  • Allow disabling color feature with debug feature enabled

v3.1.12

[3.1.12] - 2022-04-22

Fixes

  • Regression in 3.1.11 where the (output) streams were crossed

v3.1.11

[3.1.11] - 2022-04-22

Fixes

  • Implied conflicts override Arg::required, making the behavior consistent with how we calculate conflicts for error reporting
  • Members of a mutually exclusive ArgGroup override Arg::required, making the behavior consistent with how we calculate conflicts for error reporting
  • Arg::overrides_with always override Arg::required, not just when the parser processes an override
Changelog

Sourced from clap's changelog.

[3.1.14] - 2022-05-01

Fixes

  • Panic when calling Command::build with a required positional argument nested several layers in subcommands

[3.1.13] - 2022-04-30

Fixes

  • Help subcommand and Command::write_help now report required arguments in usage in more circumstances
  • Unknown subcommand for help subcommand flag now reports an error with more context
  • More details reported when using debug feature
  • Allow disabling color feature with debug feature enabled

[3.1.12] - 2022-04-22

Fixes

  • Regression in 3.1.11 where the (output) streams were crossed

[3.1.11] - 2022-04-22

Fixes

  • Implied conflicts override Arg::required, making the behavior consistent with how we calculate conflicts for error reporting
  • Members of a mutually exclusive ArgGroup override Arg::required, making the behavior consistent with how we calculate conflicts for error reporting
  • Arg::overrides_with always override Arg::required, not just when the parser processes an override
Commits

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)

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/LGUG2Z/komorebi/pull/136 **Author:** [@dependabot[bot]](https://github.com/apps/dependabot) **Created:** 5/1/2022 **Status:** ✅ Merged **Merged:** 5/4/2022 **Merged by:** [@LGUG2Z](https://github.com/LGUG2Z) **Base:** `master` ← **Head:** `dependabot/cargo/clap-3.1.14` --- ### 📝 Commits (1) - [`0d6cfcc`](https://github.com/LGUG2Z/komorebi/commit/0d6cfcc04fd6bba2ce0c847043497f8cdc386028) chore(deps): bump clap from 3.1.10 to 3.1.14 ### 📊 Changes **1 file changed** (+4 additions, -4 deletions) <details> <summary>View changed files</summary> 📝 `Cargo.lock` (+4 -4) </details> ### 📄 Description Bumps [clap](https://github.com/clap-rs/clap) from 3.1.10 to 3.1.14. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/clap-rs/clap/releases">clap's releases</a>.</em></p> <blockquote> <h2>v3.1.14</h2> <h2>[3.1.14] - 2022-05-01</h2> <h3>Fixes</h3> <ul> <li>Panic when calling <code>Command::build</code> with a required positional argument nested several layers in subcommands</li> </ul> <h2>v3.1.13</h2> <h2>[3.1.13] - 2022-04-30</h2> <h3>Fixes</h3> <ul> <li>Help subcommand and <code>Command::write_help</code> now report required arguments in usage in more circumstances</li> <li>Unknown subcommand for help subcommand flag now reports an error with more context</li> <li>More details reported when using <code>debug</code> feature</li> <li>Allow disabling <code>color</code> feature with <code>debug</code> feature enabled</li> </ul> <h2>v3.1.12</h2> <h2>[3.1.12] - 2022-04-22</h2> <h3>Fixes</h3> <ul> <li>Regression in 3.1.11 where the (output) streams were crossed</li> </ul> <h2>v3.1.11</h2> <h2>[3.1.11] - 2022-04-22</h2> <h3>Fixes</h3> <ul> <li>Implied conflicts override <code>Arg::required</code>, making the behavior consistent with how we calculate conflicts for error reporting</li> <li>Members of a mutually exclusive <code>ArgGroup</code> override <code>Arg::required</code>, making the behavior consistent with how we calculate conflicts for error reporting</li> <li><code>Arg::overrides_with</code> always override <code>Arg::required</code>, not just when the parser processes an override</li> </ul> </blockquote> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/clap-rs/clap/blob/master/CHANGELOG.md">clap's changelog</a>.</em></p> <blockquote> <h2>[3.1.14] - 2022-05-01</h2> <h3>Fixes</h3> <ul> <li>Panic when calling <code>Command::build</code> with a required positional argument nested several layers in subcommands</li> </ul> <h2>[3.1.13] - 2022-04-30</h2> <h3>Fixes</h3> <ul> <li>Help subcommand and <code>Command::write_help</code> now report required arguments in usage in more circumstances</li> <li>Unknown subcommand for help subcommand flag now reports an error with more context</li> <li>More details reported when using <code>debug</code> feature</li> <li>Allow disabling <code>color</code> feature with <code>debug</code> feature enabled</li> </ul> <h2>[3.1.12] - 2022-04-22</h2> <h3>Fixes</h3> <ul> <li>Regression in 3.1.11 where the (output) streams were crossed</li> </ul> <h2>[3.1.11] - 2022-04-22</h2> <h3>Fixes</h3> <ul> <li>Implied conflicts override <code>Arg::required</code>, making the behavior consistent with how we calculate conflicts for error reporting</li> <li>Members of a mutually exclusive <code>ArgGroup</code> override <code>Arg::required</code>, making the behavior consistent with how we calculate conflicts for error reporting</li> <li><code>Arg::overrides_with</code> always override <code>Arg::required</code>, not just when the parser processes an override</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/clap-rs/clap/commit/5e02ac1c19261d9c6693d968a8b130a6da944313"><code>5e02ac1</code></a> chore: Release</li> <li><a href="https://github.com/clap-rs/clap/commit/f7b00adacfb0cb33288d123c9757055066010666"><code>f7b00ad</code></a> docs: Update chaneglog</li> <li><a href="https://github.com/clap-rs/clap/commit/b37c0a1f0f88d369b9561ebad41f179c51094385"><code>b37c0a1</code></a> Merge pull request <a href="https://github-redirect.dependabot.com/clap-rs/clap/issues/3670">#3670</a> from epage/panic</li> <li><a href="https://github.com/clap-rs/clap/commit/0ecb6f486979bd4421660aa93410fb075929b023"><code>0ecb6f4</code></a> fix(builder): Fully recurse when building</li> <li><a href="https://github.com/clap-rs/clap/commit/c6849e2ebd2b520fcbdd3c21ccff81a2286d48c7"><code>c6849e2</code></a> fix(debug): Moe detail</li> <li><a href="https://github.com/clap-rs/clap/commit/3ca1b7709408f8bb3ec6b48ac2b4854aabe643b7"><code>3ca1b77</code></a> chore: Fix manifest</li> <li><a href="https://github.com/clap-rs/clap/commit/b01256be36fb07e5bcd7174fc5f2932d255eb1e3"><code>b01256b</code></a> chore: Release</li> <li><a href="https://github.com/clap-rs/clap/commit/0c5400dadb6d8a87ce0109e49c70eb61af5c6add"><code>0c5400d</code></a> chore: Release</li> <li><a href="https://github.com/clap-rs/clap/commit/09d21f4005623334fb30c4d364971f9c3c17888d"><code>09d21f4</code></a> docs: Update changelog</li> <li><a href="https://github.com/clap-rs/clap/commit/bd653b90d9399c4d6f99e575594e4407d3cd8e60"><code>bd653b9</code></a> Merge pull request <a href="https://github-redirect.dependabot.com/clap-rs/clap/issues/3667">#3667</a> from epage/exe</li> <li>Additional commits viewable in <a href="https://github.com/clap-rs/clap/compare/v3.1.10...v3.1.14">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=clap&package-manager=cargo&previous-version=3.1.10&new-version=3.1.14)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) 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-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> 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) </details> --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
adam added the pull-request label 2026-01-05 14:52:55 +01:00
adam closed this issue 2026-01-05 14:52:55 +01:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
0.1.36
apps-behaving-badly
bug
bug
cannot-reproduce
documentation
enhancement
github_actions
i-am-stuck
i-will-definitely-work-on-this
i-will-not-work-on-this
i-will-probably-work-on-this
komorebi
komorebi-bar
komorebic
performance
pull-request
Mirrored from GitHub Pull Request
 translation
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/komorebi#767
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?