chore(release): cut v1.1.1 (marketplace schema + pyproject version sync hotfix) - #44
Merged
Conversation
chore(backmerge): sync develop with master after v1.1.0 release
2 tasks
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
Cut release v1.1.1 (PATCH). Brings develop (now at
3c8ab11after PR #43 merge) tomaster. The hotfix closes two gaps discovered while deploying v1.1.0:claude plugin marketplace addwas blocked by a missingownerfield in.claude-plugin/marketplace.json(Claude Code v2.1.263 schema requirement). Fixed in PR fix(release): marketplace.json owner + pyproject.toml version sync for v1.1.1 #43 by adding$schema, top-leveldescription,owner.name.pyproject.toml'sversionfield was not inscripts/sync_version.py's sync surface. Fixed in PR fix(release): marketplace.json owner + pyproject.toml version sync for v1.1.1 #43 by addingTOML_VERSION_SPECS+sync_toml_version()and asserting the[project]table is present inrequire_known_paths(). Regression tests added.SemVer rationale
→ Result: 1.1.0 → 1.1.1 (PATCH). The v1.1.0 features already shipped; this PR only fixes release-artifact bugs and the marketplace-add path.
What is in this release branch
The branch
release/v1.1.1is a fast-forward ofdevelopat3c8ab11(PR #43 + the pr-title-check re-trigger commit). No additional commits; no source underskills/adr-toolkit/scripts/changed beyond what PR #43 already landed.Release flow (per AGENTS.md)
release/v1.1.1→master) merges.master→develop(follow-up PR).v1.1.1frommasterand push —.github/workflows/release.ymlruns pytest +sync_version --check(now also coveringpyproject.toml) + tag == VERSION, then publishes a GitHub Release with the skill tarball + sha256 + Python wheel/sdist. With this hotfix, the wheel/sdist will correctly beadr_toolkit-1.1.1-*instead of1.0.1. PyPI publish via Trusted Publisher (continue-on-error: true, tracked inimprovements.md).release/v1.1.1branch.Verification
scripts/sync_version.py --check: exit 0 (now also coverspyproject.toml).develop@3c8ab11, so the same green CI applies.Examples Impact
examples/change.ADR Impact