Skip to content

feat(runtime): preserve and apply exact releases - #124

Merged
MarcStdt merged 2 commits into
masterfrom
codex/runtime-release-descriptor-read
Oct 27, 2026
Merged

MarcStdt merged 2 commits into
masterfrom
codex/runtime-release-descriptor-read

Conversation

@MarcStdt

@MarcStdt MarcStdt commented Sep 27, 2026 •

Copy link
Copy Markdown
Contributor

Preserves installed release identity through artifact materialization, backup/restore and explicitly accepted deployment updates.

  • Preserve the installed release manifest during selective transfers and restoration; stage extraction and roll back on pull failure.
  • Coordinate backup, restore and accepted updates with runtime maintenance, and enforce the expected installed digest before applying a reviewed immutable artifact.
  • Report installed release descriptors from normal pull workers and cache them in persisted runtime state. Normal release queries avoid an extra inspection worker; legacy state can be inspected once. Failed materialization does not report a stale release as successfully installed.
  • Typed restore pull dependency, SQLite/ConfigMap state handling, deterministic artifact hashes and scoped ownership/file protection regressions.
  • Remove the separate druid-scroll-validator binary and build/install wiring while retaining normal runtime validation.

Review registry transfer options, worker pull/restore, runtime maintenance and accepted-release handling, installed-release state stores, then HTTP/generated contracts and failure tests.

Verification

Dependencies

Matching monorepo #377, publisher #90, Druid UI #18 and local launcher #10.

No merge, package release or production deployment is included.

@MarcStdt MarcStdt changed the title feat(runtime): apply accepted Scroll releases feat(runtime): unify Scroll release lifecycle Sep 28, 2026
@MarcStdt
MarcStdt changed the base branch from codex/scroll-runtime-backup-orchestration to master September 28, 2026 01:43
@MarcStdt
MarcStdt changed the base branch from master to codex/runtime-accepted-release-updates October 4, 2026 16:21
@MarcStdt
MarcStdt marked this pull request as ready for review October 4, 2026 16:21
@MarcStdt
MarcStdt added this pull request to stack #126 October 4, 2026 16:21
@druid-infra

Copy link
Copy Markdown
Contributor
Error: This repo is not allowlisted for Atlantis.

@MarcStdt MarcStdt changed the title feat(runtime): unify Scroll release lifecycle [4/4] feat(runtime): validate releases and finalize lifecycle safeguards Oct 4, 2026
@MarcStdt MarcStdt changed the title [4/4] feat(runtime): validate releases and finalize lifecycle safeguards [4/4] perf(runtime): cache installed release on pull Oct 27, 2026
Preserve installed release identity through backup/restore and accepted
updates. Cache release descriptors from pull results and enforce the
expected installed digest before application.

Stage restoration with rollback, retain ownership/file protections, and
remove the standalone semantic validator. Fix the running-backup fixture
so its queue stops before temporary state cleanup.
@MarcStdt
MarcStdt removed this pull request from stack #126 October 27, 2026 00:17
@MarcStdt
MarcStdt force-pushed the codex/runtime-release-descriptor-read branch from df15dbd to 88d01ef Compare October 27, 2026 00:17
@MarcStdt MarcStdt changed the title [4/4] perf(runtime): cache installed release on pull feat(runtime): preserve and apply exact releases Oct 27, 2026
@MarcStdt
MarcStdt changed the base branch from codex/runtime-accepted-release-updates to master October 27, 2026 00:17
Use only the installed release recorded by a successful pull. Remove
the inspect worker mode and its Docker and Kubernetes special cases.

BREAKING CHANGE: older runtimes without confirmed release metadata
return an error instead of starting a compatibility inspection worker.
@MarcStdt
MarcStdt merged commit adb01fe into master Oct 27, 2026
13 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants