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

[dependabot]

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

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

Release notes

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

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

• GitHub Actions can't push to our protected main by @​dangoor in actions/dependency-review-action#1017
• Bump actions/stale from 9.1.0 to 10.1.0 by @​dependabot[bot] in actions/dependency-review-action#995
• Bump github/codeql-action from 3 to 4 by @​dependabot[bot] in actions/dependency-review-action#1003
• Bump actions/setup-node from 4 to 6 by @​dependabot[bot] in actions/dependency-review-action#1005
• Upgrade glob to address a vulnerability by @​brrygrdn in actions/dependency-review-action#1024
• Bump js-yaml by @​dependabot[bot] in actions/dependency-review-action#1020
• Addressing vulnerabilities by @​Ahmed3lmallah in actions/dependency-review-action#1036
• Bump fast-xml-parser from 5.3.3 to 5.3.5 by @​dependabot[bot] in actions/dependency-review-action#1050
• Bump fast-xml-parser from 5.3.5 to 5.3.6 by @​dependabot[bot] in actions/dependency-review-action#1053
• Properly truncate long summaries and catch errors by @​juxtin in actions/dependency-review-action#1052
• Bump spdx-expression-parse from 3.0.1 to 4.0.0 in the spdx-licenses group across 1 directory by @​dependabot[bot] in actions/dependency-review-action#931
• Changes for Release 4.8.3 by @​ahpook in actions/dependency-review-action#1054

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

Commits

• 05fe457 Merge pull request #1054 from actions/ahpook/release-4.8.3
• 3a8496c Update generated package files for v4.8.3
• 0f22a01 Update CONTRIBUTING for new release process
• 58be343 Updating package versions for 4.8.3
• 9284e0c Merge pull request #931 from actions/dependabot/npm_and_yarn/spdx-licenses-20...
• 8b76656 Bump spdx-expression-parse in the spdx-licenses group across 1 directory
• 43f5f02 Merge pull request #1052 from actions/juxtin/fix-long-summaries
• f0033fc Merge pull request #1053 from actions/dependabot/npm_and_yarn/fast-xml-parser...
• b379e2e Bump fast-xml-parser from 5.3.5 to 5.3.6
• 2e1cf54 Properly truncate long summaries and catch errors
• Additional commits viewable in compare view

Updates github/codeql-action from 4.32.2 to 4.32.4

Release notes

Sourced from github/codeql-action's releases.

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]

No user facing changes.

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

• A warning is now shown in Default Setup workflow logs if a private package registry is configured using a GitHub Personal Access Token (PAT), but no username is configured. #3422
• Fixed a bug which caused the CodeQL Action to fail when repository properties cannot successfully be retrieved. #3421

4.32.0 - 26 Jan 2026

• Update default CodeQL bundle version to 2.24.0. #3425

4.31.11 - 23 Jan 2026

• When running a Default Setup workflow with Actions debugging enabled, the CodeQL Action will now use more unique names when uploading logs from the Dependabot authentication proxy as workflow artifacts. This ensures that the artifact names do not clash between multiple jobs in a build matrix. #3409
• Improved error handling throughout the CodeQL Action. #3415
• Added experimental support for automatically excluding generated files from the analysis. This feature is not currently enabled for any analysis. In the future, it may be enabled by default for some GitHub-managed analyses. #3318
• The changelog extracts that are included with releases of the CodeQL Action are now shorter to avoid duplicated information from appearing in Dependabot PRs. #3403

4.31.10 - 12 Jan 2026

• Update default CodeQL bundle version to 2.23.9. #3393

4.31.9 - 16 Dec 2025

No user facing changes.

4.31.8 - 11 Dec 2025

... (truncated)

Commits

• 89a39a4 Merge pull request #3494 from github/update-v4.32.4-39ba80c47
• e5d84c8 Apply remaining review suggestions
• 0c20209 Apply suggestions from code review
• 314172e Fix typo
• cdda72d Add changelog entries
• cfda84c Update changelog for v4.32.4
• 39ba80c Merge pull request #3493 from github/update-bundle/codeql-bundle-v2.24.2
• 00150da Add changelog note
• d97dce6 Update default bundle to codeql-bundle-v2.24.2
• 50fdbb9 Merge pull request #3492 from github/henrymercer/new-repository-properties-ff
• 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.

[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

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

... (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]

Looks like these dependencies are updatable in another way, so this is no longer needed.