New Release anytime soon?

[RunDevelopment]

It has been 4 months and ~60 commits since the last release.
(I screwed up and used Merge commit instead of Squash and merge, so I don't know the exact number.)

With #1835, the changelog can be mostly generated, so I'll make a new branch with the updated changelog in the next few days.

Regarding the open PR. I made a new milestone and add all of the PR I think should definitely be in the new release.

Is there anything else which needs to be prepared?
@mAAdhaTTah @Golmote

[mAAdhaTTah]

Appreciate the housekeeping. I'll take a pass through the labeled PRs with an eye towards cutting a release this weekend.

[mAAdhaTTah]

Oh, we will need a CHANGELOG prepared, if you wanna start getting that together.

[RunDevelopment]

This weekend sounds good.

Oh, we will need a CHANGELOG prepared

I'll do that tomorrow.

[mAAdhaTTah]

I'll take a pass through the new languages as well, but I'll caveat that an approval from me mostly means things seem ok (e.g. has tests, components.json, code is well-formatted, etc.) but none of the regexes will be reviewed cuz I don't have a lot to offer there. After I approve, def take another pass through them before you merge them (which I think you do anyway).

[RunDevelopment]

def take another pass through them

Will do.

[RunDevelopment]

@mAAdhaTTah Do you have administrator rights for this repo?

GitHub keeps forgetting that the last merge method I used was Squash after a few merges and reverts to the default method of merge commits. It's really annoying because I forget to check and unwillingly use the wrong merge method.

Could you please disable all other merge buttons in the settings of this repo? It's the only method we use AFAIK and it would help me more I'd like to admit.

[mAAdhaTTah]

@RunDevelopment I do not. @LeaVerou Is this something you could change?

[mAAdhaTTah]

Publish 1.17.0 then immediately published 1.17.1 to keep my .DS_Store files from being published c2229ec