chore: release 5.1.0#131
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
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 v5.1.0. Closes #128.
Changes
Unreleased+5.1.0-beta.1into a single dated## 5.1.0 - 2026-07-03section. The SOQLFORMULA()feature is now recorded as a feature (support inWHERE; syntax error elsewhere) rather than only its restriction, since the feature itself landed after5.1.0-beta.1.5.1.0-beta.1 → 5.1.0injvm/pom.xml,npm/package.json,npm/package-lock.json.Validation (matches CI Build.yml)
npm run init→ ANTLR generation OK,Building apex-parser 5.1.0npm run build→ JVM surefire 92 passed, jest 93 passednpm run systest(apex-samplesv1.4.0) → 100 snapshots passedRelease gate
apex-ls #441 (upgrade apex-parser to 5.1.0) and #443 (multiline-string diagnostic) are both CLOSED/COMPLETED — downstream validation done.
After merge
Create GitHub Release
v5.1.0(non-prerelease) to triggerPublishMaven.yml+PublishNPM.yml(publishes to Maven Central + npmlatest). Then a follow-up commit onmainto bump to the next dev version and record the release date.