build(deps): bump tj-actions/changed-files from 44.5.7 to 45.0.0 #761
Conversation
![dependabot[bot]](https://avatars.githubusercontent.com/in/29110?s=60&v=4){kind=small}
Bumps [tj-actions/changed-files](https://github.com/tj-actions/changed-files) from 44.5.7 to 45.0.0. - [Release notes](https://github.com/tj-actions/changed-files/releases) - [Changelog](https://github.com/tj-actions/changed-files/blob/main/HISTORY.md) - [Commits](tj-actions/changed-files@v44.5.7...v45.0.0) --- updated-dependencies: - dependency-name: tj-actions/changed-files dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <[email protected]>
dependabot
bot
added
the
dependencies
WalkthroughThe changes involve updating the version of the Changes
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (invoked as PR comments)
Additionally, you can add CodeRabbit Configuration File (
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 0
Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Files selected for processing (2)
- .github/workflows/lint.yml (1 hunks)
- .github/workflows/test.yml (1 hunks)
Additional comments not posted (2)
.github/workflows/lint.yml (1)
28-28: Verify the impact of thechanged-filesversion update.The update from
v44.5.7tov45.0.0may affect how renamed files are detected, especially with theoutput_renamed_files_as_deleted_and_addedoption. Ensure that the workflow behaves as expected with this new version.Run the following script to check for any changes in the handling of renamed files:
Verification successful
No immediate impact from
changed-filesversion update, but note breaking change.The update to
v45.0.0introduces a breaking change related to theoutput_renamed_files_as_deleted_and_addedoption, which affects the handling of renamed files. Since this option is not currently used in your workflow, there is no immediate impact. However, be aware of this change for any future modifications.
- Breaking change: Renamed files are now decomposed into deleted and added entries if
output_renamed_files_as_deleted_and_addedis set totrue.Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash # Description: Verify the handling of renamed files with the new version of `changed-files`. # Test: Check for usage of `output_renamed_files_as_deleted_and_added` option. rg --type yaml 'output_renamed_files_as_deleted_and_added' -A 2Length of output: 63
Script:
#!/bin/bash # Description: Check for release notes or changelog for tj-actions/changed-files version v45.0.0 # Attempt to find a CHANGELOG or similar documentation file in the repository fd -I -t f -i 'changelog*' --exec cat {} # Attempt to find any documentation mentioning version updates rg --type md 'v45.0.0' -A 5Length of output: 72
Script:
#!/bin/bash # Description: Fetch release notes for tj-actions/changed-files version v45.0.0 using GitHub CLI # Fetch the release notes for version v45.0.0 from the tj-actions/changed-files repository gh release view v45.0.0 --repo tj-actions/changed-files --json body -q .bodyLength of output: 3067
.github/workflows/test.yml (1)
30-30: Verify the impact of thechanged-filesversion update.The update from
v44.5.7tov45.0.0may affect how renamed files are detected, especially with theoutput_renamed_files_as_deleted_and_addedoption. Ensure that the workflow behaves as expected with this new version.Run the following script to check for any changes in the handling of renamed files:
Verification successful
No impact from
changed-filesversion update found.The searches did not reveal any usage of the
output_renamed_files_as_deleted_and_addedoption or related configurations in the codebase. Therefore, the update tov45.0.0oftj-actions/changed-filesis unlikely to affect the workflow regarding renamed files.Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash # Description: Verify the handling of renamed files with the new version of `changed-files`. # Test: Check for usage of `output_renamed_files_as_deleted_and_added` option. rg --type yaml 'output_renamed_files_as_deleted_and_added' -A 2Length of output: 63
Script:
#!/bin/bash # Search for the usage of `changed-files` action in the entire codebase rg --type yaml 'tj-actions/changed-files@' -A 5Length of output: 47
Script:
#!/bin/bash # Perform a broader search for any YAML files containing configurations related to the `changed-files` action fd --type f --extension yaml --exec rg 'changed-files' {}Length of output: 59
|
Superseded by #811. |
dependabot
bot
deleted the
dependabot/github_actions/tj-actions/changed-files-45.0.0
branch
Bumps tj-actions/changed-files from 44.5.7 to 45.0.0.
Release notes
Sourced from tj-actions/changed-files's releases.
Changelog
Sourced from tj-actions/changed-files's changelog.
... (truncated)
Commits
40853deUpdated README.md (#2243)94b94fedocs: add Whadup as a contributor for code (#2239)f8034fbRenamed Files decomposed into Deleted: previous_filename and Added:filename (...b4c0974fix: update test skip logic to use custom env (#2242)246859dchore: debug env vars (#2241)46a4c02chore: conditionally skip certain test for foked prs (#2240)525aabbfix: remove unsupported input (#2238)25b2562chore(deps): update dependency@types/nodeto v22.4.2257f12cchore(deps): update dependency@types/nodeto v22.4.1598b721Added missing changes and modified dist assets.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 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)