chore: release 2.0.0#33
Merged
Merged
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
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.
Release prep for v2.0.0 (final). Closes #32.
Promotes
v2.0.0-beta.1to final and picks up the released apex-parser 5.1.0 (test/dev-only dependency).Changes
2.0.0-beta.1→## 2.0.0 - 2026-07-03; the twoapex-parser 5.1.0-beta.1mentions updated to5.1.0.5.1.0-beta.1 → 5.1.0:build.sbt(JVMTestscope),js/npm/package.json(^5.1.0), and regeneratedjs/npm/package-lock.json.apex-parser is test/dev-only here, so this doesn't change the published outline-parser artifacts — only the test toolchain.
Validation (matches CI Build.yml)
sbt scalafmtCheck→ successsbt build→ success (JS + JVM)SAMPLES=apex-samples@v1.4.0 sbt test→ 6314 tests passed, 0 failedRelease gate
apex-ls already pins
outline-parser 2.0.0-beta.1(build.sbt), so downstream integration is validated — 2.0.0 final is unblocked per the release-coordination plan.After merge
Create GitHub Release
v2.0.0(non-prerelease) → triggersPublishMaven.yml(sbt ci-release) publishing2.0.0to Maven Central (JS + JVM). Then follow-up onmainif a next dev version is wanted.