docs(release): pin README + examples to v0.4.0 (first post-rename tag)#11
Merged
Conversation
The examples used the post-rename inputs (olympus_ref) + .olympus.json but still pinned @v0.2.0 — a pre-rename tag that has no olympus_ref input and reads .agent-ops.json. So a consumer copying the examples got silent config fallback, not a working loop. Bump every "current release" reference v0.2.0 → v0.4.0 (README mechanism row + quick-start, docs/setup.md, the 6 examples/consumer wrappers). v0.4.0 is the first Olympus-named release (cut next from this commit); it reads .olympus.json and takes the olympus_ref input, so the examples are now self-consistent. docs/migration.md is intentionally left referencing v0.2.0/v0.3.1 — those are heron's real pre-rename pins and the historical migration story. Co-Authored-By: Claude Fable 5 <noreply@anthropic.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.
What
Reconcile the "current release" version references to v0.4.0, the first
post-rename (Olympus-named) tag, cut from
mainright after this merges.Why
The
examples/consumerwrappers already used the post-rename input(
olympus_ref) and shipped a.olympus.json, but still pinned@v0.2.0—a pre-rename tag whose reusable workflows have no
olympus_refinput and read.agent-ops.json. A consumer copying the examples verbatim would get silentconfig fallback to built-in defaults, not a working loop. README and
docs/setup.mdcarried the same stalev0.2.0.Changes
README.md— mechanism-table version + quick-startuses:/olympus_ref.docs/setup.md— the@v0.2.0/olympus_reflockstep line.examples/consumer/.github/workflows/*.yml(×6) —uses:@…+olympus_ref.docs/migration.mdleft as-is: itsv0.2.0/v0.3.1are heron's realpre-rename pins and the historical migration narrative.
Note
v0.4.0does not exist yet; it is cut frommainimmediately after this merges(annotated tag, first Olympus-named release). Examples pinning a not-yet-cut tag
is fine — they live under
examples/, are not executed by CI, and become validthe moment the tag lands.
Docs/example-only.
check-leakage,check-legacy-naming,shellcheck, and thescripts/agent-bot/tests/*suite pass locally.🤖 Generated with Claude Code