Skip to content

ci(deps): bump the actions-minor-patch group across 1 directory with 4 updates#176

Open
dependabot[bot] wants to merge 1 commit intodevfrom
dependabot/github_actions/dev/actions-minor-patch-46f02b9062
Open

ci(deps): bump the actions-minor-patch group across 1 directory with 4 updates#176
dependabot[bot] wants to merge 1 commit intodevfrom
dependabot/github_actions/dev/actions-minor-patch-46f02b9062

Conversation

@dependabot
Copy link

@dependabot dependabot bot commented on behalf of github Mar 16, 2026 •
edited
Loading

Bumps the actions-minor-patch group with 4 updates in the / directory: actions/dependency-review-action, github/codeql-action, vig-os/commit-action and vig-os/sync-issues-action.

Updates actions/dependency-review-action from 4.8.2 to 4.9.0

Release notes

Sourced from actions/dependency-review-action's releases.

Dependency Review Action 4.9.0

This feature release contains a couple of notable changes:

  • There is a new configuration option show_patched_versions which will add a column to the output, showing the fix version of each vulnerable dependency. Thanks @​felickz!
  • Runs which do not display OpenSSF scorecards no longer fetch scorecard information; previously it was fetched regardless of whether or not it was displayed, causing unneccessary slowness. Great catch @​jantiebot!
  • There are a couple of fixes to purl parsing which should improve match accuracy for allow-package-dependency lists, including case (in)sensitivity and url-encoded namespaces Thanks @​juxtin!

What's Changed

New Contributors

Full Changelog: actions/dependency-review-action@v4.8.3...v4.9.0

4.8.3

Dependency Review Action v4.8.3

This is a bugfix release that updates a number of upstream dependencies and includes a fix for the earlier feature that detected oversized summaries and upload them as artifacts, which could occasionally crash the action.

We have also updated the release process to use a long-lived v4 branch for the action, instead of a force-pushed tag, which aligns better with git branching strategies; the change should be transparent to end users.

What's Changed

Full Changelog: https://github.com/actions/dependency-review-action/compare/v4.8.2..v4.8.3

Commits
  • 2031cfc Merge pull request #1064 from actions/ahpook/release-4.9.0
  • d02fa39 Updates for release 4.9.0
  • 4038a34 Merge pull request #1021 from actions/dependabot/github_actions/actions/check...
  • a632b83 Merge pull request #1058 from actions/dependabot/github_actions/actions/stale...
  • 57a3d46 Merge pull request #1060 from jantiebot/main
  • 5ecdc4b Merge pull request #1045 from forks-felickz/main
  • e8c2f9a fix: remove inferrable type annotation to pass eslint
  • 0e129e1 Prettier - Refactor summary table rendering for improved readability
  • aa60746 Add 'show-patched-versions' option to configuration and update summary handling
  • e404798 Merge upstream actions/dependency-review-action main
  • Additional commits viewable in compare view

Updates github/codeql-action from 4.32.2 to 4.32.6

Release notes

Sourced from github/codeql-action's releases.

v4.32.6

  • Update default CodeQL bundle version to 2.24.3. #3548

v4.32.5

  • Repositories owned by an organization can now set up the github-codeql-disable-overlay custom repository property to disable improved incremental analysis for CodeQL. First, create a custom repository property with the name github-codeql-disable-overlay and the type "True/false" in the organization's settings. Then in the repository's settings, set this property to true to disable improved incremental analysis. For more information, see Managing custom properties for repositories in your organization. This feature is not yet available on GitHub Enterprise Server. #3507
  • Added an experimental change so that when improved incremental analysis fails on a runner — potentially due to insufficient disk space — the failure is recorded in the Actions cache so that subsequent runs will automatically skip improved incremental analysis until something changes (e.g. a larger runner is provisioned or a new CodeQL version is released). We expect to roll this change out to everyone in March. #3487
  • The minimum memory check for improved incremental analysis is now skipped for CodeQL 2.24.3 and later, which has reduced peak RAM usage. #3515
  • Reduced log levels for best-effort private package registry connection check failures to reduce noise from workflow annotations. #3516
  • Added an experimental change which lowers the minimum disk space requirement for improved incremental analysis, enabling it to run on standard GitHub Actions runners. We expect to roll this change out to everyone in March. #3498
  • Added an experimental change which allows the start-proxy action to resolve the CodeQL CLI version from feature flags instead of using the linked CLI bundle version. We expect to roll this change out to everyone in March. #3512
  • The previously experimental changes from versions 4.32.3, 4.32.4, 3.32.3 and 3.32.4 are now enabled by default. #3503, #3504

