Repository navigation
release: 0.0.9 - #12
Merged
Merged
Conversation
Ships the Slang 2026.16 regeneration from #11. Unlike 0.0.8, this release is Slang's version moving, not slang-java's own API: the bundled binaries go 2026.14.1 -> 2026.16 and PINNED_SLANG_VERSION with them. The only public Java surface that moves is four additive SlangLanguageVersion constants upstream added (202A = 2025, 202B = 2026, 202C = 2027, NEXT = 2027). LATEST still resolves to 2026, so nothing shifts semantically for existing callers. The ABI lock was enforced rather than reset, which is what makes that claim checkable: no locked fact moved. The library and both natives artifacts share one version by design (gradle.properties is the single source), so a consumer's two coordinates always agree; README's coordinates, manifest example and both dependency snippets move to 0.0.9 with it. Verified in CI, not locally: :slang:test ran against the 2026.16 binaries on linux-x86_64, linux-aarch64, macos-aarch64 and windows-x86_64 in the bump run (32815010486), and #11's smoke matrix plus the ABI lock check passed on the same four. windows-aarch64 and macos-x86_64 are published but untested, as they are today. The release workflow re-runs the suite against the pinned binaries before it publishes anything, so the tag is gated too. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Contributor
Qodana for JVMIt seems all right 👌 No new problems were found according to the checks applied 💡 Qodana analysis was run in the pull request mode: only the changed files were checked View the detailed Qodana reportTo be able to view the detailed Qodana report, you can either:
To get - name: 'Qodana Scan'
uses: JetBrains/qodana-action@v2026.1.3
with:
upload-result: trueContact Qodana teamContact us at qodana-support@jetbrains.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
1 participant
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.
Cuts
0.0.9, shipping the Slang 2026.16 regeneration from #11.Unlike
0.0.8— which shipped a slang-java API change with the Slang pin held — this release is Slang's version moving, not ours: bundled binaries go2026.14.1→2026.16, andSlangLibrary.PINNED_SLANG_VERSIONwith them.The only public Java surface that moves is four additive
SlangLanguageVersionconstants upstream added (202A= 2025,202B= 2026,202C= 2027,NEXT= 2027).LATESTstill resolves to 2026, so nothing shifts semantically for existing callers. The ABI lock was enforced rather than reset in #11, which is what makes that claim checkable — no locked fact moved.Contents
gradle.properties—version=0.0.8→0.0.9README.md— coordinates, the manifest example and both dependency snippetsThe library and both natives artifacts share one version by design (
gradle.propertiesis the single source), so a consumer's two coordinates always agree.Verification
CI, not local:
:slang:testran against the 2026.16 binaries onlinux-x86_64,linux-aarch64,macos-aarch64andwindows-x86_64in bump run 32815010486, and #11's smoke matrix plus the ABI lock check passed on the same four.windows-aarch64andmacos-x86_64are published but untested, as they are today.Merging this only stages the version. Publishing needs the
v0.0.9tag pushed afterwards — and release.yml refuses to publish if the tag andgradle.propertiesdisagree, so this must land onmainfirst.