Repository navigation
release: 0.60.0 - #495
Merged
Merged
release: 0.60.0#495
Conversation
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.60.0 against engine 0.59.0, the same sequence as 0.59.0 (#491):
docs(changelog): 0.60.0 entry— the Unreleased block from feat(laya): exact GELU through the engine op on SKaiNET 0.59.0 #494 becomes[0.60.0] — 2026-10-15with a headline and a Deprecated note.docs(readme): 0.60.0 highlights and BOM coordinatedocs: bump version references to 0.60.0— BOM coordinates on seven pages, the Maven<version>in the Java tutorial, and the schedule paragraph in the tokenizer reference.release: prepare 0.60.0 -- against engine 0.59.0—gradle.properties.Contents since 0.59.0: #494 (engine 0.59.0, Laya's exact GELU through
gelu(approximate = false)).Deprecation note: 0.59.0 scheduled the SKEEP-006 legacy tokenizer surface for ERROR in 0.60. It stays at WARNING here and the schedule moves one more minor (ERROR in 0.61, removed in 0.62;
TokenizerFactoryand the sub-interface deprecated in 0.61, removed in 0.62). About thirty main-source files in the runtimes, CLIs and benchmarks still go through the factory, so that migration is a release of its own. The changelog, README and tokenizer reference say so.Test plan
workflow_dispatchonrelease/0.60.0) green before tagging0.60.0, tag-triggered publish,mainfast-forwarded, Central resolvessk.ainet.transformers:skainet-transformers-bom:0.60.0