Skip to content

Bump the actions group across 1 directory with 7 updates - #11

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/github_actions/actions-1a6c0bcb32
Open

dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/github_actions/actions-1a6c0bcb32

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Nov 17, 2026

Copy link
Copy Markdown

Bumps the actions group with 7 updates in the / directory:

Package From To
github/codeql-action/init 4.39.1 4.39.3
github/codeql-action/analyze 4.39.1 4.39.3
actions/setup-dotnet 6.0.0 6.1.0
pironjulien/NexusSystem/.github/workflows/product-dev-release.yml 1.7.2 1.8.0
pironjulien/NexusSystem/.github/workflows/product-promote.yml 1.7.2 1.8.0
github/codeql-action/upload-sarif 4.39.1 4.39.3
zizmorcore/zizmor-action 0.8.0 0.8.1

Updates github/codeql-action/init from 4.39.1 to 4.39.3

Release notes

Sourced from github/codeql-action/init's releases.

v4.39.3

  • Fixed diff-informed alert filtering incorrectly removing alerts in changed files whose paths contain spaces, special characters, or non-ASCII characters. #4283

v4.39.2

  • Update default CodeQL bundle version to 2.27.4. #4284
  • Upcoming breaking change: CodeQL version 2.22.3 and earlier were discontinued on 16 October 2026 alongside GitHub Enterprise Server 3.18, and will be unsupported by the next minor release of the CodeQL Action. Added a deprecation warning for customers using these versions of CodeQL. #4266
  • Starting with macOS 27 and Xcode 27, traced analyses are unsupported. See this blog post for more information. The CodeQL Action will now try to identify if a workflow is about to perform a traced analysis on version 27 or above of macOS or Xcode. If so, the CodeQL Action will emit a corresponding warning that will also be visible on the Tool Status Page. This check will be rolled out following this release of the CodeQL Action. #4221
  • The undocumented TRAP cache cleanup feature that could be enabled using the CODEQL_ACTION_CLEANUP_TRAP_CACHES environment variable has been removed, as announced in the release notes for CodeQL Action 4.35.2. The analyze Action now warns if this environment variable is set. If you used TRAP cache cleanup to limit Actions cache usage, we recommend disabling TRAP caching by passing the trap-caching: false input to the init Action. #4243
Changelog

Sourced from github/codeql-action/init'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.39.3 - 04 Nov 2026

  • Fixed diff-informed alert filtering incorrectly removing alerts in changed files whose paths contain spaces, special characters, or non-ASCII characters. #4283

4.39.2 - 03 Nov 2026

  • Update default CodeQL bundle version to 2.27.4. #4284
  • Upcoming breaking change: CodeQL version 2.22.3 and earlier were discontinued on 16 October 2026 alongside GitHub Enterprise Server 3.18, and will be unsupported by the next minor release of the CodeQL Action. Added a deprecation warning for customers using these versions of CodeQL. #4266
  • Starting with macOS 27 and Xcode 27, traced analyses are unsupported. See this blog post for more information. The CodeQL Action will now try to identify if a workflow is about to perform a traced analysis on version 27 or above of macOS or Xcode. If so, the CodeQL Action will emit a corresponding warning that will also be visible on the Tool Status Page. This check will be rolled out following this release of the CodeQL Action. #4221
  • The undocumented TRAP cache cleanup feature that could be enabled using the CODEQL_ACTION_CLEANUP_TRAP_CACHES environment variable has been removed, as announced in the release notes for CodeQL Action 4.35.2. The analyze Action now warns if this environment variable is set. If you used TRAP cache cleanup to limit Actions cache usage, we recommend disabling TRAP caching by passing the trap-caching: false input to the init Action. #4243

4.39.1 - 21 Oct 2026

  • Update default CodeQL bundle version to 2.27.3. #4256

4.39.0 - 15 Oct 2026

  • Breaking change: Bump the minimum required CodeQL bundle version to 2.20.7. #4205
  • The codeql-action/analyze step now validates that a correct argument for the checkout_path input has been provided. The checkout_path input must be set to the path where the repository that is being analyzed is checked out at on the runner, if that path is something other than the workspace root. If the path does not point to a repository checkout or is different from the path that was used by codeql-action/init, then the CodeQL Action now produces a warning. #4148
  • Resolved an issue with third-party caching implementations that prevented caches from being restored correctly. #4206
  • The codeql-action/start-proxy step that is used in Code Scanning Default Setup now finds CodeQL releases using the same logic as codeql-action/init. This primarily benefits customers who are using GitHub instances other than github.com where the codeql-action/start-proxy step may previously have been unable to locate recent releases and ended up using outdated versions of the private registry authentication proxy as a result. #4198

