Skip to content

Prepare 0.22.1#583

Merged
michalharakal merged 1 commit intodevelopfrom
release/0.22.1
Apr 30, 2026
Merged

Prepare 0.22.1#583
michalharakal merged 1 commit intodevelopfrom
release/0.22.1

Conversation

@michalharakal
Copy link
Copy Markdown
Contributor

Summary

Routine post-release merge bringing the 0.22.1 version bump + CHANGELOG entry forward into develop. Mirrors the 0.22.0 convention (PR #580).

0.22.1 was tagged from this branch and is already live on Maven Central via publish.yml (tags: '**' triggers on tag push, not on this PR's merge). This PR is purely the develop-side housekeeping so:

  • gradle.properties VERSION_NAME advances from 0.22.00.22.1 on develop
  • The CHANGELOG [0.22.1] - 2026-04-30 entry lands on develop
  • README Quickstart coordinates show 0.22.1
  • Future releases branch from a develop that reflects the latest published version

Single commit (6586ad9e) on top of develop's post-#582 tip — the same prep-commit shape as PR #580.

Release content (already on Maven Central)

No other behavioural changes vs 0.22.0.

Test plan

  • ./gradlew allTests on release/0.22.1 HEAD — pass in 1m 38s, 1068 tasks (verified pre-tag).
  • Maven Central publish (publish.yml run 25181718325) — completed, artifact sk.ainet.core:skainet-io-safetensors:0.22.1 is resolvable.
  • Downstream verification: SKaiNET-transformers feature/gemma4-ple-use-upstream-mmap CI run 25184460014Build & Test → completed success resolving 0.22.1 from Maven Central (no includeBuild shortcut on CI).

🤖 Generated with Claude Code

- gradle.properties: bump VERSION_NAME 0.22.0 → 0.22.1.
- CHANGELOG: add 0.22.1 section covering #582 — sharded analog of
  loadTensorStorageMapped on StreamingShardedSafeTensorsReader.
- README: bump Quickstart coordinates to 0.22.1.

Patch release motivated by SKaiNET-transformers' Gemma 4 PLE loader,
which currently rolls its own FileChannel.map to mmap the 4.7 GB BF16
embed_tokens_per_layer tensor (over the 2 GB JVM ByteArray cap).
Once 0.22.1 is published to Maven, that downstream consumer can drop
the JVM mmap glue and consume the upstream TensorStorage directly.

No other behavioural changes vs 0.22.0; this is a single-PR follow-up
release that ships the API surface that should have made the 0.22.0
window but landed after the release branch was cut.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@michalharakal michalharakal merged commit 62cf5ce into develop Apr 30, 2026
12 checks passed
@michalharakal michalharakal deleted the release/0.22.1 branch April 30, 2026 21:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant