Publish new version to VSCode marketplace

[EggBaconAndSpam]

The current version is somewhat out of date and doesn't support e.g. annotating let binders.

For the future, is there a way to automate this in some way? Maybe as part of the dhall-haskell (which includes dhall-lsp-server) release cycle?

[PanAeon]

@EggBaconAndSpam Sorry, it's my fault that I didn't do release for so long. I think the good way to automate the release would do something like in https://github.com/scala/vscode-scala-syntax.

The whole idea is that anyone with the write access to repository can do the release. To do the release a maintainer just need to push a git tag with the release version, then CircleCI will build and publish the extension to the marketplace. The security token that needs for the publishing can be stored securely in the CircleCI environmental variables.

If you don't mind, I think I'll take a few days to experiment with the CircleCI. If anything I can quite easily release your changes by hand.

[EggBaconAndSpam]

If you don't mind, I think I'll take a few days to experiment with the CircleCI. If anything I can quite easily release your changes by hand.

Sounds great, thanks!

[EggBaconAndSpam]

@PanAeon any progress on this?

[PanAeon]

@EggBaconAndSpam
Hey, sorry for the delay. I've just published a new version. Now I'm investigating publishing via TravisCI so all contributors with write access could do it.

[EggBaconAndSpam]

Thank you!

[gregziegan]

👋 we want to use the asciiOnly feature available after 0.4. Anything I can do to help create and publish a release?

[PanAeon]

@thebritican, the asciiOnly option is in the server config, so I think it should work without any client modification (although I haven't tried yet).
As for publishing if you are willing to help maintain this project I can give you publisher rights, as I'm not using dhall at the moment, and don't follow the project development closely. The process itself is just two commands, but we have to manually verify that everything works before publishing.

[sjakobi]

@thebritican Are you still interested in helping maintain this extension?

If so, it would be great if your permissions could be arranged.

(CC @PanAeon, @Gabriel439, @basile-henry)