Repository navigation
Distribute matched prebuilt assets and simplify Runtime onboarding - #69
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Core installation previously carried execution payloads before an operator added a node, and self-hosted Runtime setup required manual assembly. This change provides a thin matched Core/Web/PostgreSQL bundle, verified on-demand Runtime assets, cached one-command node installation with authenticated readiness, and one-command self-hosted setup using Environment-scoped credentials. Local Docker/microsandbox installation remains optional; the default has zero nodes.
Self-hosted setup reuses V1 Docker Runtime and the existing credential issuer. Issuance enforces project, tenant and creator ownership; retries retain the original container and history. The release workflow builds Linux amd64 assets and optionally creates an unpublished draft. It does not deploy or publish automatically.
Validation:
Limits: actual execution artifacts include an explicitly trusted private test CA and are not published production releases. Acceptance source is 64f5745, with the focused local-installer fix tested as an explicit overlay; latest upstream integration is checked separately. No claim that Actions publication or external public-domain installation has run. No upgrades, provider migration, new execution architecture, additional platforms or npm publication.