4.38.3 - 08 Oct 2026

  • Upcoming breaking change: CodeQL version 2.21.2 and earlier were discontinued on 24 September 2026 alongside GitHub Enterprise Server 3.17, and will be unsupported by the next minor release of the CodeQL Action. Added a deprecation warning for customers using these versions of CodeQL. #4188
  • Update default CodeQL bundle version to 2.27.2. #4203
  • Fixed a bug where the decision of whether to use a per-language bundle did not account for custom configurations that reference queries outside of compiled CodeQL packs. This issue was caught during internal testing and did not affect any customer repositories. We will resume the roll out of per-language bundles in the coming weeks. #4184

4.38.2 - 24 Sept 2026

  • Update default CodeQL bundle version to 2.27.1. #4160

4.38.1 - 18 Sept 2026

  • The CodeQL Action now has experimental support for CodeQL releases for which per-language bundles are available. Per-language bundles support analysis for a single language and are therefore smaller than the combined bundles that allow analysis for all supported languages. As a result, per-language bundles take up less space on disk and are faster to download. We expect to roll this change out to everyone in the coming weeks. #4146

4.38.0 - 09 Sept 2026

  • On GitHub-hosted runners, the CodeQL Action now deletes unused CodeQL bundles from the toolcache before downloading a different bundle, which frees up disk space for the analysis. We expect to roll this change out to everyone in September. #4124
  • The CodeQL Action now supports CodeQL releases that are compatible with Linux Arm64 and downloads the native linux-arm64 CodeQL bundle when available. #4072
  • Update default CodeQL bundle version to 2.27.0. #4129

... (truncated)

Commits
  • 33d7b85 Merge pull request #4299 from github/update-v4.39.3-064910ba2
  • 24393f8 Update changelog for v4.39.3
  • 064910b Merge pull request #4297 from github/mbg/update-glob
  • f532ac5 Update glob to 14.0.3
  • 8cd4dfa Merge pull request #4280 from github/mbg/ci/validate-yaml
  • cea289b Return different exit code when a language is not recognised
  • 7287bb3 Remove exclude entry that's no longer needed
  • 8eb7cdf Use normal .editorconfig pattern
  • 160e547 Merge remote-tracking branch 'origin/main' into mbg/ci/validate-yaml
  • 913e1bb Merge pull request #4283 from github/sam-robson/decode-diff-informed-sarif-uris
  • Additional commits viewable in compare view

Updates github/codeql-action/analyze from 4.39.1 to 4.39.3

Release notes

Sourced from github/codeql-action/analyze's releases.

v4.39.3

  • Fixed diff-informed alert filtering incorrectly removing alerts in changed files whose paths contain spaces, special characters, or non-ASCII characters. #4283

v4.39.2

  • Update default CodeQL bundle version to 2.27.4. #4284
  • Upcoming breaking change: CodeQL version 2.22.3 and earlier were discontinued on 16 October 2026 alongside GitHub Enterprise Server 3.18, and will be unsupported by the next minor release of the CodeQL Action. Added a deprecation warning for customers using these versions of CodeQL. #4266
  • Starting with macOS 27 and Xcode 27, traced analyses are unsupported. See this blog post for more information. The CodeQL Action will now try to identify if a workflow is about to perform a traced analysis on version 27 or above of macOS or Xcode. If so, the CodeQL Action will emit a corresponding warning that will also be visible on the Tool Status Page. This check will be rolled out following this release of the CodeQL Action. #4221
  • The undocumented TRAP cache cleanup feature that could be enabled using the CODEQL_ACTION_CLEANUP_TRAP_CACHES environment variable has been removed, as announced in the release notes for CodeQL Action 4.35.2. The analyze Action now warns if this environment variable is set. If you used TRAP cache cleanup to limit Actions cache usage, we recommend disabling TRAP caching by passing the trap-caching: false input to the init Action. #4243
Changelog

Sourced from github/codeql-action/analyze'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.39.3 - 04 Nov 2026

  • Fixed diff-informed alert filtering incorrectly removing alerts in changed files whose paths contain spaces, special characters, or non-ASCII characters. #4283

4.39.2 - 03 Nov 2026

  • Update default CodeQL bundle version to 2.27.4. #4284
  • Upcoming breaking change: CodeQL version 2.22.3 and earlier were discontinued on 16 October 2026 alongside GitHub Enterprise Server 3.18, and will be unsupported by the next minor release of the CodeQL Action. Added a deprecation warning for customers using these versions of CodeQL. #4266
  • Starting with macOS 27 and Xcode 27, traced analyses are unsupported. See this blog post for more information. The CodeQL Action will now try to identify if a workflow is about to perform a traced analysis on version 27 or above of macOS or Xcode. If so, the CodeQL Action will emit a corresponding warning that will also be visible on the Tool Status Page. This check will be rolled out following this release of the CodeQL Action. #4221
  • The undocumented TRAP cache cleanup feature that could be enabled using the CODEQL_ACTION_CLEANUP_TRAP_CACHES environment variable has been removed, as announced in the release notes for CodeQL Action 4.35.2. The analyze Action now warns if this environment variable is set. If you used TRAP cache cleanup to limit Actions cache usage, we recommend disabling TRAP caching by passing the trap-caching: false input to the init Action. #4243

