Skip to content

Pin vsce version used in release script#5704

Merged
captainsafia merged 1 commit intomainfrom
safia/pin-vsce
Nov 7, 2021
Merged

Pin vsce version used in release script#5704
captainsafia merged 1 commit intomainfrom
safia/pin-vsce

Conversation

@captainsafia
Copy link
Copy Markdown
Contributor

Attempting to resolve recent issues with this build step by pinning the vsce version used to a known value.

@captainsafia captainsafia requested a review from a team as a code owner November 5, 2021 23:17
Copy link
Copy Markdown
Contributor

@ryanbrandenburg ryanbrandenburg left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sounds good to me if it fixes it!

@ryanbrandenburg
Copy link
Copy Markdown
Contributor

I suspect the specific behavior pinning protects us from is microsoft/vscode-vsce#628. Another project ran into a similar problem. If the License file IS the issue would it be possible for us to include one in future releases?

@captainsafia
Copy link
Copy Markdown
Contributor Author

I suspect the specific behavior pinning protects us from is microsoft/vscode-vsce#628. Another project ran into a similar problem. If the License file IS the issue would it be possible for us to include one in future releases?

Yep. I suppose we can use the MIT license as is done repo-wide.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

2 participants