Regular Release v1.110.0 Checklist #765
Comments
confused-Techie
changed the title
|
Cirrus binaries are currently being built for this tag over on Cirrus. |
|
Blurb text below. As ever is silly o'clock in the morning for me so the tag line is just what my brain decided was vaguely funny and appropriate. As ever feel free to edit any and all of the below for the actual release. Armed with a big ol' can of Raid: Pulsar 1.110.0 is available now!Here we are with another Pulsar release, and this month we have quite a number of fixes and improvements. This time around, the focus has really been on bug fixes in order to improve the overall experience. Starting with changes to PPM (Pulsar Package Manager), it has been updated to use a newer version of On the topic of PPM, the decaffeination (conversion of CoffeeScript to JavaScript) has now been completed thanks to community members @nemokosch/@twocolours & @GuilleW. In the last release, we announced this had been completed in the core editor and packages; now this has been extended to PPM! Onto Pulsar itself: we have a few new features that have been added. The first is a new autocomplete API that works on ranges rather than the previous prefix system, which will improve LSP support. (And on the topic of autocomplete, if anyone had been editing EJS files and noticed errors popping up, these have now been greatly reduced in this update). Onto the fixes. This first one solves an issue where, if you attempted to start Pulsar with an invalid configuration file, then it would silently fail but still present a running process. Error checking has now been added so that the error can actually be exposed to the user. Next, we have a problem introduced with our And lastly, we had a problem with macOS binary signing in version '1.109.0'; this was already covered in the last community update, and now this fix applies to our regular releases. And that just about covers things for this release. We hope you have enjoyed reading this and continue to enjoy using Pulsar. As ever, a huge thank you to our generous donors and community, without whom this project would not be possible. Until next time, happy coding, and see you amongst the stars! - The Pulsar Team short version (discord compatible)Here we are with another Pulsar release, and this month we have quite a number of fixes and improvements. This time around, the focus has really been on bug fixes in order to improve the overall experience. Starting with changes to PPM (Pulsar Package Manager), it has been updated to use a newer version of node-gyp (a tool for compiling native modules for node.js), which will allow use of newer C/C++ compiler toolchains as well as newer versions of Python. For Windows users, it also now supports Visual Studio 2022! On the topic of PPM, the decaffeination (CoffeeScript -> JavaScript) has now been completed thanks to community members Onto Pulsar itself. The first is a new autocomplete API that works on ranges rather than the previous prefix system, which will improve LSP support for this package. (And on the topic of autocomplete, if anyone had been editing EJS files and noticed errors popping up, these have now been greatly reduced in this update). Onto the fixes. This first one solves an issue where, if you attempted to start Pulsar with an invalid configuration file, then it would silently fail but still present a running process. Error checking has now been added so that the error can actually be exposed to the user. Next, we have a problem introduced with our snippets package update, which now includes variables indicated by a $, which is also used by PHP, so some escaping of these characters needed to be added. And lastly, we had a problem with macOS binary signing in version '1.109.0'; this was already covered in the last community update, and now this fix applies to our regular releases. And that just about covers things for this release. As ever, a huge thank you to our generous donors and community, without whom this project would not be possible. https://github.com/pulsar-edit/pulsar/releases/tag/v1.110.0 short short version (for rootin' and tootin')Here we are with another Pulsar release, and this month we have quite a number of fixes and improvements. This time the focus has really been on bug fixes in order to improve the overall experience. We have updates to PPM for newer toolchain compatibility, a new Autocomplete API, better error handling for a crash at launch with invalid config and a fix for PHP snippets. |
|
Thanks! I've updated the discord short one (remembered markdown links dont work anyway so removed them in favour of just bolding them so it didn't go overlength). |
|
With the release published I've done the Discord announcement, Reddit post, Lemmy post (I thought I added this to the checklist...) and Mastodon toot. |
|
I've created the chocolately repo issue out of curiosity (pulsar-edit/pulsar-chocolatey#24) but realised I don't have permissions to add the release tag so can't progress from there. |
|
@Daeraxa I've gone ahead and added the tag needed to get Chocolatey going and will keep an eye on it from here. But thanks for getting all the announcements done! |
|
New chocolatey version has been published! |
|
Website links and blog post up - pulsar-edit/pulsar-edit.github.io#246 |
|
Looks like everything here is covered. |
Have you checked for existing feature requests?
Summary
Regular Release
CHANGELOG.mdandwelcomepackage)What benefits does this feature provide?
n/a
Any alternatives?
n/a
Other examples:
No response
The text was updated successfully, but these errors were encountered: