Repository navigation
release: pin LibreDB Studio 1.1.0 for installer and chart 1.2.0 - #49
Merged
Merged
Conversation
Raise the installer and chart to 1.2.0, keep LibreDB Platform 1.1.0, and pin LibreDB Studio 1.1.0 with the Studio chart 0.1.103. Studio 1.1.0 is not published yet, so the Studio image digest and the Studio chart sha256 are the all-zero placeholder sha256:000...0, which release:check and embed refuse until the real values replace them. Chart.lock, release/history/1.2.0.json, the Helm jobs bundle and the vendored governance contract follow from their generators once Studio publishes. Studio 1.1.0 refuses OIDC_ROLE_PREFIX in governance mode, so the env inventory lists it among the variables the Studio env never sets, with a drift test against the Studio image.
…rt 1.2.0 Replace the all-zero placeholders with the published Studio 1.1.0 image index digest sha256:e91183def05f4c13703c77363ec51ad68bfa45b1b1d3b92dc53c331b67e53d2c and the Studio chart 0.1.103 tgz sha256 2998a9612e175f6cada18a5d704282e778706e542377dcd22a3eee1ee77ccf2c in the release manifest, the chart's Artifact Hub images and the chart values. Regenerate the files that follow from them: the vendored governance contract from Studio tag 1.1.0 (GOVERNANCE.md only, contract-v1.json is unchanged), Chart.lock with helm dependency update, release/history/1.2.0.json with release:record, and the Helm jobs bundle with build:helm-jobs.
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.
Release 1.2.0 of the installer and the Helm chart
libredb-platform: it pins the published LibreDB Studio 1.1.0 and keeps LibreDB Platform at 1.1.0.ghcr.io/libredb/libredb-studio:1.1.0@sha256:e91183def05f4c13703c77363ec51ad68bfa45b1b1d3b92dc53c331b67e53d2c, Studio chart 0.1.103 (sha2562998a961...cf2c),reportedVersion1.1.0.contract-v1.jsonunchanged, two lines added toGOVERNANCE.md.OIDC_ROLE_PREFIXunder governance, so it joins the installer's forbidden Studio variables, with a unit and a drift test.Chart.lock,release/history/1.2.0.jsonand the jobs bundle come from their generators.Local checks:
release:check, typecheck, build (versionprints 1.2.0), the drift integration tests (6/6), root lint, typecheck and tests.coverage:checktimed out under host load here (#42), and passes with a longer per-test timeout; CI is the gate.The two pinned images already run on the Railway dev stack, checked end to end with a mobile PKCE token.