Release 0.84.0: organisational-intelligence repositioning + compliance packs - #258
Merged
Merged
Conversation
…e packs Public port of private PR #342 (merged 2026-09-15, merge commit 6c780364). Version bump only — no source changes. All eight files are byte-identical to the merged private/master. Ships the six non-merge commits already on public master 5e80aa2: 129cfeb CR-README-01 reposition README + PyPI (public PR #257) c9bc645 CR-010.R3 compliance packs as data, x-sox first b9515ef CR-DIST-06 sentinel fixes: skip on absent manifests bb71b15 CR-DIST-06 guard that referenced listing assets exist e38ed34 CR-DIST-06 follow-up: marketplace manifests were missed 334d198 CR-DIST-06 stop distribution manifests drifting WHY THIS RELEASE EXISTS PyPI metadata is immutable per version. 0.83.0 was published 2026-07-31, so pypi.org/project/graqle still renders the OLD README — including the `readme = "README.md"` pointer defect and the two non-existent commands that CR-README-01 fixed. Merging #257 fixed GitHub immediately and did nothing for PyPI. A version bump is the only mechanism that changes that page. Shipping the README alongside x-sox is deliberate: the new README advertises the SOX/COSO pack, and until this release that pack is not installable from PyPI. Releasing the copy alone would describe a capability users cannot get. MANIFEST SYNC — NOT the 0.83.0 three-file shape CR-DIST-06 added tests/test_packaging/test_manifest_version_sync.py, which asserts AT REST that all five distribution manifests equal graqle.__version__. A version bump without syncing them turns five tests red. This commit carries the output of `python scripts/ci/sync_manifest_versions.py 0.84.0`: server.json (x2 keys), both plugin manifests, both marketplace manifests. VERIFICATION ON THIS PUBLIC TREE - All 8 files byte-identical to merged private/master (scoped diff empty). - Version consistency across all 7 carriers: ALL CONSISTENT at 0.84.0. - test_manifest_version_sync + test_readme_snapshot_lock + test_eu_ai_act_docs_present: 71 passed. - Wheel builds as graqle-0.84.0-py3-none-any.whl; METADATA Summary is the new description and long_description is README_PYPI.md (4,762 chars) — new hero present, old hero absent, broken `graq learn "<text>"` absent. NOT DONE HERE — deliberately No tag is pushed. `git tag v0.84.0` triggers ci.yml publish to PyPI via Trusted Publishing, and that is irreversible. Tagging waits until this PR is merged and the owner authorises the release. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
🛡️ GraQle PR Guardian💥 Blast Radius: 8 modules affected
Total blast radius: 8 🏛️ Governance Verdict
|
| Metric | Value |
|---|---|
| Blast Radius | 8 |
| Files Analyzed | 8 |
| Blocked | 0 |
| SHACL Violations | 0 |
| Verdict | WARN |
🔬 Powered by GraQle PR Guardian v0.1.0 · Scan completed 2026-09-15T05:30:41.793985+00:00
harishquantamix
approved these changes
Sep 15, 2026
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.
Release 0.84.0 — version bump only, no source changes
Public port of private PR #342 (merged 2026-09-15, merge commit
6c780364). All eight files arebyte-identical to the merged
private/master.Ships the six non-merge commits already on public master
5e80aa21:129cfebac9bc6456x-soxfirstb9515ef8bb71b156e38ed344334d1986Why this release exists
PyPI metadata is immutable per version. 0.83.0 was published 2026-07-31, so
pypi.org/project/graqle still renders the old README — including the
readme = "README.md"pointer defect and the two non-existent commands that CR-README-01 fixed.
Merging #257 fixed the GitHub page immediately. It did nothing for PyPI. A version bump is the
only mechanism that changes that page.
Shipping the README alongside
x-soxis deliberate: the new README advertises the SOX/COSOpack, and until this release that pack is not installable from PyPI. Releasing the copy alone
would describe a capability users cannot actually get.
The 0.83.0 release commit touched only
CHANGELOG.mdplus the two version carriers. That is nolonger sufficient. CR-DIST-06 added
tests/test_packaging/test_manifest_version_sync.py, whichasserts at rest that all five distribution manifests equal
graqle.__version__. A bump withoutsyncing them turns five tests red.
This PR therefore also carries the output of
python scripts/ci/sync_manifest_versions.py 0.84.0:server.json(both keys), both plugin manifests, both marketplace manifests.Verification on this public tree
private/mastertest_manifest_version_sync+test_readme_snapshot_lock+test_eu_ai_act_docs_presentgraqle-0.84.0-py3-none-any.whl✅long_description=README_PYPI.md(4,762 chars); new hero present, old hero absent, brokengraq learn "<text>"absentRelease Gate (PyPI)will fail here as it does on every PR touchingpyproject.tomlorgraqle/**(emptyGRAQLE_LICENSE,No graph file found). It is not a required check — theonly required context on master is
ip-protection-gate.🛑 No tag is pushed by this PR
git tag v0.84.0triggersci.yml→ publish to PyPI via Trusted Publishing, and that isirreversible. Tagging waits until this PR is merged and the owner explicitly authorises the
release.
After this merges
git tag v0.84.0 && git push origin v0.84.0🤖 Generated with Claude Code