chore(objectos): bump @objectstack 10.2 → 12.1 so the runtime image ships latest#35
Merged
Merged
Conversation
…ships latest - apps/objectos deps pinned at ^10.2.0 + frozen lockfile kept the ghcr image stuck at framework 10.2 even though CI runs on every push. - Bump all @objectstack/* to ^12.1.0 and regenerate pnpm-lock.yaml. - Work around a 12.1 standalone inconsistency: createStandaloneStack emits api.projectResolution:'none', which the 12.1 validator rejects (enum: required|optional|auto, field optional). Standalone has scoping disabled, so drop the field in objectstack.config.ts. Verified: objectstack compile passes; serve boots (/ -> 302, /_console/ -> 200, SqlDriver loaded, 22 plugins).
…uction Image-level verification of the 12.1 build against postgres showed the container refuses to boot without OS_SECRET_KEY (LocalCryptoProvider guards sys_secret/datasource credentials in production). The compose already passed these through but with empty defaults, so a bare `docker compose up` crashes mid-boot with no obvious hint. Add a header block + inline REQUIRED markers.
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
1 participant
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.
Why
apps/objectospinned all@objectstack/*deps at^10.2.0. Combined with the--frozen-lockfileinstall indocker/Dockerfile, the ghcr image kept building at framework 10.2 on every push — even though upstream is now at 12.1.0. Bumping the deps + regenerating the lockfile is what actually moves the published image forward.Changes
apps/objectos/package.json: all 10@objectstack/*deps^10.2.0→^12.1.0.pnpm-lock.yaml: regenerated (resolves to 12.1.0).apps/objectos/objectstack.config.ts: work around a 12.1 standalone inconsistency —createStandaloneStackhard-codesapi.projectResolution: 'none', but the 12.1 protocol validator'sapi.projectResolutionenum only acceptsrequired|optional|auto(the field is optional). Standalone runs withenableProjectScoping: false, so we drop the field socompile/validatepasses.docker/docker-compose.yml: flagOS_SECRET_KEY/OS_AUTH_SECRETas required-in-production (header block + inline markers) — see verification note below.Verification
Source level (local):
pnpm --filter @objectos/server build(objectstack compile) → ✓ Build complete, artifact written.objectstack serveon sqlite:/→ 302,/_console/→ 200,✓ Server is ready.objectstack serveon postgres 17:Driver: SqlDriver(pg), 59 system tables created, zero errors.Image level (local
docker buildof the Dockerfile, run against postgres 17):pnpm install --frozen-lockfile+objectstack compile).healthy;/→ 302,/_console/→ 200;Driver: SqlDriver(pg); 28 plugins; 59 tables created in postgres; no error lines.OS_SECRET_KEY(LocalCryptoProvider: Refusing to start in production without a stable encryption key). The compose already passed it through but with an empty default, so a baredocker compose upcrashes mid-boot with no obvious hint. Documented indocker/docker-compose.yml. (Pre-existing requirement, surfaced by image-level testing — the smaller plugin set in a plain sourceservedoesn't reach the crypto guard.)Note on staying current
This is a one-time bump; the caret + committed lockfile keep the image reproducible at 12.1 until the next intentional bump. If we want the image to track upstream automatically, add Renovate/Dependabot for the
@objectstack/*group rather than floating the range.