build(deps): bump clap-config-file from 0.5.0 to 0.6.0 #227
Conversation
This file contains hidden or 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
Bumps [clap-config-file](https://github.com/bodo-run/clap-config-file) from 0.5.0 to 0.6.0. - [Release notes](https://github.com/bodo-run/clap-config-file/releases) - [Commits](bodo-run/clap-config-file@v0.5.0...v0.6.0) --- updated-dependencies: - dependency-name: clap-config-file dependency-version: 0.6.0 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <[email protected]>
dependabot
bot
added
dependencies
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Greptile Overview
Summary
Updates clap-config-file dependency from 0.5.0 to 0.6.0, which standardizes config file field naming to kebab-case format.
Key changes in v0.6.0:
- Field naming consistency: All config fields now use kebab-case format
- Boolean config integration: Proper serde rename attributes added for boolean fields
- Documentation improvements
Important: This update requires existing config files (yek.yaml, bench.toml) to use kebab-case field names instead of snake_case. For example:
output_dir→output-dirignore_patterns→ignore-patternspriority_rules→priority-rulesbinary_extensions→binary-extensionsgit_boost_max→git-boost-maxcategory_weights→category-weightsmax_git_depth→max-git-depth
Confidence Score: 3/5
- Safe to merge after verifying config file field naming compatibility
- Standard dependency bump with breaking changes to config file format. The v0.6.0 update enforces kebab-case field naming which requires existing config files (yek.yaml, bench.toml) to be updated from snake_case to kebab-case. Without this update, config files will fail to parse correctly. Score of 3 reflects the need to verify and update config files before merging.
- Pay close attention to yek.yaml and bench.toml - these config files must be updated to use kebab-case field names (output-dir, ignore-patterns, priority-rules, etc.) instead of snake_case to maintain compatibility with clap-config-file v0.6.0
Important Files Changed
File Analysis
| Filename | Score | Overview |
|---|---|---|
| Cargo.toml | 4/5 | Bumps clap-config-file from 0.5.0 to 0.6.0 - standard dependency update |
| Cargo.lock | 4/5 | Updates lock file with new checksum for clap-config-file 0.6.0 |
Sequence Diagram
sequenceDiagram
participant Dev as Developer
participant Dep as Dependabot
participant YC as YekConfig
participant CCF as clap-config-file
participant CF as Config Files
Dev->>Dep: Trigger dependency update
Dep->>CCF: Bump 0.5.0 → 0.6.0
Note over CCF: v0.6.0 enforces<br/>kebab-case naming
Dep->>YC: Update Cargo.toml
Dep->>YC: Update Cargo.lock
YC->>CCF: Parse CLI args + config
CCF->>CF: Read yek.yaml/bench.toml
Note over CF: MUST use kebab-case:<br/>output-dir, ignore-patterns,<br/>priority-rules, etc.
CCF->>YC: Return parsed config
Note over Dev,CF: Action Required: Update<br/>config files to kebab-case
1 file reviewed, 1 comment
| bytesize = "2.0.1" | ||
| clap = { version = "4.5", features = ["derive"] } | ||
| clap-config-file = "0.5.0" | ||
| clap-config-file = "0.6.0" |
Contributor
There was a problem hiding this comment.
style: v0.6.0 enforces kebab-case in config files. Verify yek.yaml uses output-dir, ignore-patterns, priority-rules, binary-extensions, git-boost-max, category-weights, max-git-depth (not snake_case)
Prompt To Fix With AI
This is a comment left during a code review.
Path: Cargo.toml
Line: 18:18
Comment:
**style:** v0.6.0 enforces kebab-case in config files. Verify `yek.yaml` uses `output-dir`, `ignore-patterns`, `priority-rules`, `binary-extensions`, `git-boost-max`, `category-weights`, `max-git-depth` (not snake_case)
How can I resolve this? If you propose a fix, please make it concise.
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 clap-config-file from 0.5.0 to 0.6.0.
Release notes
Sourced from clap-config-file's releases.
Commits
5a761f8Bump version to 0.6.0a0e1ed9Merge pull request #14 from bodo-run/copilot/fix-1337cb4ccFix CI test failures by updating config field names to kebab-case2a941a6Fix example config files to use kebab-case naming and update nested struct se...70e066bFix test to focus on field naming consistency validation rather than boolean ...20cdf2dFix config file field naming in tests to use kebab-case format1b46dfcFix boolean config integration by adding kebab-case serde rename attributes787c0f4Initial plan992098cMerge pull request #12 from bodo-run/defaults0818bd2Fix truncated README sentence about multiple config filesYou 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 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 show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@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)