chore(release): bump version to 3.2.0#43
Merged
Conversation
Unblocks publishing the constation/attestation modules merged in BaseIntelligence#41/BaseIntelligence#42, which no released wheel currently contains. Aligns pyproject, release manifest, and uv.lock so github-release identity asserts pass for tag v3.2.0. Ultraworked with [Sisyphus](https://github.com/code-yeongyu/oh-my-openagent) Co-authored-by: Sisyphus <clio-agent@sisyphuslabs.ai>
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (2)
📝 WalkthroughWalkthroughThe project version and release manifest were updated from 3.1.2 to 3.2.0. Contract and API version fields remain unchanged. ChangesRelease versioning
Estimated code review effort: 1 (Trivial) | ~2 minutes Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
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.
Summary
v3.2.0tag can cut a wheel that includes the constation/attestation modules already onmain(feat(constation): production Lium image-attestation wire #41, fix(scripts): allow live prism Lium attestation e2e under PrismSettings #42).git.Changes
pyproject.toml:[project] version = "3.2.0"src/base/challenge_sdk/release_manifest.json:artifact_version = "3.2.0",release_id = "v3.2.0"uv.lock: workspace packagebaseversion3.2.0(required —uv sync --locked/ monorepo-workspace + github-release jobs fail without it; one-line identity bump only)No functional code, dependency, or migration changes.
Why these fields move together
.github/workflows/ci.ymlgithub-releaseasserts on tagv*:Test plan
3.2.0/v3.2.0/ loadedARTIFACT_VERSION)uv sync --locked --extra dev --extra masteruv run ruff check ./ruff format --check .uv run mypy src testspytest --cov=base --cov-fail-under=80→ 2308 passed, 83.66% covCI
Notes
v3.2.0is a separate human step after merge.3.1.2strings left intentionally (fixture samples, prism image pins, prism Dockerfile wheel URL assertions). They are not the Base distribution identity and must not move blindly with this bump.feat/agent-challenge-eval-wire-ghcrwas left untouched via a separate git worktree.Summary by CodeRabbit