Repository navigation
Prepare 0.10.0: install version, and the upgrade note it needs - #105
Merged
Merged
Conversation
The release workflow refuses a tag that installation.md does not document, so the install lines move to 0.10.0. The upgrade note exists because the catalog label changes format. config-version now prints <environment>-<code_id> (#104), so anything matching the bare 0.9 label, an OpenVoxDB query or a dashboard, has to change first. It also says when an upgraded server starts printing the new form: OpenVox computes the label once per cached environment, so under environment_timeout = unlimited the old form lasts until the next deploy or restart. The provenance fix (#103) needs nothing from the operator, but the note says when the missing branch commits appear. CONTRIBUTING still told the release to bump a VERSION= line in the README, which has had none since the install moved to the package repository in #96. Lab: batches B, F, and I green (56/56) against an fa7e9cb snapshot built with go1.26.9, including the new I8: on real r10k, a branch that has not diverged from production gets its own label and its own provenance commit (codavox-lab 82397df). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Signed-off-by: Michael Harp <mike@mikeharp.com>
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.
Release prep for 0.10.0.
Change
docs/installation.mdinstalls 0.10.0. The release workflow refuses a tag this file does not document.docs/production.mdgets an "Upgrading to 0.10" note:code_idto<environment>-<code_id>(Put the environment in the catalog label #104). Anything matching the 0.9 form, such as an OpenVoxDB query, a dashboard, or an alert, needs updating first. The note says why an upgraded server underenvironment_timeout = unlimitedkeeps the old form until the next deploy or restart.CONTRIBUTING.mdno longer tells a release to bump aVERSION=line in the README, which has had none since Install from the harpworks repository, built outside this repo #96.Lab
Batches B, F, and I are green, 56 of 56, against an
fa7e9cbsnapshot built with go1.26.9 (codavox-lab82397df). Batch I was updated for the new label, and its new check I8 covers both changes on real r10k: a branch that has not diverged fromproductionserves the samecode_id, is labeledaudit_i8-…rather thanproduction-…, and has its own provenance record and fleet-view commit.Test plan
mainAssisted by Claude.