chore: release 2.0.0#28
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.
Promote
v2.0.0-beta.1to final 2.0.0, so downstream apex-ls can drop its beta pin.Changes
2.0.0-beta.1 → 2.0.0injvm/pom.xml,npm/package.json,npm/package-lock.json.No dependency changes — vf-parser has no apex-parser dependency (only bundled antlr4). All commits since the beta tag are dependabot/CI chores.
Validation (matches CI Build.yml)
npm run init→ ANTLR generation OK,Building vf-parser 2.0.0npm run build→ JVM surefire 2 passed, jest 2 passedNotes
2.0.0-beta.1(published; apex-ls pins it), so the coherent final version is 2.0.0. Issue #27 should be renamed to match (or closed by this release).After merge
Create GitHub Release
v2.0.0(non-prerelease) → triggersPublishMaven.yml+PublishNPM.yml(Maven Central + npmlatest).