Release 0.37.0#881
Merged
Merged
Conversation
Bump version 0.36.0 -> 0.37.0 (gradle.properties, docs/antora.yml, README quickstart). Promote CHANGELOG [Unreleased] to [0.37.0]: Lstm layer (#824), real Dropout masking (#867), LR schedules and mutable optimizer lr (#866), optional-bias and open Linear (#870, #875), androidNative IO targets (#836, #842, #845), the SDPA default-scale fix (#880), three autograd fixes (#877), the argMax DAG output spec (#878), tokenizer BPE inference and N-D gather (#879), plus the CI/docs supply-chain hardening and toolchain bumps. Refresh README "What's New" and add a Contributors (0.37.0) section. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
The @jvmoverloads set change is source- and binary-incompatible for Java callers of the 4-arg (in, out, weights, bias) overload; flag it with the BREAKING lead-in used elsewhere in the changelog instead of a trailing note. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
|
📖 Documentation Preview The documentation has been built successfully for this PR. Generated Files:
Artifacts:
This comment will be updated automatically when the PR is updated. |
aharakal
approved these changes
Jul 25, 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 preparation for 0.37.0. No functional changes — version bump, changelog, and docs only.
Version bumps
gradle.properties—VERSION_NAME=0.37.0docs/antora.yml—skainet_version: 0.37.0(all.adocdependency snippets resolve this attribute, so they follow automatically)README.md— quickstart BOM coordinateVerified no stale
0.36.0references remain outside intentional history sections.CHANGELOG
[Unreleased]promoted to[0.37.0], covering everything since the 0.36.0 prep commit:Added —
Lstmlayer withLstmState/step()(#824), LR schedules and mutable optimizerlr(#866), optional bias inLinear(#870),open Linearfor adapters (#875), androidNative IO targets (#836, #842, #845), OpenSSF Scorecard workflow (#814)Changed —
Dropoutnow performs real inverted dropout (#867), toolchain bumps (Kotlin 2.4.10, AGP 9.3.1, and others), commit-hash pinning across all workflows plus a reproducible docs Docker image,allTestssplit into parallel per-target jobs (#854)Fixed — SDPA default scale (#860), three autograd bugs (#862, #863, #864),
argMaxDAG output spec (#876), legacy tokenizer BPE inference (#858), N-Dgather(#859)Reviewer notes
Two changes are behaviorally breaking and worth a second look:
Linear@JvmOverloadsset (feat(nn): optional bias in Linear #870) — marked BREAKING in the changelog. The 4-arg(in, out, weights, bias)overload is replaced by(in, out, weights), so Java callers binding the 4-arg form break at both source and binary level. Kotlin callers are unaffected.Dropout(feat(nn): implement stochastic masking in Dropout #867) — previously an identity no-op in both phases. Models that relied on that will now see different (correct) training-time activations.Release process
CI does not run on
release/*branches, so this PR is the only validation signal before publishing. Once it is green:0.37.0on the release-branch tip — this triggerspublish.ymland deploys to Maven Central. Not reversible; a botched release needs 0.37.1.