Skip to content

Update download links and add blog post for Pulsar v1.117.0 #273

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
May 22, 2024

Conversation

DeeDeeG
Copy link
Member

@DeeDeeG DeeDeeG commented May 20, 2024

Note: The blog post content for this Pulsar v1.117.0 release was written by confused-Techie. This is just posting that content here as a new blog post and updating the download links from 1.116.0 to 1.117.0.

Alternative blurb option

Also consider this alternate blurb re-worked by me, I posted this in the Discord and did not receive any outright feedback there, so I went with the existing blurb by @confused-Techie to be safer. But we have this as an option:

As you may have come to expect, this release is full of new improvements for Tree-sitter grammars! From SCSS now having Tree-sitter support, to Ruby getting an updated parser, to performance and highlighting enhancements in Markdown and TypeScript, there's hopefully something in there for everybody. Speaking of Markdown, the markdown-preview package has gotten significant performance increases in the preview pane (especially for documents with lots of fenced code blocks), and boasts brand new dark mode support for the "GitHub.com style" option! But dark mode support doesn't stop there! Pulsar can now (optionally) use the OS's light or dark mode window theming based on the active Pulsar theme. This works with any built-in or community theme based on its color values.

Beyond the fixes and features within the editor itself, you'll be glad to know this release also saw many improvements for our Continuous Integration to ensure we can deliver timely and bug-free updates in the future.

I'd be okay to go over this and receive suggestions/feedback, either here or on Discord, if there is a desire to go over the blog post wording with a finer-toothed comb. But it works as-is too (as @confused-Techie wrote it, which is how it is committed for this PR already). So this ^ text is just an alternate second draft to consider.

The blog post content for this release was written by confused-Techie.

Co-authored-by: confused_techie <[email protected]>
Copy link
Member

@confused-Techie confused-Techie left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Apologies for not providing feedback and your reworked blurb.

I see no issue at all for swapping your work with what's here if you'd like, and the approval with both apply since as I see it both are effective to communicate the details, ones just a bit more refined lol.

Otherwise thanks for getting this PR put together!

@savetheclocktower
Copy link
Contributor

To make the mother of all nitpicks, I'd break this up into paragraphs for ease of skimming…

As you may have come to expect, this release is full of new improvements for Tree-sitter grammars! From SCSS now having Tree-sitter support, to Ruby getting an updated parser, to performance and highlighting enhancements in Markdown and TypeScript, there's hopefully something in there for everybody.

Speaking of Markdown, the markdown-preview package has gotten significant performance increases in the preview pane (especially for documents with lots of fenced code blocks), and boasts brand new dark mode support for the "GitHub.com style" option!

But dark mode support doesn't stop there! Pulsar can now (optionally) use the OS's light or dark mode window theming based on the active Pulsar theme. This works with any built-in or community theme based on its color values.

…but that's just a suggestion.

@DeeDeeG
Copy link
Member Author

DeeDeeG commented May 21, 2024

Yeah, it occurred to me a number of times to break it up, and I didn't feel it had to as the ideas flow into each-other so much, but some part of me was nudging to break it up nonetheless. I think it's a fair suggestion.

@DeeDeeG
Copy link
Member Author

DeeDeeG commented May 21, 2024

@savetheclocktower what do you think about this?:

But dark mode support doesn't stop there! Pulsar can now (optionally) use the OS's light or dark mode window theming based on the active Pulsar theme. This works with any built-in or community theme based on its color values.

-->

But dark mode support doesn't stop there! Pulsar can now (optionally) use the OS-level dark mode window theme, based on the lightness or darkness of the colors in the active Pulsar theme.

Going back to some of the wording that the original had that I think was better. ("OS-level dark mode").

@savetheclocktower
Copy link
Contributor

Either is fine with me.

This edit is partly based on feedback from savetheclocktower.

Co-authored-by: Andrew Dupont <[email protected]>
@DeeDeeG
Copy link
Member Author

DeeDeeG commented May 22, 2024

Tweaked the wording a bit, mostly as discussed above but not 100% exactly.

Ready to merge, I suppose.

Will do so if no objections in the next hour or three.

Copy link
Member

@confused-Techie confused-Techie left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM! Thanks again for getting it put together

@DeeDeeG DeeDeeG merged commit 2518acb into main May 22, 2024
2 checks passed
@DeeDeeG
Copy link
Member Author

DeeDeeG commented May 22, 2024

Okay, with this merged, and CI having done its thing, this Regular release post is now LIVE --> https://pulsar-edit.dev/blog/20240520-confused-Techie-v1.117.0.html

(A little late, but the Release itself was on time!!)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants