ci: derive lsp vscode version from release tag

[guibeira]

Summary by CodeRabbit

• Chores
  • Enhanced release workflow to synchronize and validate package version consistency during extension packaging, ensuring version integrity throughout the release process.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 096de0e8-1a95-4d02-8122-fb8ac93cb256

📥 Commits

Reviewing files that changed from the base of the PR and between 5945719 and 145c474.

📒 Files selected for processing (1)

• .github/workflows/release-lsp.yml

---

📝 Walkthrough

Walkthrough

A new validation step was added to the release workflow that synchronizes the extension's package.json version with the release tag output, using npm to update the manifest version and validating that it matches the expected release version before proceeding with VSIX packaging.

Changes

Cohort / File(s)	Summary
CI/CD Release Workflow .github/workflows/release-lsp.yml	Added a packaging step to synchronize package.json version with the workflow's release tag output via npm version --no-git-tag-version --allow-same-version, with validation to ensure the updated version matches the expected release version and failure handling if versions diverge.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

Possibly related PRs

• ci: rename release-vscode to release-lsp, remove binary workflow #21: Modifies the same release workflow and VSIX packaging job, making it directly related to the version-sync validation step being added in this PR.

Poem

🐰 A version to sync, both left and right,
The package.json shines so bright,
With npm's touch and validation's care,
Release workflows dance through the air! ✨

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly describes the main change: deriving the LSP VSCode extension version from the release tag in CI, which is exactly what the workflow step accomplishes by syncing package.json version with the release tag output.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix-bump-version-lsp

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}