Luke Arms

> Well, if you are on the main branch, it is totally expected to guess the version as being `dev-main`, i.e. the version corresponding to the `main` branch. That makes...

Thanks for your feedback so far, @stof and @Seldaek. I really appreciate it! > I would say you could use the COMPOSER_ROOT_VERSION env var to set the root package's version...

> Which build time are you talking about ? Apologies for the slow reply. In this case, the build time I'm talking about is "when generating an executable phar for...

Sorry, I'm just getting back into this now. Apologies for taking so long to respond (again). I've experimented with Box, which does indeed offer a solution of sorts, as long...

I'm not sure if the highlighting is an Intelephense issue or a VSCode issue, because mouseovers indicate Intelephense is parsing the tags correctly:  But I was just about to...

I've been having a similar issue with build 2092. It's infrequent enough that I can't replicate it consistently, but when it happens, Sublime Merge doesn't even respond to Force Quit--`ps`...

> @lkrms yep, but you have to switch to a dev branch upfront. It could be done by downloading dev build from the official site (can't provide a link since...

I've also observed this behaviour on macOS, consistently since I can remember, although changing to a different commit and back again isn't enough to restore the labels for me. Saving...