Repository navigation
release: prepare Wild 1.2.0 developer beta - #81
nia-sg-bot wants to merge 1 commit into
Conversation
Document the Python structural-analysis and provenance improvements accumulated since 1.1.0.\n\nAlign package metadata with the approved minor beta so the immutable release workflow can validate the tag after review.
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info
WalkthroughThe changelog now includes a 1.2.0 release entry. The package version declarations in Changes1.2.0 Release Metadata
Priority: ➖ Normal Estimated code review effort: 2 (Simple) | ~8 minutes Change: Other Merge Risk: ⚪ Minimal · up to
|
Summary
1.2.0minor beta for developer dogfoodingCloses #79
Validation
python3 -m pytest -q— 210 passedwild --version—wild, version 1.2.0git diff --checkRelease behavior after merge
The tested merge should create immutable
cli-v1.2.0-<sha>, publish verified native binaries, then allow the extension handoff to prepare its reviewable release candidate. This is a controlled beta; output remains advisory.Summary by CodeRabbit