Release 0.4.0

[12wrigja]

I think now's a good time to create another release.

I'd like to target a cutoff point within the next week or so, and hopefully #105 can land first? It would be great to have that included.

[12wrigja]

I can drive a release starting sometime late next week.

[justingrant]

hopefully #105 can land first? It would be great to have that included.

Agree. But I wouldn't hold the release for it. If it's ready, that's great. If not, we can pick it up in the next one.

[justingrant]

@12wrigja - how's the release going? 😄 Do you think you'll have time to get it out?

[12wrigja]

I started working on this, but then hit a roadblock and forgot to post an update here.

I was trying to ensure that we had test262 coverage parity with the spec polyfill, and found that when I sync up the test262 repo to 2f592de0 that 62 tests are failing, all of which seem to be year-zero.js tests.

I think it's because we are missing e60ef9eac7a35b67b065f25d6e560a9bf4ba8bd5, and that made me wonder what else we might be missing.

[12wrigja]

My intent is to draft a release cut at 670cda6.

I skimmed over changes to tc39/proposal-temporal and I don't think anything else relevant is missing - most of the other commits seems to been test removals (as they've been ported to test262 - yay!).

[justingrant]

Great! Heads up I'm watching tc39/proposal-temporal#2075, and if it's a bug then it may make sense to fix it before this release. Let's decide tomorrow.

[justingrant]

False alarm. According to tc39/proposal-temporal#2075 (comment) it's not a bug. Release should be good to go!

[justingrant]

Thanks so much @12wrigja for getting the release out the door! Closing.