You should create a release of 0.3.x with the fix for #71
StephenWeatherford opened this issue · 2 comments
Since #71 is present in your most recent recent of 0.3.x, any package with dependence of the form
"vscode-extension-telemetry": "^0.3.0"
will pick up 0.3.2 and hence the bug, and it won't pick up the fix that occurred in 0.4.3
This hit me in the https://github.com/azure/bicep repo through a subdependency on another package (https://github.com/microsoft/vscode-azuretools/blob/main/ui/package.json). Thx.
Luckily our test suites discovered this (on the build machines only)
It would be a bit weird to publish 0.4.3 also as 0.3.x. I think the ideal situation here is to just update the dependency in the package.json of the product. There was also a ES6 -> ES2020 target change in 0.4.1 that I don't want to pull into 0.3.x