Repository navigation
Prepare Sprig v0.8.0-beta.1 - #230
Merged
Merged
Conversation
A new MINOR: JDK 21, the language additions and the incompatible numeric spelling changes. compilerVersion and the development releaseStatus name 0.8.0-beta.1 with v0.7.1-beta.1 as the latest published; the current documentation headings, the libraries README, the tooling expectation, website/package.json and its lock and the fourteen tracked locks follow. The release notes lose their draft banner, gain the tutorial rewrite and the documentation audit in the tooling section, and are the body the release workflow publishes.
The compiler's signature help and semantic tokens are new in 0.8.0-beta.1; the extension that registers them ships as 0.3.1 (package, lock, README, changelog and both editor guides), so the VSIX built for the release is sprig-language-0.3.1.vsix.
The notes are copied into the SDK archive root, where the relative v0.7.1/release-policy/known-limitations paths do not exist; absolute GitHub links work in the GitHub release body and in the archive.
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.
Preparation PR for the v0.8.0-beta.1 release, following
docs/releases/release-policy.mdstep 2. #228 (book and audit) and #229 (editor assistance) are already onmain, so this branch is only the release preparation on top.Version decision
A new MINOR: the release requires JDK 21 and rejects or changes programs the previous release accepted (numeric conversion spellings, narrowing in
elif/else, non-nullable Java results, and the soundness/behavior fixes in the notes). The stage stays beta and N resets: 0.7.1-beta.1 → 0.8.0-beta.1. The language version stays 0.8-dev (the 0.8 language is still open).Preparation changes
compilerVersion=0.8.0-beta.1andreleaseStatus=development; based on v0.8.0-beta.1; latest published v0.7.1-beta.1incatalog.properties.libraries/README.md,tests/agent_tooling/check_tooling.py,website/package.jsonand its lock, and the fourteen tracked locks (scripts/refresh-locks.py).docs/releases/v0.8.0-beta.1.mdfinalized: the draft banner is gone, the tooling section names the tutorial rewrite, the documentation audit and the language server's signature help, semantic tokens and reference-limit warning; the cross-release links are absolute so the packaged archive's link check passes; this file is the body the release workflow publishes.main).Evidence on this branch
./scripts/verify.sh: build, fullscripts/test.py(187 gates/cases, 0 failed), grammar, documented snippets, VitePress and links, editor CLI/JVM and VSIX all pass.python3 scripts/package-alpha.py --skip-buildthenpython3 scripts/check-sdk-archive.py:sprig-v0.8.0-beta.1-jdk.zippasses offline help/api/doctor/check/run/probe/init/resolve/project and the showcases; SHA-2560d3882503a5254585626ec1e11bac3f8f69f81ba01aa58328a376ec062abebaf.python3 tests/fabric/check_template.py: passed.documented outputs: 761 checked, 0 differ; 503 snippet oracles;sprig versionreportssprig-compiler 0.8.0-beta.1.Tag plan (owner step)
SPRIG_PACKAGE_VERSION=v0.8.0-beta.1 python3 scripts/package-alpha.pypluscheck-sdk-archive.py --archive; the build must reportreleaseStatusprerelease; v0.8.0-beta.1.git tag -a v0.8.0-beta.1 -m "Sprig v0.8.0-beta.1"and push the tag; the release workflow builds, smoke-tests on Linux/macOS JDK 21/26 and publishes the prerelease.validation.mdrecords the published release and the latest-published references move.Nothing here publishes or tags; the publication decision and the tag are the owner's.
AI assistance
Prepared with an AI coding agent (DeepSeek Flash via opencode) from the release policy; the agent ran the preparation gates and packaged the archive.