v4.32.4

  • Update default CodeQL bundle version to 2.24.2. #3493
  • Added an experimental change which improves how certificates are generated for the authentication proxy that is used by the CodeQL Action in Default Setup when private package registries are configured. This is expected to generate more widely compatible certificates and should have no impact on analyses which are working correctly already. We expect to roll this change out to everyone in February. #3473
  • When the CodeQL Action is run with debugging enabled in Default Setup and private package registries are configured, the "Setup proxy for registries" step will output additional diagnostic information that can be used for troubleshooting. #3486
  • Added a setting which allows the CodeQL Action to enable network debugging for Java programs. This will help GitHub staff support customers with troubleshooting issues in GitHub-managed CodeQL workflows, such as Default Setup. This setting can only be enabled by GitHub staff. #3485
  • Added a setting which enables GitHub-managed workflows, such as Default Setup, to use a nightly CodeQL CLI release instead of the latest, stable release that is used by default. This will help GitHub staff support customers whose analyses for a given repository or organization require early access to a change in an upcoming CodeQL CLI release. This setting can only be enabled by GitHub staff. #3484

v4.32.3

  • Added experimental support for testing connections to private package registries. This feature is not currently enabled for any analysis. In the future, it may be enabled by default for Default Setup. #3466
Changelog

Sourced from github/codeql-action's changelog.

CodeQL Action Changelog

See the releases page for the relevant changes to the CodeQL CLI and language packs.

[UNRELEASED]

  • Upcoming change: Starting April 2026, the CodeQL Action will skip collecting file coverage information on pull requests to improve analysis performance. File coverage information will still be computed on non-PR analyses. Pull request analyses will log a warning about this upcoming change. #3562

    To opt out of this change:

    • Repositories owned by an organization: Create a custom repository property with the name github-codeql-file-coverage-on-prs and the type "True/false", then set this property to true in the repository's settings. For more information, see Managing custom properties for repositories in your organization. Alternatively, if you are using an advanced setup workflow, you can set the CODEQL_ACTION_FILE_COVERAGE_ON_PRS environment variable to true in your workflow.
    • User-owned repositories using default setup: Switch to an advanced setup workflow and set the CODEQL_ACTION_FILE_COVERAGE_ON_PRS environment variable to true in your workflow.
    • User-owned repositories using advanced setup: Set the CODEQL_ACTION_FILE_COVERAGE_ON_PRS environment variable to true in your workflow.

  • Fixed a bug which caused the CodeQL Action to fail loading repository properties if a "Multi select" repository property was configured for the repository. #3557

  • The CodeQL Action now loads custom repository properties on GitHub Enterprise Server, enabling the customization of features such as github-codeql-disable-overlay that was previously only available on GitHub.com. #3559

  • Once private package registries can be configured with OIDC-based authentication for organizations, the CodeQL Action will now be able to accept such configurations. #3563

  • Fixed the retry mechanism for database uploads. Previously this would fail with the error "Response body object should not be disturbed or locked". #3564

4.32.6 - 05 Mar 2026

  • Update default CodeQL bundle version to 2.24.3. #3548

