Closed DeeDeeG closed 7 months ago
git log --oneline --graph
output since 1.114.0 currently looks like this (click to expand):That includes the following PR's:
Four CI things to fix Cirrus, a small bugfix in fuzzy-finder package, the big batch of Tree-sitter fixes and some more focused Ruby folding enhancements.
Edit: Hmm, a Changelog PR was already opened, I'm going to update it myself as needed, as I believe @confused-Techie is away for the evening. See: https://github.com/pulsar-edit/pulsar/pull/962
Blurb, based predominantly on the draft provided by @savetheclocktower:
## Better Late than Never, Pulsar 1.115.0 is here!
A week later than you’re accustomed to — but worth the wait! Pulsar 1.115.0 is available now!
Last month’s 1.114.0 release was full of fixes related to the recent migration to modern Tree-sitter. This month’s release is much smaller, but still dominated by Tree-sitter fixes affecting syntax highlighting, code folding, and indentation.
The most visible fixes are related to your ability to customize the grammar that Pulsar uses on a per-language basis. This is an approach we’ve encouraged for users that want or need to revert to an older grammar for a specific language — better to do so on a targeted basis than globally. If you can edit your config file, you can do per-language customization.
For instance, now it’s even easier than before to say “use legacy Tree-sitter, but only for Python”:
\```coffeescript
".python.source":
core:
useLegacyTreeSitter: true
\```
Or “use modern Tree-sitter for JavaScript, but TextMate-style grammars everywhere else”:
\```coffeescript
"*":
core:
useTreeSitterParsers: false
".source.javascript":
core:
useTreeSitterParsers: true
\```
Better yet, now the `grammar-selector` package will be attuned to these choices. When you manually reassign a buffer to use a different grammar, it will offer you only the “correct” grammar for each language based on what you’ve opted into.
We’ve also delivered our customary incremental improvements in language support, and one change that affects nearly all languages: indentation hinting will be more accurate in transactions with multiple buffer changes. The most common example of a multi-edit transaction is when the user places more than one cursor and starts typing.
We’ve made improvements to our `language-ruby` bundle, primarily with code folding and indentation hinting. TypeScript and C/C++ also got some small enhancements, and the `language-shellscript` bundle got a parser update.
And lastly, on another note, we have a few maintenance and upkeep PR's to keep our Cirrus CI active and working, to ensure you can keep using and enjoying the latest builds Pulsar has to offer.
Until next time, happy coding, and see you amongst the stars!
\- The Pulsar team
BUY NITRO: https://discord.com/channels/992103415163396136/992231561724436591/1220946673791143988 BUY SHARES: https://www.reddit.com/r/pulsaredit/comments/1blj60c/better_late_than_never_pulsar_11150_is_here/ BUY BANANAS: https://fosstodon.org/@pulsaredit/112143017529711594 BUY INTO IT (pls): https://lemmy.ml/post/13532552
I got some error message when trying to publish the Chocolatey package:
Attempting to push pulsar.1.115.0.nupkg to https://push.chocolatey.org An error has occurred. It's possible the package version already exists on the repository or a nuspec element is invalid. See error below... Response status code does not indicate success: 409 (Conflict).
At least there's no "pending release" stuck on the Chocolatey.org site side of things, at least that I can see: https://community.chocolatey.org/packages/pulsar#versionhistory
I (or someone with perms to do so) can try tomorrow.
Looks like Chocolatey did successfully publish. Thanks everyone for getting this release out, I'll go ahead and close this issue
Regular Release
CHANGELOG.md
andwelcome
package)