Skip to content

Prepare Sprig v0.8.0-beta.1 - #230

Merged
ColinHouse merged 3 commits into
mainfrom
release/v0.8.0-beta.1
Oct 8, 2026
Merged

ColinHouse merged 3 commits into
mainfrom
release/v0.8.0-beta.1

Conversation

@ColinHouse

Copy link
Copy Markdown
Owner

Preparation PR for the v0.8.0-beta.1 release, following docs/releases/release-policy.md step 2. #228 (book and audit) and #229 (editor assistance) are already on main, 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.1 and releaseStatus=development; based on v0.8.0-beta.1; latest published v0.7.1-beta.1 in catalog.properties.
  • Current documentation headings, libraries/README.md, tests/agent_tooling/check_tooling.py, website/package.json and its lock, and the fourteen tracked locks (scripts/refresh-locks.py).
  • docs/releases/v0.8.0-beta.1.md finalized: 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.
  • VS Code extension 0.3.1: the package, lock, README, changelog and both editor guides ship the extension that registers the new providers (the compiler side is Add signature help, semantic tokens and reference limit warnings #229, already on main).

Evidence on this branch

  • ./scripts/verify.sh: build, full scripts/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-build then python3 scripts/check-sdk-archive.py: sprig-v0.8.0-beta.1-jdk.zip passes offline help/api/doctor/check/run/probe/init/resolve/project and the showcases; SHA-256 0d3882503a5254585626ec1e11bac3f8f69f81ba01aa58328a376ec062abebaf.
  • python3 tests/fabric/check_template.py: passed.
  • documented outputs: 761 checked, 0 differ; 503 snippet oracles; sprig version reports sprig-compiler 0.8.0-beta.1.

Tag plan (owner step)

  1. Merge this PR with required CI green.
  2. Tag preflight in a clean checkout of the merge commit: SPRIG_PACKAGE_VERSION=v0.8.0-beta.1 python3 scripts/package-alpha.py plus check-sdk-archive.py --archive; the build must report releaseStatus prerelease; v0.8.0-beta.1.
  3. 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.
  4. Post-release PR: validation.md records 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.

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.
@ColinHouse
ColinHouse merged commit 1352632 into main Oct 8, 2026
14 checks passed
@ColinHouse
ColinHouse deleted the release/v0.8.0-beta.1 branch October 8, 2026 15:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant