release(sdk): @klickd/core 4.1.0 + klickd 4.1.0#96
Merged
Conversation
Bumps both reference SDKs in lock-step: @klickd/core 4.0.3 -> 4.1.0 (npm) and klickd 4.0.3 -> 4.1.0 (PyPI, pyproject.toml + __version__). Aligns the publish-npm.yml default expected_version to 4.1.0 (OIDC Trusted Publishing binding and guards unchanged) and documents the v4.1.0 SDK release plus the x.klickd v4.1 candidate/benchmark/DOI track in CHANGELOG and README. The v4.0.0 GA wire envelope, JSON schemas, payload semantics, and starter .klickd bytes are unchanged. No tag, GitHub Release, Zenodo DOI, benchmark result-data, or DOI evidence-pack change. Claim boundaries preserved: no universal native support, no automatic compliance, no external benchmark superiority; v4.1 candidate track is not GA. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
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
Release-prep PR that bumps both reference SDKs to 4.1.0 in lock-step and documents the release. No publish, tag, or GitHub Release is performed by this PR — those are manual, post-merge workflow_dispatch steps.
@klickd/core4.0.3 → 4.1.0 (packages/@klickd/core/package.json)klickd4.0.3 → 4.1.0 (packages/pypi/klickd/pyproject.toml+klickd.__version__)publish-npm.ymldefaultexpected_versionaligned to4.1.0(OIDC Trusted Publishing binding, workflow file path, and pre-publish guards unchanged)packaging 4.1.0 — 2026-05-30entry; README.md SDK track line updated to 4.1.0Boundaries preserved
.klickdfiles are byte-unchangedversion(4.0.0, private/unpublished) and the legacy pinned publish workflows are intentionally left unchangedTesting
@klickd/core:npm test— 101 passed (Jest, 5 suites)@klickd/core:npm run build— ESM + CJS + DTS build success@klickd/core:npm run verify:tarball— CJS + ESM smoke OK (packsklickd-core-4.1.0.tgz)@klickd/core:npm pack --dry-run— all 4 starter skills present, version4.1.0klickd:pytest tests/— 102 passed, 1 skippedklickd:python -m build— builtklickd-4.1.0sdist + wheel; wheelVersion: 4.1.0, 4 schemas + 6 starter-skill files included;klickd.__version__ == "4.1.0"node verify_vectors.mjs47/47 (13 skipped, hash-wasm not installed locally);python verify_vectors.py77/77validate_v4_schemas.pyOK;validate_v4_1_candidate_mapping.pyOK (42 artefacts);validate_starter_packs.py(nopacks/starterdir — N/A in this layout)Optional-dep notes
>=18satisfied); the publish workflow pins Node 24.hash-wasmnot installed locally → 13 JS vector cases skipped (CI installs it).argon2-cffi+jcswere installed locally to run the suite; both are declared runtime deps.🤖 Generated with Claude Code