Skip to content

build(deps): bump the github-actions group with 11 updates - #363

Closed
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/github_actions/github-actions-5e41dfc29d
Closed

build(deps): bump the github-actions group with 11 updates#363
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/github_actions/github-actions-5e41dfc29d

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Jun 8, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

Bumps the github-actions group with 11 updates:

Package From To
actions/upload-artifact 4 7
actions/download-artifact 4 8
norrietaylor/spectacles/.github/workflows/distillery-sync.lock.yml 0.1.0 0.1.2
norrietaylor/spectacles 0.1.0 0.1.2
norrietaylor/spectacles/.github/workflows/sdd-execute-haiku.lock.yml 0.1.0 0.1.2
norrietaylor/spectacles/.github/workflows/sdd-execute-opus.lock.yml 0.1.0 0.1.2
norrietaylor/spectacles/.github/workflows/sdd-execute-sonnet.lock.yml 0.1.0 0.1.2
norrietaylor/spectacles/.github/workflows/sdd-review.lock.yml 0.1.0 0.1.2
norrietaylor/spectacles/.github/workflows/sdd-spec.lock.yml 0.1.0 0.1.2
norrietaylor/spectacles/.github/workflows/sdd-triage.lock.yml 0.1.0 0.1.2
norrietaylor/spectacles/.github/workflows/sdd-validate.lock.yml 0.1.0 0.1.2

Updates actions/upload-artifact from 4 to 7

Release notes

Sourced from actions/upload-artifact's releases.

v7.0.0

v7 What's new

Direct Uploads

Adds support for uploading single files directly (unzipped). Callers can set the new archive parameter to false to skip zipping the file during upload. Right now, we only support single files. The action will fail if the glob passed resolves to multiple files. The name parameter is also ignored with this setting. Instead, the name of the artifact will be the name of the uploaded file.

ESM

