This repository has been archived by the owner on Aug 31, 2023. It is now read-only.
chore(ci): split the release workflow between the vscode extension and CLI package #2495
Conversation
This file contains 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
ematipico
approved these changes
Apr 26, 2022
leops
force-pushed
the
chore/split-release-workflow
branch
from
612667d
to
7f2a142
Compare
Deploying with
|
| Latest commit: |
2b66e0e
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://449db553.tools-8rn.pages.dev |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Summary
This change allows the VSCode Extension to be versioned independently from the npm wrapper package for the CLI. The releases are still triggered by a change to
editors/vscode/package.jsonfor the extension (andnpm/rome/package.jsonfor the CLI), and will be published indepently to either the Visual Studio Marketplace or npm, along with creating a GitHub Release tagged withlsp/vx.y.zfor the LSP andcli/vx.y.zfor the CLITest Plan
Once we've merged in everything we want to include in the
0.5.0release I'll edit this PR to also bump the version number of the packages, and dispatch the workflow manually a few times until I get it to work