Skip to content

chore(deps): bump the actions group with 6 updates - #52

Merged
hyperpolymath merged 1 commit into
mainfrom
dependabot/github_actions/actions-8fa58e6768
Oct 10, 2026
Merged

hyperpolymath merged 1 commit into
mainfrom
dependabot/github_actions/actions-8fa58e6768

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Oct 9, 2026

Copy link
Copy Markdown
Contributor

Bumps the actions group with 6 updates:

Package From To
julia-actions/cache 3.4.0 3.5.0
julia-actions/julia-runtest 1.10.0 1.12.0
github/codeql-action/init 3.35.2 4.38.2
github/codeql-action/analyze 3.35.2 4.38.2
dtolnay/rust-toolchain 7e38f4b43b4db5c8dd498af069a4f6196df1d067 e2a55d2ffb04f378e9626c28d38b36d230d1e12f
hyperpolymath/smtp-notify-action 0.3.0 0.5.0

Updates julia-actions/cache from 3.4.0 to 3.5.0

Release notes

Sourced from julia-actions/cache's releases.

v3.5.0

What's Changed

We improved the behavior of the action if a restore from Google Cloud Platform fails part-way (#264).

We also updated some dependencies.

Full Changelog

Full Changelog: julia-actions/cache@v3.4.0...v3.5.0

Commits
  • 9353db0 Unpack a GCS restore into a staging directory so a failed stream leaves the d...
  • 3ea528d Bump @​vercel/ncc from 0.44.1 to 0.45.0 (#261)
  • 9e2ba38 Bump @​google-cloud/storage from 7.21.0 to 8.2.0 (#269)
  • 174ab9a Bump undici from 6.28.0 to 6.29.0 (#267)
  • 8d0370f Bump brace-expansion from 1.1.18 to 1.1.21 (#271)
  • 9509e92 Bump @​types/node from 24.13.3 to 26.6.2 (#270)
  • See full diff in compare view

Updates julia-actions/julia-runtest from 1.10.0 to 1.12.0

Release notes

Sourced from julia-actions/julia-runtest's releases.

v1.12.0

What's Changed

Maintenance

New Contributors

Full Changelog: julia-actions/julia-runtest@v1.11.5...v1.12.0

v1.11.5

What's Changed

Full Changelog: julia-actions/julia-runtest@v1.11.4...v1.11.5

v1.11.4

What's Changed

Maintenance

Full Changelog: julia-actions/julia-runtest@v1.11.3...v1.11.4

v1.11.3

What's Changed

Maintenance

... (truncated)

Commits

Updates github/codeql-action/init from 3.35.2 to 4.38.2

Release notes

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

v4.38.2

  • Update default CodeQL bundle version to 2.27.1. #4160

v4.38.1

  • 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

v4.38.0

  • 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

v4.37.9

  • Update default CodeQL bundle version to 2.26.4. #4106

v4.37.8

No user facing changes.

v4.37.7

  • Update default CodeQL bundle version to 2.26.3. #4085

v4.37.6

  • Changed the default filepath for the new remote file address format that was introduced in CodeQL Action 4.37.0 / 3.37.0 to .github/codeql-config.yml to align it with the suggested path that is used elsewhere. #4070

v4.37.5

  • Fixed a bug where a network error while streaming the download of the CodeQL bundle could terminate the init Action instead of falling back to downloading the bundle before extracting it. #4061

v4.37.4

  • This version of the CodeQL Action adds support for the tools input for the codeql-action/init step to be specified using a github-codeql-tools repository property. This feature will gradually be rolled out following the release of this version. Once rolled out, this allows for the CodeQL CLI version that is used in GitHub-managed workflows, such as Default Setup, to be set to a custom value. For example, customers who run into issues with rate limits when a new CodeQL CLI version is released can set the value to toolcache to always use the CodeQL CLI version that is available in the runner toolcache. For Advanced Setup workflows, the value provided for tools in the workflow definition always takes precedence unless the value of the repository property starts with !. #4037
  • Update default CodeQL bundle version to 2.26.2. #4051

v4.37.3

No user facing changes.

v4.37.2

  • The new address format for the config-file input that was introduced in CodeQL Action 4.37.0 is now enabled by default. In addition to the format described there, the remote= prefix can now be used to explicitly indicate that the input refers to a remote file. All previous input formats continue to be accepted as well. #4023
  • The CodeQL Action can now make use of configured private registries in Default Setup to retrieve CodeQL configuration files from remote repositories that require authentication. This will allow customers to store their CodeQL configuration in a single repository that can then be referenced by Default Setup workflows in other repositories. We expect to roll this and other, related changes out to everyone in July. #4007

v4.37.1

  • Upcoming breaking change: Add a deprecation warning for customers using CodeQL version 2.20.6 and earlier. These versions of CodeQL were discontinued on 1 July 2026 alongside GitHub Enterprise Server 3.16, and will be unsupported by the next minor release of the CodeQL Action. #3956
  • Update default CodeQL bundle version to 2.26.1. #4019

v4.37.0

  • Update default CodeQL bundle version to 2.26.0. #3995
  • In addition to the existing input format, the config-file input for the codeql-action/init step will soon support a new [owner/]repo[@ref][:path] format. All components except the repository name are optional. If omitted, owner defaults to the same owner as the repository the analysis is running for, ref to main, and path to .github/codeql-action.yaml. Support for this format ships in this version of the CodeQL Action, but will only be enabled over the coming weeks. #3973

v4.36.3

No user facing changes.

v4.36.2

  • Cache CodeQL CLI version information across Actions steps. #3943

... (truncated)

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

4.37.9 - 26 Aug 2026

  • Update default CodeQL bundle version to 2.26.4. #4106

4.37.8 - 21 Aug 2026

No user facing changes.

4.37.7 - 13 Aug 2026

  • Update default CodeQL bundle version to 2.26.3. #4085

4.37.6 - 04 Aug 2026

  • Changed the default filepath for the new remote file address format that was introduced in CodeQL Action 4.37.0 / 3.37.0 to .github/codeql-config.yml to align it with the suggested path that is used elsewhere. #4070

4.37.5 - 03 Aug 2026

  • Fixed a bug where a network error while streaming the download of the CodeQL bundle could terminate the init Action instead of falling back to downloading the bundle before extracting it. #4061

4.37.4 - 29 Jul 2026

... (truncated)

Commits
  • 2892aa5 Merge pull request #4168 from github/update-v4.38.2-a6ef2c96f
  • 8ad03a3 Trigger workflows
  • 98af865 Update changelog for v4.38.2
  • a6ef2c9 Merge pull request #4156 from github/mario-campos/fix-validate-cmd
  • 1ef28a1 Merge pull request #4166 from github/dependabot/github_actions/dot-github/wor...
  • 26cb08b Merge pull request #4163 from github/mbg/fix-getCommitOid-stubs
  • f035ce3 Merge pull request #4165 from github/dependabot/npm_and_yarn/npm-minor-8eaed9...
  • 5e4e255 Rebuild
  • b13f5f4 Bump ruby/setup-ruby
  • c87fe57 Rebuild
  • Additional commits viewable in compare view

Updates github/codeql-action/analyze from 3.35.2 to 4.38.2

Release notes

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

v4.38.2

  • Update default CodeQL bundle version to 2.27.1. #4160

v4.38.1

  • 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

v4.38.0

  • 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

v4.37.9

  • Update default CodeQL bundle version to 2.26.4. #4106

v4.37.8

No user facing changes.

v4.37.7

  • Update default CodeQL bundle version to 2.26.3. #4085

v4.37.6

  • Changed the default filepath for the new remote file address format that was introduced in CodeQL Action 4.37.0 / 3.37.0 to .github/codeql-config.yml to align it with the suggested path that is used elsewhere. #4070

v4.37.5

  • Fixed a bug where a network error while streaming the download of the CodeQL bundle could terminate the init Action instead of falling back to downloading the bundle before extracting it. #4061

v4.37.4

  • This version of the CodeQL Action adds support for the tools input for the codeql-action/init step to be specified using a github-codeql-tools repository property. This feature will gradually be rolled out following the release of this version. Once rolled out, this allows for the CodeQL CLI version that is used in GitHub-managed workflows, such as Default Setup, to be set to a custom value. For example, customers who run into issues with rate limits when a new CodeQL CLI version is released can set the value to toolcache to always use the CodeQL CLI version that is available in the runner toolcache. For Advanced Setup workflows, the value provided for tools in the workflow definition always takes precedence unless the value of the repository property starts with !. #4037
  • Update default CodeQL bundle version to 2.26.2. #4051

v4.37.3

No user facing changes.

v4.37.2

  • The new address format for the config-file input that was introduced in CodeQL Action 4.37.0 is now enabled by default. In addition to the format described there, the remote= prefix can now be used to explicitly indicate that the input refers to a remote file. All previous input formats continue to be accepted as well. #4023
  • The CodeQL Action can now make use of configured private registries in Default Setup to retrieve CodeQL configuration files from remote repositories that require authentication. This will allow customers to store their CodeQL configuration in a single repository that can then be referenced by Default Setup workflows in other repositories. We expect to roll this and other, related changes out to everyone in July. #4007

v4.37.1

  • Upcoming breaking change: Add a deprecation warning for customers using CodeQL version 2.20.6 and earlier. These versions of CodeQL were discontinued on 1 July 2026 alongside GitHub Enterprise Server 3.16, and will be unsupported by the next minor release of the CodeQL Action. #3956
  • Update default CodeQL bundle version to 2.26.1. #4019

v4.37.0

  • Update default CodeQL bundle version to 2.26.0. #3995
  • In addition to the existing input format, the config-file input for the codeql-action/init step will soon support a new [owner/]repo[@ref][:path] format. All components except the repository name are optional. If omitted, owner defaults to the same owner as the repository the analysis is running for, ref to main, and path to .github/codeql-action.yaml. Support for this format ships in this version of the CodeQL Action, but will only be enabled over the coming weeks. #3973

v4.36.3

No user facing changes.

v4.36.2

  • Cache CodeQL CLI version information across Actions steps. #3943

... (truncated)

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

4.37.9 - 26 Aug 2026

  • Update default CodeQL bundle version to 2.26.4. #4106

4.37.8 - 21 Aug 2026

No user facing changes.

4.37.7 - 13 Aug 2026

  • Update default CodeQL bundle version to 2.26.3. #4085

4.37.6 - 04 Aug 2026

  • Changed the default filepath for the new remote file address format that was introduced in CodeQL Action 4.37.0 / 3.37.0 to .github/codeql-config.yml to align it with the suggested path that is used elsewhere. #4070

4.37.5 - 03 Aug 2026

  • Fixed a bug where a network error while streaming the download of the CodeQL bundle could terminate the init Action instead of falling back to downloading the bundle before extracting it. #4061

4.37.4 - 29 Jul 2026

... (truncated)

Commits
  • 2892aa5 Merge pull request #4168 from github/update-v4.38.2-a6ef2c96f
  • 8ad03a3 Trigger workflows
  • 98af865 Update changelog for v4.38.2
  • a6ef2c9 Merge pull request #4156 from github/mario-campos/fix-validate-cmd
  • 1ef28a1 Merge pull request #4166 from github/dependabot/github_actions/dot-github/wor...
  • 26cb08b Merge pull request #4163 from github/mbg/fix-getCommitOid-stubs
  • f035ce3 Merge pull request #4165 from github/dependabot/npm_and_yarn/npm-minor-8eaed9...
  • 5e4e255 Rebuild
  • b13f5f4 Bump ruby/setup-ruby
  • c87fe57 Rebuild
  • Additional commits viewable in compare view

Updates dtolnay/rust-toolchain from 7e38f4b43b4db5c8dd498af069a4f6196df1d067 to e2a55d2ffb04f378e9626c28d38b36d230d1e12f

Commits

Updates hyperpolymath/smtp-notify-action from 0.3.0 to 0.5.0

Release notes

Sourced from hyperpolymath/smtp-notify-action's releases.

v0.5.0

Newsgroup posting, on the same binary

protocol: nntp with newsgroups posts one article over implicit TLS (NNTPS, 563) or STARTTLS on the news port (RFC 4642, 119), authenticating with AUTHINFO USER/PASS. Transport selection is fail-closed and unchanged in shape from the SMTP path: a server that does not advertise the upgrade is refused before any credential is written.

Refusals name their own reason, including the two 4xx codes that are not retries — 440 at POST and 441 at the article, where a class-only rule would have advised a retry and duplicated the post. Malformed newsgroups and CR/LF in a header-bound value are refused before the socket is opened. The body is dot-stuffed on the wire and a Message-ID is generated per run.

The NNTP session is a second proven contract — spec/Nntp/ (6 rows implicit, 8 with STARTTLS, plus the Newsgroups grammar and newsgroupsNoInjection) — emitted into the same src/generated/smtp_fsm.zig, so the existing drift gate covers it. The SMTP section of that file is unchanged.

The Marketplace listing can finally be published

The publish form refuses a description of 125 characters or more (measured on the parsed value, so a folded scalar does not hide it) and reads action.yml from the release tag — which is why this ships as a tag rather than a commit on main. The description is now 110 characters with STARTTLS and 365 in it; the full text lives in the README, which the listing page renders. scripts/check-action.sh and the action-metadata job keep the limit from regressing, with a selftest proving 125 is refused and 124 accepted.

server_port now defaults to empty, meaning the port the protocol and transport imply: SMTP 465/587/25, NNTP 563/119.

Provenance

CI rebuilt both static musl binaries from this tag and verified they hash to exactly the SHA-256 pins inside this tag's action.yml before publishing. SHA256SUMS is attached:

2683da8f619dd5f310c9f6884da39e825c807c2c86a6319c19aba39b27f9c5c9  smtp-notify-x86_64-linux-musl
a58138308fb9832e1ceb551a12f1b04e591dc38ba5fd336c9acfb3f263161f29  smtp-notify-aarch64-linux-musl

See CHANGELOG.adoc for the full entry, and KNOWN-DEFECTS.adoc for what is not proven — notably D-015: no real news server has ever seen this code; the end-to-end evidence is a containerised fixture.

v0.4.0

Static, byte-reproducible smtp-notify binaries. CI rebuilt them from this tag and verified they hash to exactly the SHA-256 pins inside this tag's action.yml before publishing.

Changelog

Sourced from hyperpolymath/smtp-notify-action's changelog.

// SPDX-License-Identifier: MPL-2.0 = Changelog :toc: macro :toclevels: 2

All notable changes to this action are recorded here. The format follows https://keepachangelog.com/en/1.1.0/[Keep a Changelog]; versions follow https://semver.org/spec/v2.0.0.html[Semantic Versioning].

The unit of release is the action ref: the tag or commit you pin determines both action.yml and, through the SHA-256 pins inside it, the exact binary that runs.

toc::[]

== v0.5.0 — 2026-10-04

Newsgroup posting, and the release that can finally be listed on the GitHub Marketplace. The two are one release because the description fix can only take effect from a tag — the Marketplace validates action.yml at the release's tag, not on main — and a tag is what this release is for.

NOTE: The tag must be pushed immediately after this merge. Between the two, the tagged commit's action.yml names v0.5.0 assets that do not exist yet, and @main inherits that window; the release workflow refuses to publish unless the asset URL equals the tag, so the window is a property of the release process rather than of this tree. If the tag lands on a later day, correct this heading with a follow-up commit, as was done for v0.4.0.

=== Added

  • protocol input (smtp | nntp, default smtp), chosen explicitly and never inferred. newsgroups set while protocol is smtp fails the step naming the mismatch, and protocol: nntp without newsgroups fails too, rather than either combination being guessed at.
  • NNTP posting — one article per run. Implicit TLS (NNTPS, normally 563) or STARTTLS on the cleartext news port (RFC 4642, normally 119), with AUTHINFO USER/PASS (RFC 4643). The article carries From, Newsgroups, Subject (RFC 2047 for non-ASCII), Date, a generated Message-ID, optional Content-Language, MIME-Version, Content-Type and Content-Transfer-Encoding; the body is dot-stuffed on the wire. The STARTTLS path re-reads CAPABILITIES after the upgrade, as RFC 4642 §2.2 requires, and a server that does not advertise the upgrade is refused rather than posted to in the clear.
  • A second proven contract. spec/Nntp/StateMachine.idr and spec/Nntp/Serialize.idr hold the NNTP session tables (6 rows implicit, 8 with STARTTLS) and the Newsgroups grammar, with the same style of properties as the SMTP spec: deterministic coverage, termination, ordering, and that the upgrade is on the walked path — plus newsgroupsNoInjection, the analogue of the Content-Language theorem. Both emit into the same src/generated/smtp_fsm.zig, so the existing drift gate covers them; the

... (truncated)

Commits
  • c1c9fa0 feat(nntp): NNTP posting + unblock the Marketplace listing (needs tag v0.5.0)...
  • 7ea6d7a docs(changelog): date v0.4.0 at its actual tag push (#26)
  • 170f53a ci(secret-scan): canonical estate scanner caller, key scan (D243) (#25)
  • 9f3f89f docs: add Signed commits section to CONTRIBUTING (#24)
  • acd2d3d fix: address CodeRabbit review of #21 — CertificateRequest shape checks, benc...
  • c9b6790 fix: CodeRabbit auto-fixes for PR #21 (#22)
  • 10f080a fix/issue 6 hardening (#21)
  • 5574cdc Resolve community health, accessibility, diagnostics, and benchmark debt
  • 106e28f fix(ci): reconcile the workflows with actions.lock (gh-actions-lock) (#19)
  • 2c98910 fix(ci): pin third-party actions to full commit SHAs (#18)
  • 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

Bumps the actions group with 6 updates:

| Package | From | To |
| --- | --- | --- |
| [julia-actions/cache](https://github.com/julia-actions/cache) | `3.4.0` | `3.5.0` |
| [julia-actions/julia-runtest](https://github.com/julia-actions/julia-runtest) | `1.10.0` | `1.12.0` |
| [github/codeql-action/init](https://github.com/github/codeql-action) | `3.35.2` | `4.38.2` |
| [github/codeql-action/analyze](https://github.com/github/codeql-action) | `3.35.2` | `4.38.2` |
| [dtolnay/rust-toolchain](https://github.com/dtolnay/rust-toolchain) | `7e38f4b43b4db5c8dd498af069a4f6196df1d067` | `e2a55d2ffb04f378e9626c28d38b36d230d1e12f` |
| [hyperpolymath/smtp-notify-action](https://github.com/hyperpolymath/smtp-notify-action) | `0.3.0` | `0.5.0` |


Updates `julia-actions/cache` from 3.4.0 to 3.5.0
- [Release notes](https://github.com/julia-actions/cache/releases)
- [Commits](julia-actions/cache@e32267b...9353db0)

Updates `julia-actions/julia-runtest` from 1.10.0 to 1.12.0
- [Release notes](https://github.com/julia-actions/julia-runtest/releases)
- [Commits](julia-actions/julia-runtest@d0c4f09...6e050c8)

Updates `github/codeql-action/init` from 3.35.2 to 4.38.2
- [Release notes](https://github.com/github/codeql-action/releases)
- [Changelog](https://github.com/github/codeql-action/blob/main/CHANGELOG.md)
- [Commits](github/codeql-action@ce64ddc...2892aa5)

Updates `github/codeql-action/analyze` from 3.35.2 to 4.38.2
- [Release notes](https://github.com/github/codeql-action/releases)
- [Changelog](https://github.com/github/codeql-action/blob/main/CHANGELOG.md)
- [Commits](github/codeql-action@ce64ddc...2892aa5)

Updates `dtolnay/rust-toolchain` from 7e38f4b43b4db5c8dd498af069a4f6196df1d067 to e2a55d2ffb04f378e9626c28d38b36d230d1e12f
- [Release notes](https://github.com/dtolnay/rust-toolchain/releases)
- [Commits](dtolnay/rust-toolchain@7e38f4b...e2a55d2)

Updates `hyperpolymath/smtp-notify-action` from 0.3.0 to 0.5.0
- [Release notes](https://github.com/hyperpolymath/smtp-notify-action/releases)
- [Changelog](https://github.com/hyperpolymath/smtp-notify-action/blob/main/CHANGELOG.adoc)
- [Commits](hyperpolymath/smtp-notify-action@22e7bdb...c1c9fa0)

---
updated-dependencies:
- dependency-name: julia-actions/cache
  dependency-version: 3.5.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: actions
- dependency-name: julia-actions/julia-runtest
  dependency-version: 1.12.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: actions
- dependency-name: github/codeql-action/init
  dependency-version: 4.38.2
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: actions
- dependency-name: github/codeql-action/analyze
  dependency-version: 4.38.2
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: actions
- dependency-name: dtolnay/rust-toolchain
  dependency-version: e2a55d2ffb04f378e9626c28d38b36d230d1e12f
  dependency-type: direct:production
  dependency-group: actions
- dependency-name: hyperpolymath/smtp-notify-action
  dependency-version: 0.5.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  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 Oct 9, 2026
@coderabbitai

coderabbitai Bot commented Oct 9, 2026

Copy link
Copy Markdown
Contributor

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration
  • Configuration used: Organization UI
  • Review profile: ASSERTIVE
  • Plan: Advanced
  • Run ID: e20288a3-1216-409f-a2fc-04942e86c0c8

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@hyperpolymath
hyperpolymath merged commit c742bb3 into main Oct 10, 2026
35 of 36 checks passed
@hyperpolymath
hyperpolymath deleted the dependabot/github_actions/actions-8fa58e6768 branch October 10, 2026 10:19
hyperpolymath added a commit that referenced this pull request Oct 10, 2026
… fix the CI-hygiene wave (#58–#62) (#63)

## Summary

Executes the ultraplan in `ULTRAPLAN-ISSUE-43.adoc` (first commit):
records the #43 determinations, fixes the five fixable recon findings,
and retires two mis-created probe issues. Closes #43.

## #43 triage record (issue writes are blocked for this integration —
recorded here)

The Arena integration carries `issues: read`: it can create issues but
not comment, edit bodies, tick checkboxes, add labels or close. The #43
determinations therefore live here; the issue closes via the `Closes`
keyword below.

**Root cause of all 9 red checks:** every `test (*)` job died at *setup*
on
`julia-actions/julia-runtest@79a7e100883947123f8263c5f06e6c2fee60dd0c` —
a SHA that exists in no upstream ref (30-hex prefix collision with real
v1.9.3 `79a7e100…c0ea3eb972f`). No test ever ran; all 9 were
pre-existing on `main` @ `553d49e` (2026-09-20), i.e. the
TOOLING-VERSION-INTEGRITY "never ran" failure class, not 9 independent
test failures.

**Determinations — all 9 `fixed`** (18/18 checkboxes would be ticked
were the API able):

| Check in #43 | Determination | Evidence |
|---|---|---|
| `test (1.10, {ubuntu,macos,windows}-latest, x64)` | **fixed** →
successors `test (1.10, <os>)` green on `main` | PR #48 (`487c7ab4`)
re-pinned `julia-runtest@d0c4f093…` = v1.10.0, verified via `git
ls-remote`; PR #49 (`14da03a7`) fixed the 12 suite failures at root
cause; CI run `37921988068` on `main` @ `126ced1` — 9/9 success |
| `test (1.11, {ubuntu,macos,windows}-latest, x64)` | **fixed** → `test
(1.11, <os>)` | same |
| `test (nightly, {ubuntu,macos,windows}-latest, x64)` | **fixed** →
`test (nightly, <os>)` | same |

"Green on `main`, fix in the repo — not `continue-on-error`, not a
demotion to a warning": satisfied — `CI.yml` has no soft gates and no
matrix retirement (the only soft gate in the repo is `boj-build.yml`'s,
explained in this PR).

**One rename, checked for phantoms (CICD-SIGNAL-DISCIPLINE):** PR #45
dropped the matrix arch dimension, so the contexts lost their `, x64`
suffix. Rulesets require exactly one context (`scan / gitleaks`);
nothing required the old names → no phantom requirements were created.

**#47 (closed) verified AC-by-AC** against the merged state:
`get_statistics` ✔, `evaluate` `&&`/`||` ✔, Z3 unsat core ✔ (locally, Z3
4.13.3), `declare_const` decision ✔ (tests use
`declare`/`build_script`), `Pkg.test()` green on the matrix ✔. The one
caveat — the Z3 path never ran in CI — is fixed by this PR (#62).

## Changes in this PR

- `docs` — `ULTRAPLAN-ISSUE-43.adoc`: the plan + execution record
(841076c)
- `fix(ci)` — install Z3 on the ubuntu CI legs so solver-backed tests
run instead of skipping (cda05cb, closes #62)
- `fix(ci)` — `boj-build.yml`: `by-design:` rationale for the
`continue-on-error` (TOOLING-VERSION-INTEGRITY R4) + fix the mangled
trigger payload (ce3f3db, closes #59)
- `fix(docs)` — retire the stale `docs/make.jl` (points at `.md` files
deleted by the md→adoc migration; nothing runs Documenter) (8fbc840,
closes #60)
- `docs` — fill `{{PROJECT_UNIQUE_STRENGTH}}` (derived from the README,
not invented) and retire `REQUIRES_INITIALISATION.adoc` per its own
agent rule (a905071, closes #61)
- `chore(ci)` — adopt `.github/workflows/actions.lock` (estate canon
R2), generated from the merged tree (14 workflows, 31 refs, job-level
reusable refs included) and verified both directions against
`check-lock-sync.sh` semantics (fb1d6d1, closes #58)

Also closes #54 (a permission probe) and #55 (empty-bodied mis-create;
superseded by #56).

## PR #52 (deps) handled first

All 6 new pins verified resolvable upstream via `git ls-remote` / commit
lookups — including the annotated-tag peels (`github/codeql-action`
v4.38.2 → commit `2892aa5e…`; `smtp-notify-action` v0.5.0 →
`c1c9fa07…`). Merged as squash before this branch, so the lock matches
the merged tree. (Cosmetic leftover: the codeql lines' `# v3` comment
tags are stale — dependabot does not update comments.)

## What this PR does NOT do

- **#56 (mirror) and #57 (Pages)** stay open: both need a fix/retire
ruling (secrets/vars and publishing intent are owner-level). No mute was
applied to either red.
- **Umbrella #53 stays open** until #56/#57 are determined (its
AC2–AC4).
- Estate-side GATE-tier / derived-required-context rollout is
cross-cutting (standards #994 class); required contexts are derived by
the estate applier, never typed here. Could not be commented onto
`standards` #994 (same integration permission shape) — owner please
relay §1.3/§4.8 of the ultraplan.
- Spotted but out of scope: `src/abi/Types.idr` still carries scaffold
guidance text ("Replace {{TYPES}}…") — ABI/FFI-seam residue outside the
top-up ledger's token census; `docs/make.jl`-adjacent TEST-NEEDS.adoc
claims "0 E2E tests" though `test/e2e_test.jl` exists.

## Verification

- `check-lock-sync.sh` semantics (both directions): `OK: 14 workflows,
31 lock entries`
- Payload quoting of the boj trigger is now valid JSON: `{"repo": …,
"branch": …, "engine": "casket"}`
- Token census: no `{{…}}` substitution token remains in tracked content
(only the validator's `reject-if-contains` literals and the ABI
template's guidance text)
- CI matrix on this PR must be green **with Z3 installed** (that is
#62's acceptance criterion — the solver-gated tests now execute)

---------

Signed-off-by: Jonathan D.A. Jewell <6759885+hyperpolymath@users.noreply.github.com>
Co-authored-by: arena-agent <297053741+arena-agent@users.noreply.github.com>
Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
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.

1 participant