Replace "alygin.vscode-tlaplus" and "alygin.vscode-tlaplus-nightly" on VSCode Marketplace with TLA+ Foundation owned publisher

[lemmy]

We've decided to deprecate alygin.vscode-tlaplus and alygin.vscode-tlaplus-nightly in favor of the TLA+ Foundation controlled tlaplus.vscode-ide.

The released version of this extension, found at alygin.vscode-tlaplus, is severely outdated (last update was in 2021). I suggest to replace the released version with the "nightly build" version, available at alygin.vscode-tlaplus-nightly. In other words, I propose to discontinue the "released" version of the extension and instead, updating the main "alygin.vscode-tlaplus" extension with the content from "alygin.vscode-tlaplus-nightly". This will ensure that users have access to the most recent version of the extension. It also addresses the issue that users can install both the "released" and "nightly" versions concurrently, and run into issues due to conflicts between the two versions. By merging them into one, this problem would be resolved.

Thoughts? @kape1395 @afonsonf @alygin @klinvill @ALL...

[lemmy]

I've created a new VSCode marketplace publisher that's "owned" by the TLA+ Foundation: https://marketplace.visualstudio.com/items?itemName=tlaplus.vscode-ide

@kape1395 @FedericoPonzi Please share your Microsoft account to be added as owners of the marketplace publisher.

[lemmy]

• Deprecate old extensions: Deprecated extensions microsoft/vscode-discussions#1
  Requested: Deprecated extensions microsoft/vscode-discussions#1 (comment)
• Consider renaming tlaplus-lang publisher name to tlaplus (once ADO tlaplus name is freed)

Important links

• https://marketplace.visualstudio.com/manage/publishers/tlaplus
• https://dev.azure.com/tlaplus
• https://marketplace.visualstudio.com/items?itemName=tlaplus.vscode-ide

[kape1395]

@lemmy, my account Karolis Petrauskas (k.petrauskas@gmail.com) User Id : 336ed76d-ac43-6c31-9b7e-079e407795b1

[lemmy]

@lemmy, my account Karolis Petrauskas (k.petrauskas@gmail.com) User Id : 336ed76d-ac43-6c31-9b7e-079e407795b1

You have been added as an owner of the extension at https://marketplace.visualstudio.com/manage/publishers/tlaplus. You and I are able to add additional users.

[lemmy]

@afonsonf What's your vscode marketplace id?

[afonsonf]

@afonsonf What's your vscode marketplace id?

Hi, my id is 35e6c390-a822-6fb6-8871-861e28fbe73f

[lemmy]

Old extensions have been deprecated:

[filiptronicek]

Hi @lemmy, would it, as a part of this change, be possible to publish the extension under the new namespace under https://open-vsx.org/ as well? For context, I'm trying to also mark the extension as deprecated on Open VSX, but the replacement, tlaplus.vscode-ide is not yet available.

[lemmy]

Done: https://open-vsx.org/extension/tlaplus/vscode-ide

[filiptronicek]

Thanks for the superfast turnaround!

[lemmy]

@filiptronicek Would you happen to know what breaks our OVSX publishing: https://github.com/tlaplus/vscode-tlaplus/actions/runs/11185435522/job/31098301346 ?

[filiptronicek]

@lemmy it looks like you're trying to override version 1.7.0. If you bump the version in your package.json, publishing should work.

[lemmy]

I see, we don't have to do that with the VSCode marketplace because vsce publish accepts a version number:

vscode-tlaplus/.github/workflows/release.yml

Line 62 in 250ef51

vsce publish $(git log -1 --format=%cd --date="format:%Y.%-m.%-d%H%M") --pat "${{ secrets.VSCODE_MARKETPLACE_TLAPLUS_TOKEN }}"

Is there a reason why ovsx publish doesn't accept a version number?

[filiptronicek]

@lemmy interesting find, ovsx has a positional argument too, but it accepts a .vsix pathname instead of a version. Given the fact that ovsx is a wrapper around an internal vsce, there are some differences in arguments and flags. Feel free to raise an issue in https://github.com/eclipse/openvsx if you have suggestions regarding this.