4.32.5 - 02 Mar 2026

  • Repositories owned by an organization can now set up the github-codeql-disable-overlay custom repository property to disable improved incremental analysis for CodeQL. First, create a custom repository property with the name github-codeql-disable-overlay and the type "True/false" in the organization's settings. Then in the repository's settings, set this property to true to disable improved incremental analysis. For more information, see Managing custom properties for repositories in your organization. This feature is not yet available on GitHub Enterprise Server. #3507
  • Added an experimental change so that when improved incremental analysis fails on a runner — potentially due to insufficient disk space — the failure is recorded in the Actions cache so that subsequent runs will automatically skip improved incremental analysis until something changes (e.g. a larger runner is provisioned or a new CodeQL version is released). We expect to roll this change out to everyone in March. #3487
  • The minimum memory check for improved incremental analysis is now skipped for CodeQL 2.24.3 and later, which has reduced peak RAM usage. #3515
  • Reduced log levels for best-effort private package registry connection check failures to reduce noise from workflow annotations. #3516
  • Added an experimental change which lowers the minimum disk space requirement for improved incremental analysis, enabling it to run on standard GitHub Actions runners. We expect to roll this change out to everyone in March. #3498
  • Added an experimental change which allows the start-proxy action to resolve the CodeQL CLI version from feature flags instead of using the linked CLI bundle version. We expect to roll this change out to everyone in March. #3512
  • The previously experimental changes from versions 4.32.3, 4.32.4, 3.32.3 and 3.32.4 are now enabled by default. #3503, #3504

4.32.4 - 20 Feb 2026

  • Update default CodeQL bundle version to 2.24.2. #3493
  • Added an experimental change which improves how certificates are generated for the authentication proxy that is used by the CodeQL Action in Default Setup when private package registries are configured. This is expected to generate more widely compatible certificates and should have no impact on analyses which are working correctly already. We expect to roll this change out to everyone in February. #3473
  • When the CodeQL Action is run with debugging enabled in Default Setup and private package registries are configured, the "Setup proxy for registries" step will output additional diagnostic information that can be used for troubleshooting. #3486
  • Added a setting which allows the CodeQL Action to enable network debugging for Java programs. This will help GitHub staff support customers with troubleshooting issues in GitHub-managed CodeQL workflows, such as Default Setup. This setting can only be enabled by GitHub staff. #3485
  • Added a setting which enables GitHub-managed workflows, such as Default Setup, to use a nightly CodeQL CLI release instead of the latest, stable release that is used by default. This will help GitHub staff support customers whose analyses for a given repository or organization require early access to a change in an upcoming CodeQL CLI release. This setting can only be enabled by GitHub staff. #3484

4.32.3 - 13 Feb 2026

  • Added experimental support for testing connections to private package registries. This feature is not currently enabled for any analysis. In the future, it may be enabled by default for Default Setup. #3466

4.32.2 - 05 Feb 2026

  • Update default CodeQL bundle version to 2.24.1. #3460

4.32.1 - 02 Feb 2026

... (truncated)

Commits
  • 0d579ff Merge pull request #3551 from github/update-v4.32.6-72d2d850d
  • d4c6be7 Update changelog for v4.32.6
  • 72d2d85 Merge pull request #3548 from github/update-bundle/codeql-bundle-v2.24.3
  • 23f983c Merge pull request #3544 from github/dependabot/github_actions/dot-github/wor...
  • 832e97c Merge pull request #3545 from github/dependabot/github_actions/dot-github/wor...
  • 5ef38c0 Merge pull request #3546 from github/dependabot/npm_and_yarn/tar-7.5.10
  • 80c9cda Add changelog note
  • f2669dd Update default bundle to codeql-bundle-v2.24.3
  • bd03c44 Merge branch 'main' into dependabot/github_actions/dot-github/workflows/actio...
  • 102d762 Bump tar from 7.5.7 to 7.5.10
  • Additional commits viewable in compare view

Updates vig-os/commit-action from 0.1.3 to 0.1.5

Release notes

Sourced from vig-os/commit-action's releases.

v0.1.5

