Repository navigation
Conversation
Use dedicated account auth and private project robots for staging. Import immutable releases and publish through the customer lifecycle; keep private PR previews in separate repositories. Leave workflows unchanged pending release-environment and credential approval. Verify real local gateway/Core/Harbor retries with deterministic CLI builds and clean up only identity-verified disposable fixtures.
Route releases and private previews through verified lifecycle publication with immutable revisions and fail-closed provisioning guards. Dedicated credentials and protected environments remain rollout prerequisites. Recover the September 29 local draft and its offline regression coverage into the durable workspace. No remote publication performed.
MarcStdt
marked this pull request as ready for review
October 4, 2026 16:21
Collaborator
|
MarcStdt
had a problem deploying
to
scroll-preview
October 4, 2026 16:25 — with 
GitHub Actions
Failure
GitHub Actions
Failure
Requires the platform command-controls package release before merge. Keep local registry versions out of the public lockfile.
Regenerate with the npm 10 resolver used by CI. The newer local npm resolver omitted optional esbuild peer entries required by npm ci.
MarcStdt
changed the title
Contributor
Author
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.
Scope
One Scrolls UI/artifact PR against master; not an artificial stack.
CI configuration
Only SCROLL_REGISTRY_USER and SCROLL_REGISTRY_PASSWORD secrets are required with the existing defaults. Both reusable-workflow callers inherit secrets. Host, namespace and released CLI/runtime references can be overridden with repository variables; see docs/registry-publication.md.
Registry updates do not require Core/Auth APIs, a Druid account or catalog registration. Existing public repositories are updated directly.
Verification
Dependency blocker — not merge/release ready
The config editor imports ensureFileService from Druid UI #18. Release the corresponding npm packages and update this consumer's package/lockfile before merging. The committed lockfile still uses public versions lacking the API; local 1000.* packages are not release dependencies.
For full feature rollout, make the matching runtime #124 and monorepo #377 available before publishing the new editor artifacts. This is application/runtime compatibility, not a registry-publication API dependency.
Review order
.github/workflows/scrolls.yml and callers → scripts/push.sh and push regressions → UI/config-editor and staging changes → docs/registry-publication.md.