search

pulsar-edit / pulsar

A Community-led Hyper-Hackable Text Editor
https://pulsar-edit.dev
Other
3.33k stars 140 forks source link

Release Checklist for Pulsar 1.116.0 #975

Open DeeDeeG opened 7 months ago

DeeDeeG commented 7 months ago

Regular Release 1.116.0

confused-Techie commented 7 months ago

For the blurbening:

# Pulsar 1.116.0 Ready for all the Code Ninjas out there
Like the past few months this Pulsar release is full of Tree-sitter improvements and fixes! From TypeScript and Python getting improved syntax highlighting all around, to big changes like replacing the underlying Markdown Tree-sitter parser, Pulsar 1.116 is sure to make these grammars more stable and aesthetically pleasing.

But onto some of the really exciting stuff this month, we have a flurry of new features and updates to `snippets`, which is sure to make otherwise repetitive coding exciting and high-tech! For anyone familiar with the super secret code ninja techniques of `snippets` there's now support for new snippet variables and support for some new transformation flags. Be sure to read the full changelog to get caught up on all of these changes.

Lastly, as always this release has some bug fixes and house-keeping to do. Linux folks will appreciate improved metadata for their installs, meanwhile Windows folks will be happy to see adding Pulsar to the PATH is easier than ever regardless if Pulsar is installed per user or per machine.

That's just about everything this time around, we can't wait to see what people do with these powerful new `snippets` features and look forward to the next one!

Until next time, happy coding, and see you amongst the stars!
- The Pulsar Team
savetheclocktower commented 7 months ago

Suggested edits — I might take a second pass at this, but don't wait up if you're ready to publish:

# Pulsar 1.116.0: Ready for all the code ninjas out there

Like the past few releases, this Pulsar release is full of Tree-sitter improvements and fixes! From TypeScript and Python getting improved syntax highlighting all around, to big changes like replacing the underlying Markdown Tree-sitter parser, Pulsar 1.116 is sure to make these grammars more stable and aesthetically pleasing.

But on to some of the really exciting stuff this month: we have a flurry of new features and updates to `snippets`, which is sure to make otherwise repetitive coding exciting and high-tech!

For anyone familiar with the super secret code ninja techniques of `snippets`, there's now support for new snippet variables and transformation flags. Be sure to read the full changelog to get caught up on all of these changes.

As always, this release has some bug fixes and housekeeping. Linux folks will appreciate improved metadata for their installs, whereas Windows folks will be happy to see that adding Pulsar to the PATH is easier than ever whether Pulsar is installed for just one user or for all users.

That's just about everything this time around. We can't wait to see what people do with these powerful new `snippets` features and look forward to the next one!

Until next time, happy coding, and see you amongst the stars!
- The Pulsar Team
DeeDeeG commented 7 months ago

Another suggestion:

installed for just one user or for all users.

-->

installed for just one user or system-wide.

To avoid potential ambiguity in the technical distinction.

Release is posted, by the way! 🎉

DeeDeeG commented 7 months ago

For posterity, I want to mention something I ran into when publishing to Chocolatey:

The first run of the pulsar-chocolatey publishing workflow (<-- see link for details) did not work, and showed a message like this on Chocolatey's side:

pulsar has failed automated validation. [ . . . ] We were unable to find a package, and are unable to continue validation. Please try uploading the package again. If you encounter this message again, please contact the Site Administrators.

Since it asked us to try uploading the package again, I ran the final publishing step (as described in pulsar-chocolatey's README.md) a second time:

  1. With the PR now merged to main go ahead and trigger the GitHub Action auto_publish. This Action should run and if successful will publish a new version of Pulsar to Chocolatey.

This second time, running that GitHub Actions workflow auto_publish (AKA "Chocolatey Publish Pulsar Package") again at pulsar-edit/pulsar-chocolatey repo, appears to have had no problem, and the v1.116.0 version is now live at Chocolatey and has several downloads already.

So, in case anyone is wondering what to do in this situation, I can suggest to read the message carefully on the Chocolatey.org page for the specific version of Pulsar you are trying to publish (such as: https://community.chocolatey.org/packages/pulsar/1.116.0). And if the situation is just like the one I'm writing about now, the answer is to indeed try publishing the same version again, for a second time.

It worked out in the end.