4.39.1 - 21 Oct 2026

  • Update default CodeQL bundle version to 2.27.3. #4256

4.39.0 - 15 Oct 2026

  • Breaking change: Bump the minimum required CodeQL bundle version to 2.20.7. #4205
  • The codeql-action/analyze step now validates that a correct argument for the checkout_path input has been provided. The checkout_path input must be set to the path where the repository that is being analyzed is checked out at on the runner, if that path is something other than the workspace root. If the path does not point to a repository checkout or is different from the path that was used by codeql-action/init, then the CodeQL Action now produces a warning. #4148
  • Resolved an issue with third-party caching implementations that prevented caches from being restored correctly. #4206
  • The codeql-action/start-proxy step that is used in Code Scanning Default Setup now finds CodeQL releases using the same logic as codeql-action/init. This primarily benefits customers who are using GitHub instances other than github.com where the codeql-action/start-proxy step may previously have been unable to locate recent releases and ended up using outdated versions of the private registry authentication proxy as a result. #4198

4.38.3 - 08 Oct 2026

  • Upcoming breaking change: CodeQL version 2.21.2 and earlier were discontinued on 24 September 2026 alongside GitHub Enterprise Server 3.17, and will be unsupported by the next minor release of the CodeQL Action. Added a deprecation warning for customers using these versions of CodeQL. #4188
  • Update default CodeQL bundle version to 2.27.2. #4203
  • Fixed a bug where the decision of whether to use a per-language bundle did not account for custom configurations that reference queries outside of compiled CodeQL packs. This issue was caught during internal testing and did not affect any customer repositories. We will resume the roll out of per-language bundles in the coming weeks. #4184

4.38.2 - 24 Sept 2026

  • Update default CodeQL bundle version to 2.27.1. #4160

4.38.1 - 18 Sept 2026

  • The CodeQL Action now has experimental support for CodeQL releases for which per-language bundles are available. Per-language bundles support analysis for a single language and are therefore smaller than the combined bundles that allow analysis for all supported languages. As a result, per-language bundles take up less space on disk and are faster to download. We expect to roll this change out to everyone in the coming weeks. #4146

4.38.0 - 09 Sept 2026

  • On GitHub-hosted runners, the CodeQL Action now deletes unused CodeQL bundles from the toolcache before downloading a different bundle, which frees up disk space for the analysis. We expect to roll this change out to everyone in September. #4124
  • The CodeQL Action now supports CodeQL releases that are compatible with Linux Arm64 and downloads the native linux-arm64 CodeQL bundle when available. #4072
  • Update default CodeQL bundle version to 2.27.0. #4129

... (truncated)

Commits
  • 33d7b85 Merge pull request #4299 from github/update-v4.39.3-064910ba2
  • 24393f8 Update changelog for v4.39.3
  • 064910b Merge pull request #4297 from github/mbg/update-glob
  • f532ac5 Update glob to 14.0.3
  • 8cd4dfa Merge pull request #4280 from github/mbg/ci/validate-yaml
  • cea289b Return different exit code when a language is not recognised
  • 7287bb3 Remove exclude entry that's no longer needed
  • 8eb7cdf Use normal .editorconfig pattern
  • 160e547 Merge remote-tracking branch 'origin/main' into mbg/ci/validate-yaml
  • 913e1bb Merge pull request #4283 from github/sam-robson/decode-diff-informed-sarif-uris
  • Additional commits viewable in compare view

Updates actions/setup-dotnet from 6.0.0 to 6.1.0

Release notes

Sourced from actions/setup-dotnet's releases.

v6.1.0

What's Changed

Enhancements

Documentation

Dependency Updates

New Contributors

Full Changelog: actions/setup-dotnet@v6.0.0...v6.1.0

