chore: declare version 1.1.0#79
Closed
Coding-Dev-Tools wants to merge 1 commit into
Closed
Conversation
Bump the five places the client version is written, all of which `tests/test_packaging.py` requires to agree: `pyproject.toml`, the `PackageNotFoundError` fallback in `engraphis/__init__.py`, the commercial manifest that `scripts/check_commercial_manifest.py` cross-checks against pyproject, and the plugin/marketplace pair under `.claude-plugin/`. Editing the two `.claude-plugin/*.json` files invalidates their entries in `.claude-plugin/skill-assets.sha256`, which `test_packaging.py` verifies by hashing the files on disk, so those two digests are regenerated here. All six files are LF, as `.gitattributes` requires. 1.1.0 rather than 1.0.2: the unreleased work adds commands and changes the managed-compute consent default, which is a minor bump. Note that 1.0.1 was declared and dated in the changelog but never tagged or published — PyPI's latest is 1.0.0 — so 1.1.0 is the first release to actually carry it. No tag is pushed by this commit; publishing stays a separate, deliberate step. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
There was a problem hiding this comment.
Coding-Dev-Tools has reached the 50-credit limit for trial accounts. To continue receiving code reviews, upgrade your plan.
Owner
Author
|
Superseded by #80, which consolidated this change with the complete audited 1.1.0 client release and is now merged into main. |
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.
Bumps the declared client version to 1.1.0. No tag, no publish — this only changes what the tree says about itself.
Why 1.1.0 and not 1.0.2
The unreleased work adds new commands (
engraphis,engraphis connect) and changes the managed-compute consent default. That is a minor bump, not a patch.Worth recording: 1.0.1 was never released.
pyproject.tomlsaid1.0.1andCHANGELOG.mdcarries a dated## [1.0.1] - 2026-07-24section, but nov1.0.1tag exists and PyPI's latest is still1.0.0. 1.1.0 is the first release that will actually carry that work.The five places the version is written
tests/test_packaging.pyrequires all of these to agree, so they move together:pyproject.tomlengraphis/__init__.py(PackageNotFoundErrorfallback)test_source_tree_version_matches_pyprojectengraphis/commercial_manifest.jsonscripts/check_commercial_manifest.py.claude-plugin/plugin.jsontest_git_plugin_release_version_and_asset_hashes_are_exact.claude-plugin/marketplace.jsonEditing the two
.claude-plugin/*.jsonfiles invalidates their digests in.claude-plugin/skill-assets.sha256, which the same test verifies by hashing the files on disk — so those two lines are regenerated. All six files are LF, per.gitattributes.Verification
tests/test_packaging.py+tests/test_release_infrastructure.py— 22 passedpython scripts/check_commercial_manifest.py—commercial manifest check: OKMerge last
Merging this rebases every other open PR, so it should land after the rest, immediately before tagging.
Two things this PR deliberately does not do
CHANGELOG.mdis untouched.[Unreleased]still gains entries as the open PRs land; it gets renamed to[1.1.0]as part of cutting the release, not here. Note thattests/test_release_infrastructure.py:205-206pins the literal## [1.0.1] - 2026-07-24heading, so folding 1.0.1 into 1.1.0 later means updating that test too.scripts/check_commercial_manifest.pyrequires the website to contain"v" + manifest["version"], but that check only runs when--website-rootis passed, and neitherci.ymlnorrelease.ymlpasses it. So the live site will keep sayingv1.0.1after this ships and nothing in CI will catch it. Flagging rather than fixing, since the website is not in this repo.🤖 Generated with Claude Code