Fixed

  • Excluded .git metadata paths during FILE_PATHS directory expansion to prevent malformed Git tree paths (issue #15).

v0.1.4

Added

  • Added ALLOW_EMPTY environment variable support to allow creating signed empty commits when no file changes are detected
  • Added unit test coverage for empty commit behavior in commitViaAPI() and commit-runner flow handling

Changed

  • Updated npm dependency overrides to force patched minimatch versions across transitive dependency trees.
  • Updated commitViaAPI() to support empty commits by reusing the parent tree SHA when ALLOW_EMPTY=true
  • Updated runner behavior to preserve default no-op behavior when no files are detected, unless ALLOW_EMPTY=true
  • Updated README usage examples and environment variable documentation for ALLOW_EMPTY
  • Replaced process.exit(0) with early return in runner for improved testability

Fixed

  • Fixed missing ALLOW_EMPTY in commit-runner environment variable documentation

Security

  • Fixed minimatch ReDoS vulnerabilities (CVE-2026-27903 / GHSA-7r86-cg39-jmmj) by pinning safe transitive versions via npm overrides.
Changelog

Sourced from vig-os/commit-action's changelog.

Changelog

All notable changes to this project will be documented in this file.

The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.

v0.1.5 - 2026-03-13

Fixed

  • Excluded .git metadata paths during FILE_PATHS directory expansion to prevent malformed Git tree paths (issue #15).

v0.1.4 - 2026-03-11

Added

  • Added ALLOW_EMPTY environment variable support to allow creating signed empty commits when no file changes are detected
  • Added unit test coverage for empty commit behavior in commitViaAPI() and commit-runner flow handling

Changed

  • Updated npm dependency overrides to force patched minimatch versions across transitive dependency trees.
  • Updated commitViaAPI() to support empty commits by reusing the parent tree SHA when ALLOW_EMPTY=true
  • Updated runner behavior to preserve default no-op behavior when no files are detected, unless ALLOW_EMPTY=true
  • Updated README usage examples and environment variable documentation for ALLOW_EMPTY
  • Replaced process.exit(0) with early return in runner for improved testability

Fixed

  • Fixed missing ALLOW_EMPTY in commit-runner environment variable documentation

Security

  • Fixed minimatch ReDoS vulnerabilities (CVE-2026-27903 / GHSA-7r86-cg39-jmmj) by pinning safe transitive versions via npm overrides.

v0.1.3 - 2026-01-28

Added

  • Added TARGET_BRANCH environment variable support to avoid conflicts with GitHub's built-in GITHUB_REF
  • Added normalizeBranch() and resolveBranch() exported functions for branch resolution logic
  • Added comprehensive test suite for branch normalization and resolution (commit-runner.test.ts)

Changed

  • Improved branch resolution logic with explicit priority: TARGET_BRANCH > GITHUB_REF (if different from context) > workflow context
  • Refactored branch resolution into testable exported functions

Fixed

... (truncated)

Commits
  • c0024cb release: Release 0.1.5
  • 3d6eb3a chore: bump action version to 0.1.5
  • 0e52494 chore: prepare CHANGELOG for release 0.1.5
  • ef2addf fix: exclude .git paths when expanding FILE_PATHS directories
  • 873cb5f build(dist): refresh compiled commit-runner test artifacts
  • f2baddf docs(readme): clarify direct .git FILE_PATHS entries are ignored
  • a93945c test(commit-runner): cover direct .git FILE_PATHS and remove require usage
  • 0cc2e65 build(dist): re-bundle artifacts for issue 15 fix
  • 7974cb6 docs(changelog): document issue 15 .git exclusion behavior
  • 74d2d5f fix(commit-runner): skip .git metadata during FILE_PATHS expansion
  • Additional commits viewable in compare view

Updates vig-os/sync-issues-action from 0.1.1 to 0.2.2

Release notes

Sourced from vig-os/sync-issues-action's releases.

v0.2.2

Added

  • Exported shiftHeadersToMinLevel utility function for independent unit testing
  • Sync sub-issue relationships into frontmatter (#8, #15)
    • Fetch parent and subIssues via GraphQL batch query for all synced issues
    • New sync-sub-issues action input to control sub-issue syncing (default: true)
    • Replace hardcoded relationship: none with dynamic parent and children fields
    • Graceful degradation: emits info message and falls back to none if the sub-issues API is unavailable
  • CI/CD pipeline (#13)
    • CI workflow with lint, build-dist verification, and test jobs
    • Integration test suite as a reusable workflow with parallel jobs covering issues-only, PRs-only, force-update, include-closed, sub-issues, updated-since, state-file, and default-mode scenarios
    • Three-phase release pipeline: prepare-release (branch + draft PR), release (tag + GitHub Release with provenance attestation), and post-release (dev sync + CHANGELOG reset)
    • setup-env and build-dist composite actions for consistent environment setup
    • CHANGELOG management CLI (prepare_changelog.py) for automated release note preparation
    • Dependabot configuration for automated dependency updates
    • CODEOWNERS file for automated review assignment
    • CodeQL analysis workflow for automated security vulnerability scanning
    • Scorecard workflow for ongoing supply-chain security assessments
    • Security scan workflow for continuous security monitoring

Changed

  • Sync-issues workflow uses local action checkout (#13)
    • Replaced pinned remote ref with uses: ./ so the workflow always tests the current branch's code
  • Node.js version pinned via .nvmrc (#13)
    • .nvmrc is the single source of truth; setup-env and devcontainer read from it

Fixed

  • Corrected heading hierarchy in formatPRAsMarkdown: promoted the Comments section header from ## to # and individual comment entry headers from ### to ##
  • Release workflow avoids immutable-release upload failures
    • Generates checksums-sha256.txt before creating the GitHub release and attaches it during gh release create instead of uploading afterward
  • Release workflow: floating-tag updates and rollback (#38)
    • Floating-tag updates (vX, vX.Y) run in a separate job after the release job succeeds; main rollback no longer restores floating tags
    • Resolve floating tags via exact "Get a reference" API (git/ref/tags/$TAG) instead of git/matching-refs to avoid wrong-SHA from prefix matches
    • New job captures current SHAs, updates tags, and on failure restores from captured SHAs (self-contained)
  • --force-update does not re-sync issues (only PRs) (#10)
    • Added force-update action input that bypasses the hasContentChanged content-comparison gate
    • When active, all fetched items are re-written (with updated synced: frontmatter) even if body content is unchanged
    • Updated sync-issues.yml workflow to pass the force-update dispatch input to the action
  • Added shiftHeadersToMinLevel helper to re-level headers inside comment bodies so the shallowest header maps to ###, preventing collisions with outer document structure
  • Fixed default GITHUB_REPOSITORY in test-local.sh from non-existent vig-os/actions to vig-os/sync-issues-action
  • Removed broken fallback command in test-local.sh that passed a file path where a directory is required

Security

  • CodeQL and OpenSSF Scorecard analysis workflows (#13)
    • CodeQL scans JavaScript/TypeScript on push and PR
    • Scorecard publishes results to the Security tab via SARIF
Changelog

Sourced from vig-os/sync-issues-action's changelog.

Changelog

All notable changes to this project will be documented in this file.

The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.

Unreleased

Changed

  • Post-release replaced by PR-based main-to-dev sync (#52)
    • Remove post-release.yml workflow; add sync-main-to-dev.yml that opens a PR to sync main into dev, satisfying branch protection on both branches
    • Harden sync checks by failing clearly when origin/main or origin/dev is missing instead of silently treating branches as up to date
    • Fix workflow_dispatch hyphenated input access and conflict path robustness (issues: write, safer conflict label handling, clearer manual resolution commands)
    • Reduce duplicate/no-op sync PR risk by re-checking ahead/behind state inside the sync job and tightening existing-sync-PR detection (search + explicit list limit)
    • Split auth into explicit app tokens by responsibility: COMMIT_APP_* for checkout/ref operations and RELEASE_APP_* for PR/label operations requiring broader scopes
    • Generate RELEASE_APP_* only after re-check confirms sync work remains, reducing unnecessary broader-scope token issuance
  • Sync workflow uses commit-scoped app secrets and manual output target
    • Update sync-issues.yml to use COMMIT_APP_ID/COMMIT_APP_PRIVATE_KEY for both checkout token generation and action app auth inputs
    • Respect workflow_dispatch output-dir input in the action call, with 'docs' as the default fallback

[0.2.2] - 2026-02-26

Added

  • Exported shiftHeadersToMinLevel utility function for independent unit testing
  • Sync sub-issue relationships into frontmatter (#8, #15)
    • Fetch parent and subIssues via GraphQL batch query for all synced issues
    • New sync-sub-issues action input to control sub-issue syncing (default: true)
    • Replace hardcoded relationship: none with dynamic parent and children fields
    • Graceful degradation: emits info message and falls back to none if the sub-issues API is unavailable
  • CI/CD pipeline (#13)
    • CI workflow with lint, build-dist verification, and test jobs
    • Integration test suite as a reusable workflow with parallel jobs covering issues-only, PRs-only, force-update, include-closed, sub-issues, updated-since, state-file, and default-mode scenarios
    • Three-phase release pipeline: prepare-release (branch + draft PR), release (tag + GitHub Release with provenance attestation), and post-release (dev sync + CHANGELOG reset)
    • setup-env and build-dist composite actions for consistent environment setup
    • CHANGELOG management CLI (prepare_changelog.py) for automated release note preparation
    • Dependabot configuration for automated dependency updates
    • CODEOWNERS file for automated review assignment
    • CodeQL analysis workflow for automated security vulnerability scanning
    • Scorecard workflow for ongoing supply-chain security assessments
    • Security scan workflow for continuous security monitoring

Changed

  • Sync-issues workflow uses local action checkout (#13)
    • Replaced pinned remote ref with uses: ./ so the workflow always tests the current branch's code
  • Node.js version pinned via .nvmrc (#13)
    • .nvmrc is the single source of truth; setup-env and devcontainer read from it

... (truncated)

Commits
  • bad447d chore: finalize release 0.2.2
  • 30477c3 chore: prepare release 0.2.2
  • b101f48 fix(release): floating-tag updates in separate job and exact ref resolution
  • eb1e7a7 fix: move floating-tag updates to separate job and resolve tags via exact ref
  • 3c4f799 fix: avoid immutable release upload failures in release workflow
  • 45683e1 chore: update CHANGELOG to reflect unreleased changes
  • df4b531 fix: avoid immutable release upload failures in release workflow
  • 4d4e1ed chore: merge release/0.2.0 back into dev to retrigger prepare release
  • c4cf762 fix: allow reusable workflow permissions in release integration test
  • 2f0beac fix: allow required read permissions for release integration workflow
  • Additional commits viewable in compare view

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 show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore <dependency name> major version will 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 version will 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 conditions

@dependabot
ci(deps): bump the actions-minor-patch group across 1 directory with …
28df254 
…4 updates

Bumps the actions-minor-patch group with 4 updates in the / directory: [actions/dependency-review-action](https://github.com/actions/dependency-review-action), [github/codeql-action](https://github.com/github/codeql-action), [vig-os/commit-action](https://github.com/vig-os/commit-action) and [vig-os/sync-issues-action](https://github.com/vig-os/sync-issues-action).


Updates `actions/dependency-review-action` from 4.8.2 to 4.9.0
- [Release notes](https://github.com/actions/dependency-review-action/releases)
- [Commits](actions/dependency-review-action@3c4e3dc...2031cfc)

Updates `github/codeql-action` from 4.32.2 to 4.32.6
- [Release notes](https://github.com/github/codeql-action/releases)
- [Changelog](https://github.com/github/codeql-action/blob/main/CHANGELOG.md)
- [Commits](github/codeql-action@45cbd0c...0d579ff)

Updates `vig-os/commit-action` from 0.1.3 to 0.1.5
- [Release notes](https://github.com/vig-os/commit-action/releases)
- [Changelog](https://github.com/vig-os/commit-action/blob/main/CHANGELOG.md)
- [Commits](vig-os/commit-action@b70c2d8...c0024cb)

Updates `vig-os/sync-issues-action` from 0.1.1 to 0.2.2
- [Release notes](https://github.com/vig-os/sync-issues-action/releases)
- [Changelog](https://github.com/vig-os/sync-issues-action/blob/main/CHANGELOG.md)
- [Commits](vig-os/sync-issues-action@b4cdf37...bad447d)

---
updated-dependencies:
- dependency-name: actions/dependency-review-action
  dependency-version: 4.9.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: actions-minor-patch
- dependency-name: github/codeql-action
  dependency-version: 4.32.6
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: actions-minor-patch
- dependency-name: vig-os/commit-action
  dependency-version: 0.1.5
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: actions-minor-patch
- dependency-name: vig-os/sync-issues-action
  dependency-version: 0.2.2
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: actions-minor-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot added dependencies Pull requests that update a dependency file github_actions Pull requests that update GitHub Actions code labels Mar 16, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

dependencies Pull requests that update a dependency file github_actions Pull requests that update GitHub Actions code

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants