Release 0.6.0 - #93
Merged
Merged
Conversation
Since 0.5.0: builds declare the optimizer trial's limits, the compiled task is frozen and verifiable with per-run tokens delivered through the environment, a build can pin a published vero instead of copying the source tree, and each build records the optimizer harness releases its results used, replicable with `vero harbor run --pin-harness`. The credential check moved from compile to launch, and the benchmark tree was renamed harness-opt-bench. Co-Authored-By: Claude Fable 5.1 <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.
Version bump only. Once merged, tag the merge commit
v0.6.0to publishscaleapi-vero 0.6.0; the publish workflow checks that the tag equals the version inpyproject.toml.Since 0.5.0: builds declare the optimizer trial's limits; the compiled task is frozen and verifiable, with per-run tokens delivered through the environment; a build can pin a published vero instead of copying the source tree; each build records the optimizer harness releases its results used, replicable with
vero harbor run --pin-harness; the credential check moved from compile to launch; the benchmark tree isharness-opt-bench.🤖 Generated with Claude Code
The PR appears safe to merge because the release version is synchronized across package metadata and the lockfile and matches the publishing workflow’s validation contract.
Summary
vero/pyproject.tomlfrom 0.5.0 to 0.6.0.vero/uv.lock.Reviews (1) · Last reviewed commit: "Release 0.6.0"