Repository navigation
release: 0.61.0 - #497
Merged
Merged
release: 0.61.0#497
Conversation
1 of 7 tasks
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 0.61.0 against engine 0.60.0, the same sequence as 0.60.0 (#495):
docs(changelog): 0.61.0 entry— the Unreleased block from feat(encoders): padded batches with key lengths for BERT and Laya on engine 0.60.0 (#490) #496 becomes[0.61.0] — 2026-10-16with a headline and a Deprecated note.docs(readme): 0.61.0 highlights and BOM coordinatedocs: bump version references to 0.61.0— BOM coordinates on seven pages, the Maven<version>in the Java tutorial, and the schedule paragraph in the tokenizer reference.release: prepare 0.61.0 -- against engine 0.60.0—gradle.properties.Contents since 0.60.0: #496 (engine 0.60.0; padded batches with key lengths for the BERT and Laya encoders, #490).
Deprecation note: 0.60.0 scheduled the SKEEP-006 legacy tokenizer surface for ERROR in 0.61. It stays at WARNING here and the schedule moves one more minor (ERROR in 0.62, removed in 0.63;
TokenizerFactoryand the sub-interface deprecated in 0.62, removed in 0.63). The runtimes, CLIs and benchmarks still go through the factory and this release carries the engine bump and the batched encoders; that migration is still a release of its own. The engine's own io-core aliases are errors since 0.60.0 and the two tests that used one were moved in #496. The changelog, README and tokenizer reference say so.Test plan
apiCheck), CI greenworkflow_dispatchonrelease/0.61.0) green before tagging0.61.0, tag-triggered publish,mainfast-forwarded, Central resolvessk.ainet.transformers:skainet-transformers-bom:0.61.0