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.
This branch had an error being deployed
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 cohesive publisher/UI PR; not an artificial stack.
The former import helper and tests are removed. Earlier import-based acceptance results do not validate this replacement publisher.
Review order
scripts/publish-owned and tests → scripts/push.sh and workflow guards → UI file-service gateway and tests → docs/shared-lifecycle-publication.md.
Dependency blocker — not merge/release ready
The UI imports ensureFileService from Druid UI #18. That API is not in the currently published package. The lockfile contains public npm versions (no localhost registry or 1000.* local versions), but a clean public-package build remains blocked until the new Druid UI package is released and this consumer lockfile is updated.
No npm release was authorized or performed. Local UI tests/build used the adjacent unpublished package and do not prove the public dependency build passes.
Fresh local verification — 2026-10-22
No fresh live authenticated publisher/Harbor or browser/Kubernetes E2E run was performed.
Rollout
Depends on the monorepo stack, runtime stack and Druid UI package release. Configure separate preview/release identities, protected environments and credentials before enabling SCROLL_LIFECYCLE_READY. Keep gates fail-closed; workflow YAML does not provision protections.
No merge or production publication was performed.
Clean-install CI follow-up
The first run exposed missing optional esbuild peer entries in the lockfile regenerated by the newer local npm resolver. Commit 07c12ac regenerates those entries with npm 10; isolated npm ci --ignore-scripts --dry-run now passes. This fixes installation, not the separate unpublished Druid UI API dependency above.
Latest CI confirms installation now succeeds; verification stops at the documented dependency:
TS2305: @druid-ui/plattform has no exported member ensureFileService. Failing dependency check. Release Druid UI #18 and update this lockfile before merge; do not bypass the check.