Provide new workflow to package .vsix #98
Merged
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.
I was noticing that the .vsix generated for release using
vsce package
is very dependent on the individual user's environment so I wanted to provide a way to make this more reproducible in CI.The workflow is triggered when a new tag is pushed, a test tag run can be seen here after I pushed the
0.3.1-beta1
tag: https://github.com/splunk/vscode-extension-splunk/actions/runs/5571074169Under the job summary a zip file containing the generated .vsix can be seen at the bottom of the page under Artifacts:
Two other fixes that were made
overrides
section to account for peer dependencies using older incompatible versions ofreact
,react-dom
andstyled-components
, these changes match the0.3.0
release so there shouldn't be any actual dependency changes here 🤞