Prepare v0.13.1 — install / deploy L1 repair + security patch#474
Merged
Conversation
The release job fed docs-site/docs/release-notes/<TAG>.md into `gh release create --notes-file` verbatim. GitHub renders the body as plain Markdown and does not recognise YAML front matter — worse, the closing `---` is parsed as the setext-heading underline of the metadata block above it, so the entire id:/title:/description:/sidebar_* block rendered as one giant H2 (visible on v0.10.0–v0.13.0). Strip the leading `--- ... ---` front matter with awk before publishing, emitting only the body after the second delimiter.
v0.13.1 is a fixes-only patch: it repairs fresh role-separated (L1) installs and deployments (trustedoss_app role creation, AUTO_MIGRATE plumbing, owner-password consistency + staged boot, dev entrypoint auto-migration) and bumps python-multipart 0.0.30 → 0.0.31 for CVE-2026-53540. No feature or schema change. - add docs-site/docs/release-notes/v0.13.1.md - record the 0.13.1 entry in CHANGELOG.md - reorder v0.13.0 note (sidebar_position 1 → 2) so v0.13.1 sits on top - bump install-uat's default IMAGE_TAG 0.13.0 → 0.13.1
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.
What
Prep for the v0.13.1 patch release. Fixes-only — no new features, no schema changes.
The substantive fixes are already merged to
main; this PR adds the release notes / changelog and version bookkeeping so taggingv0.13.1produces a correct GitHub Release.Why a release now
Fixes landed since v0.13.0 that ship in the images / install path and are user-facing:
trustedoss_approle was never created on fresh L1 stacks — psql variable substitution inside a dollar-quoted block silently abortedpostgres-init.sh. (fix(deploy): repair L1 role provisioning + plumb AUTO_MIGRATE into the container #466)AUTO_MIGRATEnever reached the container, so the backend attempted DDL as the unprivileged app role. (fix(deploy): repair L1 role provisioning + plumb AUTO_MIGRATE into the container #466)python-multipart0.0.30 → 0.0.31 (CVE-2026-53540), ships in the backend image. (chore(deps): bump python-multipart 0.0.30 → 0.0.31 (CVE-2026-53540) #472)A from-scratch role-separated install at v0.13.0 could fail to provision or deadlock on boot; v0.13.1 is the fix.
Contents
docs-site/docs/release-notes/v0.13.1.mdCHANGELOG.md—[0.13.1]entrysidebar_position1 → 2)install-uatdefaultIMAGE_TAG0.13.0 → 0.13.1After merge
Tag
v0.13.1on the merge commit and push —release.ymlbuilds/publishes the images, runs the release gate against the published stack, and reveals the Release (front matter now stripped from the notes, per #473).