Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

reverts vscode type upgrade to restore version compatibility #894

Merged
merged 1 commit into from
Oct 31, 2023
Merged

reverts vscode type upgrade to restore version compatibility #894

merged 1 commit into from
Oct 31, 2023

Conversation

bockstaller
Copy link
Contributor

the automatic upgrade bumped the @types/vscode and "engines": {"vscode": "^1.63.1"} which removed all backwards compatibility
this change can be savely reverted as this extension doesn't use any newly introduced vscode interfaces

the automatic upgrade bumped the `@types/vscode` and
`"engines": {"vscode": "^1.63.1"}` which removed all backwards
compatibility
this change can be savely reverted as this extension doesn't
use any newly introduced vscode interfaces

Signed-off-by: Lukas Bockstaller <[email protected]>
@chadlwilson
Copy link
Contributor

What do you mean by “the automatic upgrade”?

@chadlwilson chadlwilson merged commit efbfb47 into getgauge:master Oct 31, 2023
4 checks passed
@bockstaller
Copy link
Contributor Author

I used https://www.npmjs.com/package/npm-check-updates to update the dependencies, which bumped the vscode types.

@chadlwilson
Copy link
Contributor

Ok, sure. Another reason to keep a ~ on the types, if they are important in this way (and not semver compliant).

I imagine it doesn’t touch the engines definition though which is presumably the one which eventually makes it into the VSIX as defining compatibility (although I haven’t looked in depth and not super familiar with vscode extensions) so assume you manually changed that?

@bockstaller
Copy link
Contributor Author

Yeah, I am afraid I did upgrade the engine version manually in response to the build error message.

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

Successfully merging this pull request may close these issues.

2 participants