Timing of next point release?

[gkz]

Hi, thank you for being such active maintainers of Prettier! PRs get reviewed very quickly.

I was just wondering if there is a timeline for the next point release (2.0.6).

Thanks!

[alexander-akait]

/cc @thorn0 What do you think about new release?

[thorn0]

There is a bunch of things in master that need to be finished before releasing 2.1. If some specific fix urgently needs to be released, we can cherry-pick it into the patch-release branch and release it from there. That's how 2.0.5 was done.

[gkz]

Ah OK, so master is tracking a future 2.1 release rather than a 2.0.6 release, makes sense. I recently had #8768 merged and was just wondering what the approximate time frame would be for it being released. It's not super urgent.

[bakkot]

@thorn0 which things in master need to be finished before releasing 2.1? Is there a reason it can't be released now, so that features like #7875 can go out, and whatever those other things are be pushed to 2.2?

[thorn0]

@bakkot

• Finalize the update of remark: Work after updating markdown parser #8630
• Printing of member chains: Further improve method chain breaking heuristic #7889 has been merged, and I started but didn't finish Avoid line-breaking inside a method chain before breaking the chain itself #8063. I expect that if we release one without the other, there will be a lot of criticism again as it happened after 2.0, but together they might be good enough.

[bakkot]

@thorn0 If those PRs weren't good enough to ship, shouldn't they be backed out and re-landed once they're done? I'd be happy to do that if you'd like.

[thorn0]

@bakkot I'm fine with reverting #7889 but not remark. That update is really long-overdue and fixes too many issues.

[justingrant]

I've been eagerly waiting for #4216 (the fix to #4926) which I'm hoping will fix the issue with VSCode randomly indenting every line in a class method when I paste one line of code into it. If you do end up doing a point release instead of 2.1, it'd be great to see that fix in it.

P.S. - Prettier is wonderful. Thanks so much for maintaining it!

[sosukesuzuki]

/cc @thorn0
We've finished #8630 so I think we can revert #7889 and work for releasing 2.1.

[sosukesuzuki]

@fisker @evilebottnawi @thorn0 What about other todos in 2.1 milestone? Should we postpone implementing them until 2.2? I'm not sure about status.

[alexander-akait]

Agree, we can postpone other changes to 2.2 and do release 2.1 (markdown fixes)

[sosukesuzuki]

Okay I've created PR reverts 7889. And I'll remove other changes from 2.1 milestone.

[alexander-akait]

/cc @thorn0 What do you think?

[sosukesuzuki]

I opened 2.1 checklist issue #8882

[sosukesuzuki]

We've already released 2.1:+1: