Repository navigation
chore(release): cut 0.6.0 - #167
Merged
Merged
Conversation
Promote develop to main: 0.5.0 (Build journey, spec 1.3, the store and identity, the studio redesign, scan-vs-live)
Promote develop to main: the store complete (slices 4–6), Settings, Windows CI, Compare in the bundle
main carries the merge commits of the 0.5.0 and develop promotions (#131, #166) that develop does not; their trees are develop's already, so this merge changes no file: it only records main's history in develop, and the 0.6.0 promotion fast-forwards main's side. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01UhPGnqVJ24goSVtbKpdkLJ
Everything under Unreleased since 0.5.0 (2026-10-01) moves under a `## 0.6.0 — 2026-10-15` heading with a one-paragraph summary; Unreleased stays as an empty section for what comes next. The version moves with it: package.json and the lockfile, the footer's fallback label, and the image tag in the Dockerfile, the README and the k8s manifests and their docs. References to the pre-store release stay `v0.4.0` (the CI job and the rollback notes build that tag on purpose), and the ones that name 0.5.0 as a build to roll back to, or as the build a fixture or a copied rule comes from, stay 0.5.0; the rollback notes now say the store build is 0.6.0 and that 0.5.0 was the first store release. Two guards that did not exist at 0.5.0 move with the cut. VENDOR-MANIFEST.json carries the package version, so it is regenerated: version 0.6.0, and 0.6.0 is the new baseline (every module's changedSinceRelease false, no releasedExports, removedSinceRelease empty); no module's bytes or exports change. tools/test-doc-test-totals.mjs read the totals the Unreleased entries quote and required at least one; right after a cut Unreleased is empty and those entries are the release section under it, so the guard reads that section until the next entry lands, with the same rules. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01UhPGnqVJ24goSVtbKpdkLJ
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.
Cuts 0.6.0, following the 0.5.0 pattern (#132 and #133) in one PR.
Commits
maincarried Promote develop to main: 0.5.0 (Build journey, spec 1.3, the store and identity, the studio redesign, scan-vs-live) #131's and Promote develop to main: the store complete (slices 4–6), Settings, Windows CI, Compare in the bundle #166's merge commits only. No file changes.## Unreleasedmoves under## 0.6.0 — 2026-10-15with a one-paragraph summary. Unreleased stays as an empty section.package.jsonandpackage-lock.json(version fields only, no dependency moved), the studio footer's fallback label instudio/index.html, the image tag inDockerfile,README.md,deploy/k8s/*anddeploy/k8s-journeys/kustomization.yaml, and the k8s rollback notes.VENDOR-MANIFEST.json: regenerated bynpm run vendor-manifest. Itsversionis 0.6.0, andchangedSinceRelease/releasedExportsreset against the new release baseline, as the manifest is meant to.tools/test-doc-test-totals.mjs: right after a cut, the Unreleased section is empty. The check now reads the release section directly under it until the next entry lands, instead of failing on an empty Unreleased.v0.4.0) and historical mentions of 0.5.0, such as the 0.5.0 CHANGELOG section and the store-050 guard fixture and its tests.Summary paragraph (the CHANGELOG's)
The store-and-seams release. The store now holds the studio's state, not only its identities: the pack registry moved into the database; services, their environments and an org's MCP endpoints are records managed over HTTP; every change a principal makes through the server is an audit row that can be read; the home is the org's services table with a page per service; and Settings is the org's administration as a studio mode (STORE_PLAN slices 4 to 6). A downstream can vendor and rebadge Observogram without forking it: a manifest of the vendorable modules, the MCP transport hook, the artefact taxonomy classifier, reverse-proxy identity passthrough, one brand config and an embeddable static bundle, which now runs Compare and loads no font over the network. The rebadge batches built on those seams: a reviewer's verdicts, waivers and an exportable service audit report; canonical pack production, where a fresh crawl is a valid pack; a true-snapshot live pack behind a connection test; comparison identity modes; the MCP server's settings in the page. Spec 1.4 keeps a repository's operational alert rules and pairs them with the live ones. Windows has a CI leg, and a path there is compared by what it names, not by how it is spelled: a journey's org scope holds, and
packc store purge-orgdecides the users file by what deleting the org's root takes. Also: a malformed JSON body is answered as JSON on every route, a server-run journey's notification reads only its org's hooks, the settings-policy deadline is per rule, and the id clocks time the pattern, not the machine.Checks
node tools/cli.mjs --versionreadsv0.6.0.vendor-manifest:checkis in sync (57 modules).test-doc-test-totals,test-vendor-manifestandtest-deploy-manifestspass (19/19).After this merges
develop → main. It applies cleanly thanks to f4bfcfb.v0.6.0onmainand publish the GitHub release, with the CHANGELOG's 0.6.0 section as its notes.🤖 Generated with Claude Code
https://claude.ai/code/session_01UhPGnqVJ24goSVtbKpdkLJ
Generated by Claude Code