Commits
  • 0f4a354 Prepare v6.1.0 release with updated cache dependency (#798)
  • 6ec5c6b Add fallback install directory when default is not writable (#785)
  • 62573f4 Bump brace-expansion (#790)
  • 67290a9 Bump handlebars from 4.7.9 to 4.7.10 (#792)
  • 0072421 Bump actions/checkout from 7.0.0 to 7.0.1 (#788)
  • 9ead317 Bump undici from 6.28.0 to 6.29.1 (#784)
  • 349aa19 Add skip-lts-prepass input to optimize .NET SDK installation process (#791)
  • e2cf7c6 Bump eslint-plugin-jest from 29.15.2 to 29.16.6 (#771)
  • 7576362 Bump eslint from 10.5.0 to 10.11.0 (#772)
  • 074373f Add check-latest input to reuse a locally installed .NET SDK and skip network...
  • Additional commits viewable in compare view

Updates pironjulien/NexusSystem/.github/workflows/product-dev-release.yml from 1.7.2 to 1.8.0

Release notes

Sourced from pironjulien/NexusSystem/.github/workflows/product-dev-release.yml's releases.

NexusSystem 1.8.0

Changed

  • The pack's installation moved from PowerShell to the native engine: get-nexus.ps1 (about 1,500 lines before) is now a minimal bootstrap that downloads NexusMaintenance.exe of its own release, checks its SHA-256 (and its build provenance when gh is signed in) and runs it in the same console. NexusMaintenance.exe --install does everything else, with the same options, plan, messages, checks and summary as before: AI app detection, the plugins of Claude Code and Codex, each product's official installer (its release's get.ps1, checked, now with its build provenance too when gh is there), the exact removal of Codex's old direct declarations, and the hourly task. --install-maintenance, --maintain and --status replace the script's maintenance part; the hand-over contract of the 1.6 PowerShell worker (-Maintain -MaintenanceCurrent) is kept.
  • The "NexusSystem Update" task is registered through the Task Scheduler API (source-generated COM interop, also in the native engine) instead of PowerShell's cmdlets, with the same settings; a task its owner disabled stays disabled.
  • Installing the engine never stops one that runs: it is renamed aside (under a unique name while an older one still runs), put back if the new file cannot take its place, and engines set aside are removed once nothing runs them.
  • Tests: the PowerShell tests of the pack (test_pack.ps1, test_codex_pack.ps1, test_maintenance.ps1) became xUnit tests of the engine (PackInstallerTests, MaintenanceSetupTests: fresh installation, update while an engine runs, failed replacement restored, a real Task Scheduler round trip), and ScriptTests runs the bootstrap with this commit's engine on a throwaway profile.

Fixed

  • A product release's build provenance was refused when the official gh tool was installed but not signed in (exit code 4: it cannot read attestations), so the hourly maintenance failed every product update on such a PC and the new pack check failed on GitHub's runners. That case now checks nothing, as without gh; the SHA-256 is verified anyway, and a real attestation failure stays fatal.
  • get-nexus.ps1 removes the PowerShell worker of releases up to 1.6.54 (~\.nexus\nexussystem\maintenance\get-nexus.ps1) when a development engine is selected as well: on the author's workstation it stayed, and the workstation sync kept installing products with that 1.6 script (07/11/2026). The public installation already removed it.
  • app/tools/sandbox.ps1 stops with the reason when the Windows Sandbox is gone before the guest's result (closed, connection lost, never started: app/tools/sandbox-watch.ps1, checked every 5 s through wsb list, 15 s of grace) instead of waiting until its 30-minute timeout. On 07/11/2026 the Sandbox's connection was lost before the guest's user logon (its logon command never ran) and the script kept waiting.
  • app/tools/sandbox.ps1 can start an unsigned Store package: the Sandbox guest enforces Smart App Control whatever the host's setting and refused app 1.0.18.0, test-signed in the guest, with 0x800711C7. With -Certification on an unsigned package (or -DisableSmartAppControlInGuest) the guest turns it off for itself only before installing and records it in result.json; the host's state must be the same after the run (app/tools/sandbox-policy.ps1, app/tests/test_sandbox_policy.ps1).
  • Tests: no test can show a Windows error box. The test process sets the error mode (no critical-error, crash or missing-file box) when it loads, and every process it starts inherits it; a test checks it in a child process.

NexusSystem 1.7.3

Fixed

  • Maintenance engine: an AI app command line (claude plugin marketplace update, codex plugin ...) could run with no limit, so one stuck command kept the hourly run going until Task Scheduler stopped it at 30 minutes (ExecutionTimeLimit, result 0x41306) and the receipt stayed checking for the next hour. Each command now gets 5 minutes, then is stopped with its child processes and reported with its last output; its standard input is closed instead of inherited. A failed command says why (Claude plugin update failed (exit code N: <its last error line>)) instead of a bare "failed".
  • A cancelled run writes failed (retryable) instead of leaving checking, and a run that finds a checking

... (truncated)

Changelog

Sourced from pironjulien/NexusSystem/.github/workflows/product-dev-release.yml's changelog.

Changelog

All notable changes to NexusSystem are documented here: the plugin catalogs and one-line install (sections [x.y.z], tags vx.y.z) and the Windows app on the Microsoft Store (sections [app a.b.c.d], one per Store version, dated by its last change and linked to the commit that set the version; the site reads the version the Store serves, so app versions have no GitHub release since 1.0.5.0). The format follows Keep a Changelog and the catalogs use Semantic Versioning.

[Unreleased]

Added

  • The Store's release notes are generated: app/tools/package.ps1 -Store writes release-notes.en.txt (the version's [app a.b.c.d] section of this file) and release-notes.fr.txt (the same section of app/store/release-notes.fr.md, its versioned French translation) next to the package, as plain text, and fails before building when a section is missing or empty, the two languages have different entries, or a text exceeds Partner Center's 1,500 characters (app/tools/release-notes.ps1, app/tests/test_release_notes.ps1). App 1.0.19.0 went to the Store with the notes of 1.0.18.0, typed by hand in Partner Center; the hand-written "What's new" of app/store/listing.md is gone.

[app 1.0.20.0] - 2026-11-08

Changed

  • A product's page fits the window: "On this PC", then the help and guides, then what your AI apps did, each card scrolling inside itself when the window is short, and a margin under the product's page of the site.

[app 1.0.19.0] - 2026-11-08

Changed

  • The app no longer extracts and runs get-nexus.ps1 in %TEMP%: when an older installation lacks the maintenance task, it installs the native engine of its catalog release (NexusMaintenance.exe 1.8.0, checked against the release's SHA256SUMS.txt and, when gh is signed in, its build provenance) under %USERPROFILE%\.nexus and registers its task through the Task Scheduler API, in the app's own process.

[1.8.0] - 2026-11-08

Changed

  • The pack's installation moved from PowerShell to the native engine: get-nexus.ps1 (about 1,500 lines before) is now a minimal bootstrap that downloads NexusMaintenance.exe of its own release, checks its SHA-256 (and its build provenance when gh is signed in) and runs it in the same console. NexusMaintenance.exe --install does everything else, with the same options, plan, messages, checks and summary as before: AI app detection, the plugins of Claude Code and Codex, each product's official installer (its release's get.ps1, checked, now with its build provenance too when gh is there), the exact removal of Codex's old direct declarations, and the hourly task. --install-maintenance, --maintain and --status replace the script's maintenance part; the hand-over contract of the 1.6 PowerShell worker (-Maintain -MaintenanceCurrent) is kept.
  • The "NexusSystem Update" task is registered through the Task Scheduler API (source-generated COM interop, also in the native engine) instead of PowerShell's cmdlets, with the same settings; a task its owner disabled stays disabled.
  • Installing the engine never stops one that runs: it is renamed aside (under a unique name while an older one still runs), put back if the new file cannot take its place, and engines set aside are removed once nothing runs them.
  • Tests: the PowerShell tests of the pack (test_pack.ps1, test_codex_pack.ps1, test_maintenance.ps1) became xUnit tests of the engine (PackInstallerTests, MaintenanceSetupTests: fresh installation, update while an

... (truncated)

Commits
  • 0e7bd4e Build provenance: a gh that is not signed in checks nothing instead of failin...
  • 9f7931b Move the pack's installation into the native engine: get-nexus.ps1 becomes a ...
  • d6775a4 Catalog: pin nexus-browser to NexusBrowser v2.36.1
  • 68999bf Catalog: pin nexus-browser to NexusBrowser v2.36.0
  • 7093c6a Add the OpenSSF Best Practices passing badge to the README
  • 5ea66b4 Add CONTRIBUTING.md: how to run test.ps1, contribution rules, a test for ever...
  • f8e3b39 Catalog: pin nexus-browser to NexusBrowser v2.35.32
  • 6b13fd2 Nexus.App.csproj: the project comment says what is true now (unpackaged for l...
  • e6f4b04 sandbox.ps1: the guest turns its own Smart App Control off for an unsigned St...
  • 8a7b075 get-nexus.ps1 removes the 1.6 PowerShell worker on a development workstation ...
  • Additional commits viewable in compare view

Updates pironjulien/NexusSystem/.github/workflows/product-promote.yml from 1.7.2 to 1.8.0

Release notes

Sourced from pironjulien/NexusSystem/.github/workflows/product-promote.yml's releases.

NexusSystem 1.8.0

Changed

  • The pack's installation moved from PowerShell to the native engine: get-nexus.ps1 (about 1,500 lines before) is now a minimal bootstrap that downloads NexusMaintenance.exe of its own release, checks its SHA-256 (and its build provenance when gh is signed in) and runs it in the same console. NexusMaintenance.exe --install does everything else, with the same options, plan, messages, checks and summary as before: AI app detection, the plugins of Claude Code and Codex, each product's official installer (its release's get.ps1, checked, now with its build provenance too when gh is there), the exact removal of Codex's old direct declarations, and the hourly task. --install-maintenance, --maintain and --status replace the script's maintenance part; the hand-over contract of the 1.6 PowerShell worker (-Maintain -MaintenanceCurrent) is kept.
  • The "NexusSystem Update" task is registered through the Task Scheduler API (source-generated COM interop, also in the native engine) instead of PowerShell's cmdlets, with the same settings; a task its owner disabled stays disabled.
  • Installing the engine never stops one that runs: it is renamed aside (under a unique name while an older one still runs), put back if the new file cannot take its place, and engines set aside are removed once nothing runs them.
  • Tests: the PowerShell tests of the pack (test_pack.ps1, test_codex_pack.ps1, test_maintenance.ps1) became xUnit tests of the engine (PackInstallerTests, MaintenanceSetupTests: fresh installation, update while an engine runs, failed replacement restored, a real Task Scheduler round trip), and ScriptTests runs the bootstrap with this commit's engine on a throwaway profile.

Fixed

  • A product release's build provenance was refused when the official gh tool was installed but not signed in (exit code 4: it cannot read attestations), so the hourly maintenance failed every product update on such a PC and the new pack check failed on GitHub's runners. That case now checks nothing, as without gh; the SHA-256 is verified anyway, and a real attestation failure stays fatal.
  • get-nexus.ps1 removes the PowerShell worker of releases up to 1.6.54 (~\.nexus\nexussystem\maintenance\get-nexus.ps1) when a development engine is selected as well: on the author's workstation it stayed, and the workstation sync kept installing products with that 1.6 script (07/11/2026). The public installation already removed it.
  • app/tools/sandbox.ps1 stops with the reason when the Windows Sandbox is gone before the guest's result (closed, connection lost, never started: app/tools/sandbox-watch.ps1, checked every 5 s through wsb list, 15 s of grace) instead of waiting until its 30-minute timeout. On 07/11/2026 the Sandbox's connection was lost before the guest's user logon (its logon command never ran) and the script kept waiting.
  • app/tools/sandbox.ps1 can start an unsigned Store package: the Sandbox guest enforces Smart App Control whatever the host's setting and refused app 1.0.18.0, test-signed in the guest, with 0x800711C7. With -Certification on an unsigned package (or -DisableSmartAppControlInGuest) the guest turns it off for itself only before installing and records it in result.json; the host's state must be the same after the run (app/tools/sandbox-policy.ps1, app/tests/test_sandbox_policy.ps1).
  • Tests: no test can show a Windows error box. The test process sets the error mode (no critical-error, crash or missing-file box) when it loads, and every process it starts inherits it; a test checks it in a child process.

NexusSystem 1.7.3

Fixed

  • Maintenance engine: an AI app command line (claude plugin marketplace update, codex plugin ...) could run with no limit, so one stuck command kept the hourly run going until Task Scheduler stopped it at 30 minutes (ExecutionTimeLimit, result 0x41306) and the receipt stayed checking for the next hour. Each command now gets 5 minutes, then is stopped with its child processes and reported with its last output; its standard input is closed instead of inherited. A failed command says why (Claude plugin update failed (exit code N: <its last error line>)) instead of a bare "failed".
  • A cancelled run writes failed (retryable) instead of leaving checking, and a run that finds a checking

... (truncated)

Changelog

Sourced from pironjulien/NexusSystem/.github/workflows/product-promote.yml's changelog.

Changelog

All notable changes to NexusSystem are documented here: the plugin catalogs and one-line install (sections [x.y.z], tags vx.y.z) and the Windows app on the Microsoft Store (sections [app a.b.c.d], one per Store version, dated by its last change and linked to the commit that set the version; the site reads the version the Store serves, so app versions have no GitHub release since 1.0.5.0). The format follows Keep a Changelog and the catalogs use Semantic Versioning.

[Unreleased]

Added

  • The Store's release notes are generated: app/tools/package.ps1 -Store writes release-notes.en.txt (the version's [app a.b.c.d] section of this file) and release-notes.fr.txt (the same section of app/store/release-notes.fr.md, its versioned French translation) next to the package, as plain text, and fails before building when a section is missing or empty, the two languages have different entries, or a text exceeds Partner Center's 1,500 characters (app/tools/release-notes.ps1, app/tests/test_release_notes.ps1). App 1.0.19.0 went to the Store with the notes of 1.0.18.0, typed by hand in Partner Center; the hand-written "What's new" of app/store/listing.md is gone.

[app 1.0.20.0] - 2026-11-08

Changed

  • A product's page fits the window: "On this PC", then the help and guides, then what your AI apps did, each card scrolling inside itself when the window is short, and a margin under the product's page of the site.

[app 1.0.19.0] - 2026-11-08

Changed

  • The app no longer extracts and runs get-nexus.ps1 in %TEMP%: when an older installation lacks the maintenance task, it installs the native engine of its catalog release (NexusMaintenance.exe 1.8.0, checked against the release's SHA256SUMS.txt and, when gh is signed in, its build provenance) under %USERPROFILE%\.nexus and registers its task through the Task Scheduler API, in the app's own process.

[1.8.0] - 2026-11-08

Changed

  • The pack's installation moved from PowerShell to the native engine: get-nexus.ps1 (about 1,500 lines before) is now a minimal bootstrap that downloads NexusMaintenance.exe of its own release, checks its SHA-256 (and its build provenance when gh is signed in) and runs it in the same console. NexusMaintenance.exe --install does everything else, with the same options, plan, messages, checks and summary as before: AI app detection, the plugins of Claude Code and Codex, each product's official installer (its release's get.ps1, checked, now with its build provenance too when gh is there), the exact removal of Codex's old direct declarations, and the hourly task. --install-maintenance, --maintain and --status replace the script's maintenance part; the hand-over contract of the 1.6 PowerShell worker (-Maintain -MaintenanceCurrent) is kept.
  • The "NexusSystem Update" task is registered through the Task Scheduler API (source-generated COM interop, also in the native engine) instead of PowerShell's cmdlets, with the same settings; a task its owner disabled stays disabled.
  • Installing the engine never stops one that runs: it is renamed aside (under a unique name while an older one still runs), put back if the new file cannot take its place, and engines set aside are removed once nothing runs them.
  • Tests: the PowerShell tests of the pack (test_pack.ps1, test_codex_pack.ps1, test_maintenance.ps1) became xUnit tests of the engine (PackInstallerTests, MaintenanceSetupTests: fresh installation, update while an

... (truncated)

Commits
  • 0e7bd4e Build provenance: a gh that is not signed in checks nothing instead of failin...
  • 9f7931b Move the pack's installation into the native engine: get-nexus.ps1 becomes a ...
  • d6775a4 Catalog: pin nexus-browser to NexusBrowser v2.36.1
  • 68999bf Catalog: pin nexus-browser to NexusBrowser v2.36.0
  • 7093c6a Add the OpenSSF Best Practices passing badge to the README
  • 5ea66b4 Add CONTRIBUTING.md: how to run test.ps1, contribution rules, a test for ever...
  • f8e3b39 Catalog: pin nexus-browser to NexusBrowser v2.35.32
  • 6b13fd2 Nexus.App.csproj: the project comment says what is true now (unpackaged for l...
  • e6f4b04 sandbox.ps1: the guest turns its own Smart App Control off for an unsigned St...
  • 8a7b075 get-nexus.ps1 removes the 1.6 PowerShell worker on a development workstation ...
  • Additional commits viewable in compare view

Updates github/codeql-action/upload-sarif from 4.39.1 to 4.39.3

Release notes

Sourced from github/codeql-action/upload-sarif's releases.

v4.39.3

  • Fixed diff-informed alert filtering incorrectly removing alerts in changed files whose paths contain spaces, special characters, or non-ASCII characters. #4283

v4.39.2

  • Update default CodeQL bundle version to 2.27.4. #4284
  • Upcoming breaking change: CodeQL version 2.22.3 and earlier were discontinued on 16 October 2026 alongside GitHub Enterprise Server 3.18, and will be unsupported by the next minor release of the CodeQL Action. Added a deprecation warning for customers using these versions of CodeQL. #4266
  • Starting with macOS 27 and Xcode 27, traced analyses are unsupported. See this blog post for more information. The CodeQL Action will now try to identify if a workflow is about to perform a traced analysis on version 27 or above of macOS or Xcode. If so, the CodeQL Action will emit a corresponding warning that will also be visible on the Tool Status Page. This check will be rolled out following this release of the CodeQL Action. #4221
  • The undocumented TRAP cache cleanup feature that could be enabled using the CODEQL_ACTION_CLEANUP_TRAP_CACHES environment variable has been removed, as announced in the release notes for CodeQL Action 4.35.2. The analyze Action now warns if this environment variable is set. If you used TRAP cache cleanup to limit Actions cache usage, we recommend disabling TRAP caching by passing the trap-caching: false input to the init Action. #4243
Changelog

Sourced from github/codeql-action/upload-sarif'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.39.3 - 04 Nov 2026

  • Fixed diff-informed alert filtering incorrectly removing alerts in changed files whose paths contain spaces, special characters, or non-ASCII characters. #4283

4.39.2 - 03 Nov 2026

  • Update default CodeQL bundle version to 2.27.4. #4284
  • Upcoming breaking change: CodeQL version 2.22.3 and earlier were discontinued on 16 October 2026 alongside GitHub Enterprise Server 3.18, and will be unsupported by the next minor release of the CodeQL Action. Added a deprecation warning for customers using these versions of CodeQL. #4266
  • Starting with macOS 27 and Xcode 27, traced analyses are unsupported. See this blog post for more information. The CodeQL Action will now try to identify if a workflow is about to perform a traced analysis on version 27 or above of macOS or Xcode. If so, the CodeQL Action will emit a corresponding warning that will also be visible on the Tool Status Page. This check will be rolled out following this release of the CodeQL Action. #4221
  • The undocumented TRAP cache cleanup feature that could be enabled using the CODEQL_ACTION_CLEANUP_TRAP_CACHES environment variable has been removed, as announced in the release notes for CodeQL Action 4.35.2. The analyze Action now warns if this environment variable is set. If you used TRAP cache cleanup to limit Actions cache usage, we recommend disabling TRAP caching by passing the trap-caching: false input to the init Action. #4243

4.39.1 - 21 Oct 2026

  • Update default CodeQL bundle version to 2.27.3. #4256

4.39.0 - 15 Oct 2026

  • Breaking change: Bump the minimum required CodeQL bundle version to 2.20.7. #4205
  • The codeql-action/analyze step now validates that a correct argument for the checkout_path input has been provided. The checkout_path input must be set to the path where the repository that is being analyzed is checked out at on the runner, if that path is something other than the workspace root. If the path does not point to a repository checkout or is different from the path that was used by codeql-action/init, then the CodeQL Action now produces a warning. #4148
  • Resolved an issue with third-party caching implementations that prevented caches from being restored correctly. #4206
  • The codeql-action/start-proxy step that is used in Code Scanning Default Setup now finds CodeQL releases using the same logic as codeql-action/init. This primarily benefits customers who are using GitHub instances other than github.com where the codeql-action/start-proxy step may previously have been unable to locate recent releases and ended up using outdated versions of the private registry authentication proxy as a result. #4198

4.38.3 - 08 Oct 2026

  • Upcoming breaking change: CodeQL version 2.21.2 and earlier were discontinued on 24 September 2026 alongside GitHub Enterprise Server 3.17, and will be unsupported by the next minor release of the CodeQL Action. Added a deprecation warning for customers using these versions of CodeQL.

Bumps the actions group with 7 updates in the / directory:

| Package | From | To |
| --- | --- | --- |
| [github/codeql-action/init](https://github.com/github/codeql-action) | `4.39.1` | `4.39.3` |
| [github/codeql-action/analyze](https://github.com/github/codeql-action) | `4.39.1` | `4.39.3` |
| [actions/setup-dotnet](https://github.com/actions/setup-dotnet) | `6.0.0` | `6.1.0` |
| [pironjulien/NexusSystem/.github/workflows/product-dev-release.yml](https://github.com/pironjulien/nexussystem) | `1.7.2` | `1.8.0` |
| [pironjulien/NexusSystem/.github/workflows/product-promote.yml](https://github.com/pironjulien/nexussystem) | `1.7.2` | `1.8.0` |
| [github/codeql-action/upload-sarif](https://github.com/github/codeql-action) | `4.39.1` | `4.39.3` |
| [zizmorcore/zizmor-action](https://github.com/zizmorcore/zizmor-action) | `0.8.0` | `0.8.1` |



Updates `github/codeql-action/init` from 4.39.1 to 4.39.3
- [Release notes](https://github.com/github/codeql-action/releases)
- [Changelog](https://github.com/github/codeql-action/blob/main/CHANGELOG.md)
- [Commits](github/codeql-action@9b32540...33d7b85)

Updates `github/codeql-action/analyze` from 4.39.1 to 4.39.3
- [Release notes](https://github.com/github/codeql-action/releases)
- [Changelog](https://github.com/github/codeql-action/blob/main/CHANGELOG.md)
- [Commits](github/codeql-action@9b32540...33d7b85)

Updates `actions/setup-dotnet` from 6.0.0 to 6.1.0
- [Release notes](https://github.com/actions/setup-dotnet/releases)
- [Commits](actions/setup-dotnet@a98b568...0f4a354)

Updates `pironjulien/NexusSystem/.github/workflows/product-dev-release.yml` from 1.7.2 to 1.8.0
- [Release notes](https://github.com/pironjulien/nexussystem/releases)
- [Changelog](https://github.com/pironjulien/NexusSystem/blob/main/CHANGELOG.md)
- [Commits](pironjulien/NexusSystem@6a66dbe...0e7bd4e)

Updates `pironjulien/NexusSystem/.github/workflows/product-promote.yml` from 1.7.2 to 1.8.0
- [Release notes](https://github.com/pironjulien/nexussystem/releases)
- [Changelog](https://github.com/pironjulien/NexusSystem/blob/main/CHANGELOG.md)
- [Commits](pironjulien/NexusSystem@6a66dbe...0e7bd4e)

Updates `github/codeql-action/upload-sarif` from 4.39.1 to 4.39.3
- [Release notes](https://github.com/github/codeql-action/releases)
- [Changelog](https://github.com/github/codeql-action/blob/main/CHANGELOG.md)
- [Commits](github/codeql-action@9b32540...33d7b85)

Updates `zizmorcore/zizmor-action` from 0.8.0 to 0.8.1
- [Release notes](https://github.com/zizmorcore/zizmor-action/releases)
- [Commits](zizmorcore/zizmor-action@53290ba...45d7276)

---
updated-dependencies:
- dependency-name: github/codeql-action/init
  dependency-version: 4.39.3
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: actions
- dependency-name: github/codeql-action/analyze
  dependency-version: 4.39.3
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: actions
- dependency-name: actions/setup-dotnet
  dependency-version: 6.1.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: actions
- dependency-name: pironjulien/NexusSystem/.github/workflows/product-dev-release.yml
  dependency-version: 1.8.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: actions
- dependency-name: pironjulien/NexusSystem/.github/workflows/product-promote.yml
  dependency-version: 1.8.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: actions
- dependency-name: github/codeql-action/upload-sarif
  dependency-version: 4.39.3
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: actions
- dependency-name: zizmorcore/zizmor-action
  dependency-version: 0.8.1
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: actions
...

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 Nov 17, 2026

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants