Skip to content

Accept any Runtime image name in the Runtime reference - #160

Merged
SaladDay merged 1 commit into
mainfrom
codex/web-runtime-ref
Sep 26, 2026
Merged

SaladDay merged 1 commit into
mainfrom
codex/web-runtime-ref

Conversation

@SaladDay

@SaladDay SaladDay commented Sep 26, 2026 •

Copy link
Copy Markdown
Collaborator

Rename step W1 (design 60-rename-oac-design.md): the Web stops hard-coding the Runtime image name in the Runtime reference.

The Runtime reference prefix changes from parsar-core-runtime@sha256:… to oac-runtime@sha256:… in the backend's R2. Before this change, two Web regexes required the old prefix, so R2's manifest would have broken the setup wizard.

Change

One shared RUNTIME_REF_PATTERN = /^[a-z0-9][a-z0-9._-]*@sha256:[0-9a-f]{64}$/ now serves both:

  • the manifest parser (deployment-specification.ts);
  • the wizard's microsandbox_ref field check (runtime-release.ts).

Core stays the authority: it checks the reference against the manifest exactly. The Web only checks the shape before submitting.

Tests

  • A new unit test accepts parsar-core-runtime@… and oac-runtime@…, and rejects a ref without @sha256:, a short digest, uppercase hex and an empty name.
  • Results: typecheck ✓, web tests 367, nodes.spec.ts 8/8.

View with [code]smith Autofix with [code]smith
Need help on this PR? Tag @codesmith with what you need. Autofix is disabled.

@SaladDay
SaladDay merged commit b54b081 into main Sep 26, 2026
2 checks passed
@SaladDay
SaladDay deleted the codex/web-runtime-ref branch October 7, 2026 06:38
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.

1 participant