Repository navigation
build(deps): bump the github-actions group across 1 directory with 2 updates - #800
Conversation
|
Warning Review limit reachedYou’ve reached a temporary PR review limit under our Fair Usage Limits Policy. Next review available in: 2 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (6)
📝 WalkthroughWalkthroughThe pull request updates pinned GitHub Actions revisions in five CI workflows and one promotion workflow. CI path filters retain their existing gating configuration, while the approval-required Slack notification advances to v4.0.0. ChangesCI action pins
Promotion notification pin
Estimated code review effort: 1 (Trivial) | ~5 minutes Possibly related PRs
Suggested reviewers: Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
Comment |
There was a problem hiding this comment.
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (5)
.github/workflows/ci-shell-installer.yml (1)
49-54: 📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick winUpdate the stale action version comment.
The pin now references dorny/paths-filter v4.0.2, but the comment still documents v3.0.2. Update it to avoid misleading maintenance and incident investigations. (mail-archive.com)
Proposed fix
- # v3.0.2, SHA-pinned. + # v4.0.2, SHA-pinned.🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In @.github/workflows/ci-shell-installer.yml around lines 49 - 54, Update the version comment immediately above the dorny/paths-filter action to document v4.0.2 instead of the stale v3.0.2, leaving the SHA pin and workflow behavior unchanged..github/workflows/ci-linux-kvm.yml (1)
53-60: 📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick winUpdate the stale action version comment.
The pin is the
dorny/paths-filterv4.0.2 commit, but the comment still says v3.0.2. (mail-archive.com)Proposed fix
- # v3.0.2, SHA-pinned. + # v4.0.2, SHA-pinned.🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In @.github/workflows/ci-linux-kvm.yml around lines 53 - 60, Update the version annotation in the comment above the dorny/paths-filter action to identify the pinned commit as v4.0.2, leaving the workflow condition, action reference, and surrounding rationale unchanged..github/workflows/ci.yml (1)
43-50: 📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick winUpdate the stale action version comment.
The action pin is now dorny/paths-filter v4.0.2, but the comment still says v3.0.2. Synchronize the comment with the pinned revision. (mail-archive.com)
Proposed fix
- # v3.0.2, SHA-pinned. + # v4.0.2, SHA-pinned.🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In @.github/workflows/ci.yml around lines 43 - 50, Update the version comment immediately above the dorny/paths-filter action to state v4.0.2, keeping the existing SHA pin and workflow configuration unchanged..github/workflows/ci-macos.yml (1)
44-49: 📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick winUpdate the stale action version comment.
This now pins dorny/paths-filter v4.0.2, while the comment still says v3.0.2. Keep the inline release annotation synchronized with the pinned SHA. (mail-archive.com)
Proposed fix
- # v3.0.2, SHA-pinned. + # v4.0.2, SHA-pinned.🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In @.github/workflows/ci-macos.yml around lines 44 - 49, Update the inline version annotation above the dorny/paths-filter action to identify v4.0.2, keeping the existing SHA pin and workflow behavior unchanged..github/workflows/ci-linux-native.yml (1)
55-62: 📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick winUpdate the stale action version comment.
The action pin has been upgraded to v4.0.2, but the comment still says v3.0.2. Update the comment so future reviewers can identify the pinned release correctly. (mail-archive.com)
Proposed fix
- # v3.0.2, SHA-pinned. + # v4.0.2, SHA-pinned.🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In @.github/workflows/ci-linux-native.yml around lines 55 - 62, Update the release annotation in the comment immediately above the dorny/paths-filter action to identify the pinned version as v4.0.2 instead of v3.0.2; leave the SHA pin and surrounding workflow logic unchanged.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Outside diff comments:
In @.github/workflows/ci-linux-kvm.yml:
- Around line 53-60: Update the version annotation in the comment above the
dorny/paths-filter action to identify the pinned commit as v4.0.2, leaving the
workflow condition, action reference, and surrounding rationale unchanged.
In @.github/workflows/ci-linux-native.yml:
- Around line 55-62: Update the release annotation in the comment immediately
above the dorny/paths-filter action to identify the pinned version as v4.0.2
instead of v3.0.2; leave the SHA pin and surrounding workflow logic unchanged.
In @.github/workflows/ci-macos.yml:
- Around line 44-49: Update the inline version annotation above the
dorny/paths-filter action to identify v4.0.2, keeping the existing SHA pin and
workflow behavior unchanged.
In @.github/workflows/ci-shell-installer.yml:
- Around line 49-54: Update the version comment immediately above the
dorny/paths-filter action to document v4.0.2 instead of the stale v3.0.2,
leaving the SHA pin and workflow behavior unchanged.
In @.github/workflows/ci.yml:
- Around line 43-50: Update the version comment immediately above the
dorny/paths-filter action to state v4.0.2, keeping the existing SHA pin and
workflow configuration unchanged.
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro
Run ID: 8bc0a3ed-3c4e-46fb-8dc5-711512d23598
📒 Files selected for processing (6)
.github/workflows/ci-linux-kvm.yml.github/workflows/ci-linux-native.yml.github/workflows/ci-macos.yml.github/workflows/ci-shell-installer.yml.github/workflows/ci.yml.github/workflows/promote.yml
…updates Bumps the github-actions group with 2 updates in the / directory: [dorny/paths-filter](https://github.com/dorny/paths-filter) and [slackapi/slack-github-action](https://github.com/slackapi/slack-github-action). Updates `dorny/paths-filter` from 3.0.2 to 4.0.2 - [Release notes](https://github.com/dorny/paths-filter/releases) - [Changelog](https://github.com/dorny/paths-filter/blob/master/CHANGELOG.md) - [Commits](dorny/paths-filter@de90cc6...7b450ff) Updates `slackapi/slack-github-action` from 3.0.3 to 4.0.0 - [Release notes](https://github.com/slackapi/slack-github-action/releases) - [Changelog](https://github.com/slackapi/slack-github-action/blob/main/CHANGELOG.md) - [Commits](slackapi/slack-github-action@45a88b9...dcb1066) --- updated-dependencies: - dependency-name: dorny/paths-filter dependency-version: 4.0.2 dependency-type: direct:production update-type: version-update:semver-major dependency-group: github-actions - dependency-name: slackapi/slack-github-action dependency-version: 4.0.0 dependency-type: direct:production update-type: version-update:semver-major dependency-group: github-actions ... Signed-off-by: dependabot[bot] <support@github.com>
a9654c5 to
1811962
Compare
Bumps the github-actions group with 2 updates in the / directory: dorny/paths-filter and slackapi/slack-github-action.
Updates
dorny/paths-filterfrom 3.0.2 to 4.0.2Release notes
Sourced from dorny/paths-filter's releases.
Changelog
Sourced from dorny/paths-filter's changelog.
... (truncated)
Commits
7b450ffdocs: update changelog for v4.0.2 (#318)9280377fix: work around git dubious ownership errors in container jobs (#317)f3ceefdfix: use rev-parse instead of branch --show-current for older git compat (#303)61f87a1chore: fix GitHub spelling in logs (#278)b82ff81fix warning message (#282)fbd0ab8feat: add merge_group event supportefb1da7feat: add dist/ freshness check to PR workflowd8f7b06Merge pull request #302 from dorny/issue-299addbc14Update README for v49d7afb8Update CHANGELOG for v4.0.0Updates
slackapi/slack-github-actionfrom 3.0.3 to 4.0.0Release notes
Sourced from slackapi/slack-github-action's releases.
Changelog
Sourced from slackapi/slack-github-action's changelog.
Commits
dcb1066chore: release53861e0chore: release (#645)b1974f0build!: parse yaml with more strict multiline indentation rules (#640)947ed06build(deps): bump undici from 7.28.0 to 8.7.0 (#653)03922a9chore: track undici-types to the resolved undici version (#652)31d473ebuild(deps-dev): bump typescript from 6.0.3 to 7.0.2 (#651)3ca6997build(deps-dev): bump sinon and@types/sinon(#649)26a5ad3build(deps): bump actions/setup-node from 6.4.0 to 7.0.0 (#647)5092efbbuild(deps-dev): bump@biomejs/biomefrom 2.5.3 to 2.5.4 (#650)3548c3ebuild(deps): bump slackapi/slack-github-action from 3.0.3 to 3.0.5 (#646)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 show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore <dependency name> major versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)@dependabot ignore <dependency name> minor versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)@dependabot ignore <dependency name>will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)@dependabot unignore <dependency name>will remove all of the ignore conditions of the specified dependency@dependabot unignore <dependency name> <ignore condition>will remove the ignore condition of the specified dependency and ignore conditionsSummary by CodeRabbit