To support new versions of the @actions/* packages, we've upgraded the package to ESM.

What's Changed

New Contributors

Full Changelog: actions/upload-artifact@v6...v7.0.0

v6.0.0

v6 - What's new

[!IMPORTANT] actions/upload-artifact@v6 now runs on Node.js 24 (runs.using: node24) and requires a minimum Actions Runner version of 2.327.1. If you are using self-hosted runners, ensure they are updated before upgrading.

Node.js 24

This release updates the runtime to Node.js 24. v5 had preliminary support for Node.js 24, however this action was by default still running on Node.js 20. Now this action by default will run on Node.js 24.

What's Changed

Full Changelog: actions/upload-artifact@v5.0.0...v6.0.0

v5.0.0

What's Changed

BREAKING CHANGE: this update supports Node v24.x. This is not a breaking change per-se but we're treating it as such.

... (truncated)

Commits
  • 043fb46 Merge pull request #797 from actions/yacaovsnc/update-dependency
  • 634250c Include changes in typespec/ts-http-runtime 0.3.5
  • e454baa Readme: bump all the example versions to v7 (#796)
  • 74fad66 Update the readme with direct upload details (#795)
  • bbbca2d Support direct file uploads (#764)
  • 589182c Upgrade the module to ESM and bump dependencies (#762)
  • 47309c9 Merge pull request #754 from actions/Link-/add-proxy-integration-tests
  • 02a8460 Add proxy integration test
  • b7c566a Merge pull request #745 from actions/upload-artifact-v6-release
  • e516bc8 docs: correct description of Node.js 24 support in README
  • Additional commits viewable in compare view

Updates actions/download-artifact from 4 to 8

Release notes

Sourced from actions/download-artifact's releases.

v8.0.0

v8 - What's new

[!IMPORTANT] actions/download-artifact@v8 has been migrated to an ESM module. This should be transparent to the caller but forks might need to make significant changes.

[!IMPORTANT] Hash mismatches will now error by default. Users can override this behavior with a setting change (see below).

Direct downloads

To support direct uploads in actions/upload-artifact, the action will no longer attempt to unzip all downloaded files. Instead, the action checks the Content-Type header ahead of unzipping and skips non-zipped files. Callers wishing to download a zipped file as-is can also set the new skip-decompress parameter to true.

Enforced checks (breaking)

A previous release introduced digest checks on the download. If a download hash didn't match the expected hash from the server, the action would log a warning. Callers can now configure the behavior on mismatch with the digest-mismatch parameter. To be secure by default, we are now defaulting the behavior to error which will fail the workflow run.

ESM

To support new versions of the @actions/* packages, we've upgraded the package to ESM.

What's Changed

Full Changelog: actions/download-artifact@v7...v8.0.0

v7.0.0

v7 - What's new

[!IMPORTANT] actions/download-artifact@v7 now runs on Node.js 24 (runs.using: node24) and requires a minimum Actions Runner version of 2.327.1. If you are using self-hosted runners, ensure they are updated before upgrading.

Node.js 24

This release updates the runtime to Node.js 24. v6 had preliminary support for Node 24, however this action was by default still running on Node.js 20. Now this action by default will run on Node.js 24.

What's Changed

New Contributors

Full Changelog: actions/download-artifact@v6.0.0...v7.0.0

v6.0.0

... (truncated)

Commits
  • 3e5f45b Add regression tests for CJK characters (#471)
  • e6d03f6 Add a regression test for artifact name + content-type mismatches (#472)
  • 70fc10c Merge pull request #461 from actions/danwkennedy/digest-mismatch-behavior
  • f258da9 Add change docs
  • ccc058e Fix linting issues
  • bd7976b Add a setting to specify what to do on hash mismatch and default it to error
  • ac21fcf Merge pull request #460 from actions/danwkennedy/download-no-unzip
  • 15999bf Add note about package bumps
  • 974686e Bump the version to v8 and add release notes
  • fbe48b1 Update test names to make it clearer what they do
  • Additional commits viewable in compare view

Updates norrietaylor/spectacles/.github/workflows/distillery-sync.lock.yml from 0.1.0 to 0.1.2

Release notes

Sourced from norrietaylor/spectacles/.github/workflows/distillery-sync.lock.yml's releases.

v0.1.2 — Spikes, observability, and lifecycle status

Adds three planning- and operability-grade capabilities on top of the v0.1.1 reliability work: a spike primitive for unproven assumptions, OTLP span export from every agent, and spec/architecture document lifecycle status. Plus a deterministic cycle-detect backstop and a round of cascade hardening.

Planning hardening

  • #229 (Track B) — spike primitive + assumption ledger. sdd-triage phase A now builds an assumption ledger in the architecture record, one row per load-bearing assumption. A load-bearing assumption that can't be settled from the working tree or precedent is marked needs-spike and materialized as a kind:spike sub-issue. sdd-spike-actuator posts /execute, sdd-execute writes a docs/spikes/<date>-<slug>.md finding, and sdd-validate resolves it (proved → sdd:spike-resolved; disproved/partial → park at needs-human). sdd-spike-reentry re-enters phase B once the wave drains. See docs/sdd/spikes.md.
  • #229 (Track C) — latent-edge pass + cycle-detect backstop. Phase B adds the implied dependency edge when a task's proof artifacts consume a sibling's output, even with no blocked by line. A deterministic sdd-cycle-detect composite job runs after phase-C materialization and parks needs-human on a real cycle (or an unresolvable blocked by) the LLM missed. The backstop also runs on partial phase-C failure.

Observability

  • #234 — OTLP agent spans (ADR-0020). Every engine:-bearing agent exports spans (token usage, duration, outcomes) to the optional GH_AW_OTEL_ENDPOINT collector. The endpoint is redacted from artifacts before upload, including on failure paths.

Document lifecycle

  • ADR-0021 — spec/arch status advance. Spec and architecture documents carry lifecycle frontmatter that advances through the pipeline. See spec frontmatter and doc states.

Cascade and reliability fixes

  • sdd-dispatch closes a Unit deterministically once all its tasks close.
  • sdd-execute: stable check_suite concurrency key, scoped to actionable suites.
  • sdd-monitor: minted App token scoped to least-privilege permissions.
  • sdd-dispatch: removeLabel 404 tolerance scoped to the dispatch job.
  • sdd-spec: post-merge /revise (situation 8) scoped to the spec doc.
  • sdd-doc-status: dropped [skip ci] so distillery-sync re-mirrors.

Tooling

  • gh-aw pin bumped v0.74.3 → v0.77.5; all locks recompiled.

Full diff: norrietaylor/spectacles@v0.1.1...v0.1.2

v0.1.1 — SDD pipeline reliability

SDD pipeline reliability and recovery. Hardens the dispatch → execute → review → merge cascade against the strand/no-op/conflict failure modes surfaced by the E2E tracker, plus repo-grounded planning and CI self-healing.

SDD pipeline fixes

  • #193 sdd-dispatch fails hard when arming sdd:dispatched (no more swallowed label-arm failure stranding the cascade).
  • #202 sdd-review: an actionable COMMENTED review on an sdd/ PR now triggers revise instead of dead-ending.
  • #203 sdd-execute: a failed required check on an open sdd/ PR triggers revise (bounded, then needs-human); ignores stale check-suite SHAs.
  • #201 sdd-monitor recovers tasks stranded by pre-agent execute failures (cancelled/activation) and re-dispatches them; compute now admits non-in-flight sdd:in-progress tasks.
  • #205 sdd-execute: static.crates.io added to the firewall allow-list and a pre-PR CI gate (escalate rather than ship unverified).
  • #204 sdd-execute: terminal-outcome contract — a run must yield a non-empty PR or an explicit already-satisfied no-op; empty-diff PRs are auto-closed/escalated.
  • #207 sdd-execute: sibling sdd/ PRs behind base are auto-refreshed on merge; textual conflicts route to revise before needs-human.
  • #200 sdd-dispatch claims a task as sdd:in-progress at dispatch time (removing sdd:ready), making in-flight tasks distinguishable; sdd-dispatch added as a lifecycle co-writer.
  • #216 sdd-spec/sdd-triage require a Serena+Distillery repo-grounding baseline before task creation — no tasks for already-implemented requirements.

Tooling / CI

  • #215 drifted workflow locks are auto-recompiled on main via a bypass-actor App.
  • #214 Playwright browser MCP wired into sdd-execute agents.
  • #199 distillery-sync reports honestly on a gh_sync client timeout.
  • #198 agent PRs emit conventional-commit subjects.
  • #195 distillery-sync wrapper granted discussions/pull-requests write.

Full diff: norrietaylor/spectacles@v0.1.0...v0.1.1

Commits
  • ed4f15d Merge pull request #245 from norrietaylor/docs/v0.1.2-housekeeping
  • 4771198 docs: correct agent count and spike labels for v0.1.2
  • a8c1472 Merge pull request #244 from norrietaylor/feat/229c-mkdocs-flows
  • 5b7ae3e docs(sdd): document the cycle-detect backstop and spike wave (Track C, #229)
  • cce8622 build: recompile locks after fragment merge [skip ci]
  • f55750c Merge pull request #242 from norrietaylor/feat/229b-spike-primitive
  • 1d60cd9 docs(spike): address CodeRabbit on #242 (3 findings)
  • 5a40cff feat(spike): assumption ledger + spike primitive (Track B, #229)
  • 08c35c5 build: recompile locks after fragment merge [skip ci]
  • d96c773 Merge pull request #239 from norrietaylor/feat/229a-latent-cycle
  • Additional commits viewable in compare view

Updates norrietaylor/spectacles from 0.1.0 to 0.1.2

Release notes

Sourced from norrietaylor/spectacles's releases.

v0.1.2 — Spikes, observability, and lifecycle status

Adds three planning- and operability-grade capabilities on top of the v0.1.1 reliability work: a spike primitive for unproven assumptions, OTLP span export from every agent, and spec/architecture document lifecycle status. Plus a deterministic cycle-detect backstop and a round of cascade hardening.

Planning hardening

  • #229 (Track B) — spike primitive + assumption ledger. sdd-triage phase A now builds an assumption ledger in the architecture record, one row per load-bearing assumption. A load-bearing assumption that can't be settled from the working tree or precedent is marked needs-spike and materialized as a kind:spike sub-issue. sdd-spike-actuator posts /execute, sdd-execute writes a docs/spikes/<date>-<slug>.md finding, and sdd-validate resolves it (proved → sdd:spike-resolved; disproved/partial → park at needs-human). sdd-spike-reentry re-enters phase B once the wave drains. See docs/sdd/spikes.md.
  • #229 (Track C) — latent-edge pass + cycle-detect backstop. Phase B adds the implied dependency edge when a task's proof artifacts consume a sibling's output, even with no blocked by line. A deterministic sdd-cycle-detect composite job runs after phase-C materialization and parks needs-human on a real cycle (or an unresolvable blocked by) the LLM missed. The backstop also runs on partial phase-C failure.

Observability

  • #234 — OTLP agent spans (ADR-0020). Every engine:-bearing agent exports spans (token usage, duration, outcomes) to the optional GH_AW_OTEL_ENDPOINT collector. The endpoint is redacted from artifacts before upload, including on failure paths.

Document lifecycle

  • ADR-0021 — spec/arch status advance. Spec and architecture documents carry lifecycle frontmatter that advances through the pipeline. See spec frontmatter and doc states.

Cascade and reliability fixes

  • sdd-dispatch closes a Unit deterministically once all its tasks close.
  • sdd-execute: stable check_suite concurrency key, scoped to actionable suites.
  • sdd-monitor: minted App token scoped to least-privilege permissions.
  • sdd-dispatch: removeLabel 404 tolerance scoped to the dispatch job.
  • sdd-spec: post-merge /revise (situation 8) scoped to the spec doc.
  • sdd-doc-status: dropped [skip ci] so distillery-sync re-mirrors.

Tooling

  • gh-aw pin bumped v0.74.3 → v0.77.5; all locks recompiled.

Full diff: norrietaylor/spectacles@v0.1.1...v0.1.2

v0.1.1 — SDD pipeline reliability

SDD pipeline reliability and recovery. Hardens the dispatch → execute → review → merge cascade against the strand/no-op/conflict failure modes surfaced by the E2E tracker, plus repo-grounded planning and CI self-healing.

SDD pipeline fixes

  • #193 sdd-dispatch fails hard when arming sdd:dispatched (no more swallowed label-arm failure stranding the cascade).
  • #202 sdd-review: an actionable COMMENTED review on an sdd/ PR now triggers revise instead of dead-ending.
  • #203 sdd-execute: a failed required check on an open sdd/ PR triggers revise (bounded, then needs-human); ignores stale check-suite SHAs.
  • #201 sdd-monitor recovers tasks stranded by pre-agent execute failures (cancelled/activation) and re-dispatches them; compute now admits non-in-flight sdd:in-progress tasks.
  • #205 sdd-execute: static.crates.io added to the firewall allow-list and a pre-PR CI gate (escalate rather than ship unverified).
  • #204 sdd-execute: terminal-outcome contract — a run must yield a non-empty PR or an explicit already-satisfied no-op; empty-diff PRs are auto-closed/escalated.
  • #207 sdd-execute: sibling sdd/ PRs behind base are auto-refreshed on merge; textual conflicts route to revise before needs-human.
  • #200 sdd-dispatch claims a task as sdd:in-progress at dispatch time (removing sdd:ready), making in-flight tasks distinguishable; sdd-dispatch added as a lifecycle co-writer.
  • #216 sdd-spec/sdd-triage require a Serena+Distillery repo-grounding baseline before task creation — no tasks for already-implemented requirements.

Tooling / CI

  • #215 drifted workflow locks are auto-recompiled on main via a bypass-actor App.
  • #214 Playwright browser MCP wired into sdd-execute agents.
  • #199 distillery-sync reports honestly on a gh_sync client timeout.
  • #198 agent PRs emit conventional-commit subjects.
  • #195 distillery-sync wrapper granted discussions/pull-requests write.

Full diff: norrietaylor/spectacles@v0.1.0...v0.1.1

Commits
  • ed4f15d Merge pull request #245 from norrietaylor/docs/v0.1.2-housekeeping
  • 4771198 docs: correct agent count and spike labels for v0.1.2
  • a8c1472 Merge pull request #244 from norrietaylor/feat/229c-mkdocs-flows
  • 5b7ae3e docs(sdd): document the cycle-detect backstop and spike wave (Track C, #229)
  • cce8622 build: recompile locks after fragment merge [skip ci]
  • f55750c Merge pull request #242 from norrietaylor/feat/229b-spike-primitive
  • 1d60cd9 docs(spike): address CodeRabbit on #242 (3 findings)
  • 5a40cff feat(spike): assumption ledger + spike primitive (Track B, #229)
  • 08c35c5 build: recompile locks after fragment merge [skip ci]
  • d96c773 Merge pull request #239 from norrietaylor/feat/229a-latent-cycle
  • Additional commits viewable in compare view

Updates norrietaylor/spectacles/.github/workflows/sdd-execute-haiku.lock.yml from 0.1.0 to 0.1.2

Release notes

Sourced from norrietaylor/spectacles/.github/workflows/sdd-execute-haiku.lock.yml's releases.

v0.1.2 — Spikes, observability, and lifecycle status

Adds three planning- and operability-grade capabilities on top of the v0.1.1 reliability work: a spike primitive for unproven assumptions, OTLP span export from every agent, and spec/architecture document lifecycle status. Plus a deterministic cycle-detect backstop and a round of cascade hardening.

Planning hardening

  • #229 (Track B) — spike primitive + assumption ledger. sdd-triage phase A now builds an assumption ledger in the architecture record, one row per load-bearing assumption. A load-bearing assumption that can't be settled from the working tree or precedent is marked needs-spike and materialized as a kind:spike sub-issue. sdd-spike-actuator posts /execute, sdd-execute writes a docs/spikes/<date>-<slug>.md finding, and sdd-validate resolves it (proved → sdd:spike-resolved; disproved/partial → park at needs-human). sdd-spike-reentry re-enters phase B once the wave drains. See docs/sdd/spikes.md.
  • #229 (Track C) — latent-edge pass + cycle-detect backstop. Phase B adds the implied dependency edge when a task's proof artifacts consume a sibling's output, even with no blocked by line. A deterministic sdd-cycle-detect composite job runs after phase-C materialization and parks needs-human on a real cycle (or an unresolvable blocked by) the LLM missed. The backstop also runs on partial phase-C failure.

Observability

  • #234 — OTLP agent spans (ADR-0020). Every engine:-bearing agent exports spans (token usage, duration, outcomes) to the optional GH_AW_OTEL_ENDPOINT collector. The endpoint is redacted from artifacts before upload, including on failure paths.

Document lifecycle

  • ADR-0021 — spec/arch status advance. Spec and architecture documents carry lifecycle frontmatter that advances through the pipeline. See spec frontmatter and doc states.

Cascade and reliability fixes

  • sdd-dispatch closes a Unit deterministically once all its tasks close.
  • sdd-execute: stable check_suite concurrency key, scoped to actionable suites.
  • sdd-monitor: minted App token scoped to least-privilege permissions.
  • sdd-dispatch: removeLabel 404 tolerance scoped to the dispatch job.
  • sdd-spec: post-merge /revise (situation 8) scoped to the spec doc.
  • sdd-doc-status: dropped [skip ci] so distillery-sync re-mirrors.

Tooling

  • gh-aw pin bumped v0.74.3 → v0.77.5; all locks recompiled.

Full diff: norrietaylor/spectacles@v0.1.1...v0.1.2

v0.1.1 — SDD pipeline reliability

SDD pipeline reliability and recovery. Hardens the dispatch → execute → review → merge cascade against the strand/no-op/conflict failure modes surfaced by the E2E tracker, plus repo-grounded planning and CI self-healing.

SDD pipeline fixes

  • #193 sdd-dispatch fails hard when arming sdd:dispatched (no more swallowed label-arm failure stranding the cascade).
  • #202 sdd-review: an actionable COMMENTED review on an sdd/ PR now triggers revise instead of dead-ending.
  • #203 sdd-execute: a failed required check on an open sdd/ PR triggers revise (bounded, then needs-human); ignores stale check-suite SHAs.
  • #201 sdd-monitor recovers tasks stranded by pre-agent execute failures (cancelled/activation) and re-dispatches them; compute now admits non-in-flight sdd:in-progress tasks.
  • #205 sdd-execute: static.crates.io added to the firewall allow-list and a pre-PR CI gate (escalate rather than ship unverified).
  • #204 sdd-execute: terminal-outcome contract — a run must yield a non-empty PR or an explicit already-satisfied no-op; empty-diff PRs are auto-closed/escalated.
  • #207 sdd-execute: sibling sdd/ PRs behind base are auto-refreshed on merge; textual conflicts route to revise before needs-human.
  • #200 sdd-dispatch claims a task as sdd:in-progress at dispatch time (removing sdd:ready), making in-flight tasks distinguishable; sdd-dispatch added as a lifecycle co-writer.
  • #216 sdd-spec/sdd-triage require a Serena+Distillery repo-grounding baseline before task creation — no tasks for already-implemented requirements.

Tooling / CI

  • #215 drifted workflow locks are auto-recompiled on main via a bypass-actor App.
  • #214 Playwright browser MCP wired into sdd-execute agents.
  • #199 distillery-sync reports honestly on a gh_sync client timeout.
  • #198 agent PRs emit conventional-commit subjects.
  • #195 distillery-sync wrapper granted discussions/pull-requests write.

Full diff: norrietaylor/spectacles@v0.1.0...v0.1.1

Commits
  • ed4f15d Merge pull request #245 from norrietaylor/docs/v0.1.2-housekeeping
  • 4771198 docs: correct agent count and spike labels for v0.1.2
  • a8c1472 Merge pull request #244 from norrietaylor/feat/229c-mkdocs-flows
  • 5b7ae3e docs(sdd): document the cycle-detect backstop and spike wave (Track C, #229)
  • cce8622 build: recompile locks after fragment merge [skip ci]
  • f55750c Merge pull request #242 from norrietaylor/feat/229b-spike-primitive
  • 1d60cd9 docs(spike): address CodeRabbit on #242 (3 findings)
  • 5a40cff feat(spike): assumption ledger + spike primitive (Track B, #229)
  • 08c35c5 build: recompile locks after fragment merge [skip ci]
  • d96c773 Merge pull request #239 from norrietaylor/feat/229a-latent-cycle
  • Additional commits viewable in compare view

Updates norrietaylor/spectacles/.github/workflows/sdd-execute-opus.lock.yml from 0.1.0 to 0.1.2

Release notes

Sourced from norrietaylor/spectacles/.github/workflows/sdd-execute-opus.lock.yml's releases.

v0.1.2 — Spikes, observability, and lifecycle status

Adds three planning- and operability-grade capabilities on top of the v0.1.1 reliability work: a spike primitive for unproven assumptions, OTLP span export from every agent, and spec/architecture document lifecycle status. Plus a deterministic cycle-detect backstop and a round of cascade hardening.

Planning hardening

  • #229 (Track B) — spike primitive + assumption ledger. sdd-triage phase A now builds an assumption ledger in the architecture record, one row per load-bearing assumption. A load-bearing assumption that can't be settled from the working tree or precedent is marked needs-spike and materialized as a kind:spike sub-issue. sdd-spike-actuator posts /execute, sdd-execute writes a docs/spikes/<date>-<slug>.md finding, and sdd-validate resolves it (proved → sdd:spike-resolved; disproved/partial → park at needs-human). sdd-spike-reentry re-enters phase B once the wave drains. See docs/sdd/spikes.md.
  • #229 (Track C) — latent-edge pass + cycle-detect backstop. Phase B adds the implied dependency edge when a task's proof artifacts consume a sibling's output, even with no blocked by line. A deterministic sdd-cycle-detect composite job runs after phase-C materialization and parks needs-human on a real cycle (or an unresolvable blocked by) the LLM missed. The backstop also runs on partial phase-C failure.

Observability

  • #234 — OTLP agent spans (ADR-0020). Every engine:-bearing agent exports spans (token usage, duration, outcomes) to the optional GH_AW_OTEL_ENDPOINT collector. The endpoint is redacted from artifacts before upload, including on failure paths.

Document lifecycle

  • ADR-0021 — spec/arch status advance. Spec and architecture documents carry lifecycle frontmatter that advances through the pipeline. See spec frontmatter and doc states.

Cascade and reliability fixes

  • sdd-dispatch closes a Unit deterministically once all its tasks close.
  • sdd-execute: stable check_suite concurrency key, scoped to actionable suites.
  • sdd-monitor: minted App token scoped to least-privilege permissions.
  • sdd-dispatch: removeLabel 404 tolerance scoped to the dispatch job.
  • sdd-spec: post-merge /revise (situation 8) scoped to the spec doc.
  • sdd-doc-status: dropped [skip ci] so distillery-sync re-mirrors.

Tooling

  • gh-aw pin bumped v0.74.3 → v0.77.5; all locks recompiled.

Full diff: norrietaylor/spectacles@v0.1.1...v0.1.2

v0.1.1 — SDD pipeline reliability

SDD pipeline reliability and recovery. Hardens the dispatch → execute → review → merge cascade against the strand/no-op/conflict failure modes surfaced by the E2E tracker, plus repo-grounded planning and CI self-healing.

SDD pipeline fixes

  • #193 sdd-dispatch fails hard when arming sdd:dispatched (no more swallowed label-arm failure stranding the cascade).
  • #202 sdd-review: an actionable COMMENTED review on an sdd/ PR now triggers revise instead of dead-ending.
  • #203 sdd-execute: a failed required check on an open sdd/ PR triggers revise (bounded, then needs-human); ignores stale check-suite SHAs.
  • #201 sdd-monitor recovers tasks stranded by pre-agent execute failures (cancelled/activation) and re-dispatches them; compute now admits non-in-flight sdd:in-progress tasks.
  • #205 sdd-execute: static.crates.io added to the firewall allow-list and a pre-PR CI gate (escalate rather than ship unverified).
  • #204 sdd-execute: terminal-outcome contract — a run must yield a non-empty PR or an explicit already-satisfied no-op; empty-diff PRs are auto-closed/escalated.
  • #207 sdd-execute: sibling sdd/ PRs behind base are auto-refreshed on merge; textual conflicts route to revise before needs-human.
  • #200 sdd-dispatch claims a task as sdd:in-progress at dispatch time (removing sdd:ready), making in-flight tasks distinguishable; sdd-dispatch added as a lifecycle co-writer.
  • #216 sdd-spec/sdd-triage require a Serena+Distillery repo-grounding baseline before task creation — no tasks for already-implemented requirements.

Tooling / CI

  • #215 drifted workflow locks are auto-recompiled on main via a bypass-actor App.
  • #214 Playwright browser MCP wired into sdd-execute agents.
  • #199 distillery-sync reports honestly on a gh_sync client timeout.
  • #198 agent PRs emit conventional-commit subjects.
  • #195 distillery-sync wrapper granted discussions/pull-requests write.

Full diff: norrietaylor/spectacles@v0.1.0...v0.1.1

Commits
  • ed4f15d Merge pull request #245 from norrietaylor/docs/v0.1.2-housekeeping
  • 4771198 docs: correct agent count and spike labels for v0.1.2
  • a8c1472 Merge pull request #244 from norrietaylor/feat/229c-mkdocs-flows
  • 5b7ae3e docs(sdd): document the cycle-detect backstop and spike wave (Track C, #229)
  • cce8622 build: recompile locks after fragment merge [skip ci]
  • f55750c Merge pull request #242 from norrietaylor/feat/229b-spike-primitive
  • 1d60cd9 docs(spike): address CodeRabbit on #242 (3 findings)
  • 5a40cff feat(spike): assumption ledger + spike primitive (Track B, #229)
  • 08c35c5 build: recompile locks after fragment merge [skip ci]
  • d96c773 Merge pull request #239 from norrietaylor/feat/229a-latent-cycle
  • Additional commits viewable in compare view

Updates norrietaylor/spectacles/.github/workflows/sdd-execute-sonnet.lock.yml from 0.1.0 to 0.1.2

Release notes

Sourced from norrietaylor/spectacles/.github/workflows/sdd-execute-sonnet.lock.yml's releases.

v0.1.2 — Spikes, observability, and lifecycle status

Adds three planning- and operability-grade capabilities on top of the v0.1.1 reliability work: a spike primitive for unproven assumptions, OTLP span export from every agent, and spec/architecture document lifecycle status. Plus a deterministic cycle-detect backstop and a round of cascade hardening.

Planning hardening

  • #229 (Track B) — spike primitive + assumption ledger. sdd-triage phase A now builds an assumption ledger in the architecture record, one row per load-bearing assumption. A load-bearing assumption that can't be settled from the working tree or precedent is marked needs-spike and materialized as a kind:spike sub-issue. sdd-spike-actuator posts /execute, sdd-execute writes a docs/spikes/<date>-<slug>.md finding, and sdd-validate resolves it (proved → sdd:spike-resolved; disproved/partial → park at needs-human). sdd-spike-reentry re-enters phase B once the wave drains. See docs/sdd/spikes.md.
  • #229 (Track C) — latent-edge pass + cycle-detect backstop. Phase B adds the implied dependency edge when a task's proof artifacts consume a sibling's output, even with no blocked by line. A deterministic sdd-cycle-detect composite job runs after phase-C materialization and parks needs-human on a real cycle (or an unresolvable blocked by) the LLM missed. The backstop also runs on partial phase-C failure.

Observability

  • #234 — OTLP agent spans (ADR-0020). Every engine:-bearing agent exports spans (token usage, duration, outcomes) to the optional GH_AW_OTEL_ENDPOINT collector. The endpoint is redacted from artifacts before upload, including on failure paths.

Document lifecycle

  • ADR-0021 — spec/arch status advance. Spec and architecture documents carry lifecycle frontmatter that advances through the pipeline. See spec frontmatter and doc states.

Cascade and reliability fixes

  • sdd-dispatch closes a Unit deterministically once all its tasks close.
  • sdd-execute: stable check_suite concurrency key, scoped to actionable suites.
  • sdd-monitor: minted App token scoped to least-privilege permissions.
  • sdd-dispatch: removeLabel 404 tolerance scoped to the dispatch job.
  • sdd-spec: post-merge /revise (situation 8) scoped to the spec doc.
  • sdd-doc-status: dropped [skip ci] so distillery-sync re-mirrors.

Tooling

  • gh-aw pin bumped v0.74.3 → v0.77.5; all locks recompiled.

Full diff: norrietaylor/spectacles@v0.1.1...v0.1.2

v0.1.1 — SDD pipeline reliability

SDD pipeline reliability and recovery. Hardens the dispatch → execute → review → merge cascade against the strand/no-op/conflict failure modes surfaced by the E2E tracker, plus repo-grounded planning and CI self-healing.

SDD pipeline fixes

  • #193 sdd-dispatch fails hard when arming sdd:dispatched (no more swallowed label-arm failure stranding the cascade).
  • #202 sdd-review: an actionable COMMENTED review on an sdd/ PR now triggers revise instead of dead-ending.
  • #203 sdd-execute: a failed required check on an open sdd/ PR triggers revise (bounded, then needs-human); ignores stale check-suite SHAs.
  • #201 sdd-monitor recovers tasks stranded by pre-agent execute failures (cancelled/activation) and re-dispatches them; compute now admits non-in-flight sdd:in-progress tasks.
  • #205 sdd-execute: static.crates.io added to the firewall allow-list and a pre-PR CI gate (escalate rather than ship unverified).
  • #204 sdd-execute: terminal-outcome contract — a run must yield a non-empty PR or an explicit already-satisfied no-op; empty-diff PRs are auto-closed/escalated.
  • #207 sdd-execute: sibling sdd/ PRs behind base are auto-refreshed on merge; textual conflicts route to revise before needs-human.
  • #200 sdd-dispatch claims a task as sdd:in-progress at dispatch time (removing sdd:ready), making in-flight tasks distinguishable; sdd-dispatch added as a lifecycle co-writer.
  • #216 sdd-spec/sdd-triage require a Serena+Distillery repo-grounding baseline before task creation — no tasks for already-implemented requirements.

Tooling / CI

  • #215 drifted workflow locks are auto-recompiled on main via a bypass-actor App.
  • #214 Playwright browser MCP wired into sdd-execute agents.
  • #199 distillery-sync reports honestly on a gh_sync client timeout.
  • #198 agent PRs emit conventional-commit subjects.
  • #195 distillery-sync wrapper granted discussions/pull-requests write.

Full diff: norrietaylor/spectacles@v0.1.0...v0.1.1

Commits

@dependabot
build(deps): bump the github-actions group with 11 updates
b288455 
Bumps the github-actions group with 11 updates:

| Package | From | To |
| --- | --- | --- |
| [actions/upload-artifact](https://github.com/actions/upload-artifact) | `4` | `7` |
| [actions/download-artifact](https://github.com/actions/download-artifact) | `4` | `8` |
| [norrietaylor/spectacles/.github/workflows/distillery-sync.lock.yml](https://github.com/norrietaylor/spectacles) | `0.1.0` | `0.1.2` |
| [norrietaylor/spectacles](https://github.com/norrietaylor/spectacles) | `0.1.0` | `0.1.2` |
| [norrietaylor/spectacles/.github/workflows/sdd-execute-haiku.lock.yml](https://github.com/norrietaylor/spectacles) | `0.1.0` | `0.1.2` |
| [norrietaylor/spectacles/.github/workflows/sdd-execute-opus.lock.yml](https://github.com/norrietaylor/spectacles) | `0.1.0` | `0.1.2` |
| [norrietaylor/spectacles/.github/workflows/sdd-execute-sonnet.lock.yml](https://github.com/norrietaylor/spectacles) | `0.1.0` | `0.1.2` |
| [norrietaylor/spectacles/.github/workflows/sdd-review.lock.yml](https://github.com/norrietaylor/spectacles) | `0.1.0` | `0.1.2` |
| [norrietaylor/spectacles/.github/workflows/sdd-spec.lock.yml](https://github.com/norrietaylor/spectacles) | `0.1.0` | `0.1.2` |
| [norrietaylor/spectacles/.github/workflows/sdd-triage.lock.yml](https://github.com/norrietaylor/spectacles) | `0.1.0` | `0.1.2` |
| [norrietaylor/spectacles/.github/workflows/sdd-validate.lock.yml](https://github.com/norrietaylor/spectacles) | `0.1.0` | `0.1.2` |


Updates `actions/upload-artifact` from 4 to 7
- [Release notes](https://github.com/actions/upload-artifact/releases)
- [Commits](actions/upload-artifact@v4...v7)

Updates `actions/download-artifact` from 4 to 8
- [Release notes](https://github.com/actions/download-artifact/releases)
- [Commits](actions/download-artifact@v4...v8)

Updates `norrietaylor/spectacles/.github/workflows/distillery-sync.lock.yml` from 0.1.0 to 0.1.2
- [Release notes](https://github.com/norrietaylor/spectacles/releases)
- [Commits](norrietaylor/spectacles@v0.1.0...v0.1.2)

Updates `norrietaylor/spectacles` from 0.1.0 to 0.1.2
- [Release notes](https://github.com/norrietaylor/spectacles/releases)
- [Commits](norrietaylor/spectacles@v0.1.0...v0.1.2)

Updates `norrietaylor/spectacles/.github/workflows/sdd-execute-haiku.lock.yml` from 0.1.0 to 0.1.2
- [Release notes](https://github.com/norrietaylor/spectacles/releases)
- [Commits](norrietaylor/spectacles@v0.1.0...v0.1.2)

Updates `norrietaylor/spectacles/.github/workflows/sdd-execute-opus.lock.yml` from 0.1.0 to 0.1.2
- [Release notes](https://github.com/norrietaylor/spectacles/releases)
- [Commits](norrietaylor/spectacles@v0.1.0...v0.1.2)

Updates `norrietaylor/spectacles/.github/workflows/sdd-execute-sonnet.lock.yml` from 0.1.0 to 0.1.2
- [Release notes](https://github.com/norrietaylor/spectacles/releases)
- [Commits](norrietaylor/spectacles@v0.1.0...v0.1.2)

Updates `norrietaylor/spectacles/.github/workflows/sdd-review.lock.yml` from 0.1.0 to 0.1.2
- [Release notes](https://github.com/norrietaylor/spectacles/releases)
- [Commits](norrietaylor/spectacles@v0.1.0...v0.1.2)

Updates `norrietaylor/spectacles/.github/workflows/sdd-spec.lock.yml` from 0.1.0 to 0.1.2
- [Release notes](https://github.com/norrietaylor/spectacles/releases)
- [Commits](norrietaylor/spectacles@v0.1.0...v0.1.2)

Updates `norrietaylor/spectacles/.github/workflows/sdd-triage.lock.yml` from 0.1.0 to 0.1.2
- [Release notes](https://github.com/norrietaylor/spectacles/releases)
- [Commits](norrietaylor/spectacles@v0.1.0...v0.1.2)

Updates `norrietaylor/spectacles/.github/workflows/sdd-validate.lock.yml` from 0.1.0 to 0.1.2
- [Release notes](https://github.com/norrietaylor/spectacles/releases)
- [Commits](norrietaylor/spectacles@v0.1.0...v0.1.2)

---
updated-dependencies:
- dependency-name: actions/upload-artifact
  dependency-version: '7'
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: github-actions
- dependency-name: actions/download-artifact
  dependency-version: '8'
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: github-actions
- dependency-name: norrietaylor/spectacles/.github/workflows/distillery-sync.lock.yml
  dependency-version: 0.1.2
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: github-actions
- dependency-name: norrietaylor/spectacles
  dependency-version: 0.1.2
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: github-actions
- dependency-name: norrietaylor/spectacles/.github/workflows/sdd-execute-haiku.lock.yml
  dependency-version: 0.1.2
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: github-actions
- dependency-name: norrietaylor/spectacles/.github/workflows/sdd-execute-opus.lock.yml
  dependency-version: 0.1.2
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: github-actions
- dependency-name: norrietaylor/spectacles/.github/workflows/sdd-execute-sonnet.lock.yml
  dependency-version: 0.1.2
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: github-actions
- dependency-name: norrietaylor/spectacles/.github/workflows/sdd-review.lock.yml
  dependency-version: 0.1.2
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: github-actions
- dependency-name: norrietaylor/spectacles/.github/workflows/sdd-spec.lock.yml
  dependency-version: 0.1.2
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: github-actions
- dependency-name: norrietaylor/spectacles/.github/workflows/sdd-triage.lock.yml
  dependency-version: 0.1.2
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: github-actions
- dependency-name: norrietaylor/spectacles/.github/workflows/sdd-validate.lock.yml
  dependency-version: 0.1.2
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: github-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 Jun 8, 2026
@coderabbitai

coderabbitai Bot commented Jun 8, 2026 •
edited
Loading

Copy link
Copy Markdown

Review Change Stack

📝 Walkthrough

Walkthrough

This PR updates pinned versions across GitHub Actions workflows. The CI macOS workflow is updated to use newer artifact management action versions (upload v7, download v8). Across 11 Spectacles-hosted workflow wrappers, reusable actions and workflows are bumped from v0.1.0 to v0.1.2, including dispatch routing, execution tiers, validation, review, spec, triage, and monitoring components.

Changes

GitHub Actions and Spectacles Workflow Version Updates

Layer / File(s) Summary
CI macOS artifact action versions
.github/workflows/ci-macos.yml		 Kernel artifact uploads switch from actions/upload-artifact@v4 to @v7, and kernel downloads in both E2E jobs switch from actions/download-artifact@v4 to @v8. Guest boot and autospawn boot log uploads updated to actions/upload-artifact@v7.
Spectacles dispatch and execution tier workflows
.github/workflows/distillery-sync.yml, .github/workflows/sdd-dispatch.yml, .github/workflows/sdd-execute-{haiku,opus,sonnet}.yml		 Distillery-sync, dispatch routing, and execute-tier workflows bump reusable action/workflow versions from @v0.1.0 to @v0.1.2: sdd-route-dispatch, sdd-dispatch-compute, sdd-route-execute, tier-specific lock files, and sdd-auto-merge across haiku, opus, and sonnet tiers.
Spectacles validation, review, and spec workflows
.github/workflows/sdd-validate.yml, .github/workflows/sdd-review.yml, .github/workflows/sdd-spec.yml		 Validation and review wrappers update sdd-route-validate, sdd-route-review, lock files, and advisory-thread resolver to @v0.1.2. Spec workflow updates sdd-route-spec, sdd-fastpath-approve, sdd-spec lock, and sdd-spec-failure-handoff to @v0.1.2.
Spectacles triage and monitor workflows
.github/workflows/sdd-triage.yml, .github/workflows/sdd-triage-{dedupe-tasks,promote-ready}.yml, .github/workflows/sdd-monitor.yml, .github/workflows/sdd-pr-sanitize.yml		 Triage routing, dedupe-tasks, promote-ready, monitor, and PR sanitize actions all updated from @v0.1.0 to @v0.1.2.

🎯 2 (Simple) | ⏱️ ~8 minutes

Possibly Related PRs

  • gominimal/minspec-test#60: Bumps the same set of Spectacles wrapper workflows from @v0.1.0 to @v0.1.2 following the earlier suite installation.
  • gominimal/webapp#102: Updates the same Spectacles wrappers' pinned versions, advancing from intermediate versions to @v0.1.2.
  • gominimal/minimal#307: Introduces the original SDD workflow wrappers that this PR updates with newer version pins.

Suggested Reviewers

  • jtnkminimal
  • twitchyliquid64

Poem

🐰 Version bumps dance through workflows bright,
Actions and spectacles—updated to v0.1.2 tonight!
From v4 to v7, artifacts ascend with care,
CI macOS and SDD pipelines float on air. ✨

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Title check ✅ Passed The title accurately summarizes the main change: bumping 11 GitHub Actions dependencies. It is concise, specific, and uses clear language aligned with the actual changeset.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
📝 Generate docstrings
  • Create stacked PR
  • Commit on current branch

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

@dependabot @github

dependabot Bot commented on behalf of github Jun 8, 2026

Copy link
Copy Markdown
Contributor Author

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

@dependabot dependabot Bot closed this Jun 8, 2026
@dependabot
dependabot Bot deleted the dependabot/github_actions/github-actions-5e41dfc29d branch June 8, 2026 20:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

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

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants