chore: Publish v1.3.17

[kdy1]

No description provided.

[kdy1]

swc-bump:

• dbg-swc

[kdy1]

cc @kwonoj I reverted 1dd8b3d as it broke wasm

[kwonoj]

@kdy1 can I see Ci logs to fix it forward?

[kdy1]

https://github.com/swc-project/swc/actions/runs/3467260819/jobs/5791963901

[kdy1]

Oh revert was not enough

[kwonoj]

Let bindings use published version of swc_core serves well, but we definitely need some way to test latest swc_core directly before publishing bindings :/ I'll file an issue and think about some way.

[kdy1]

It does not work. With the latest version wasm CI fails

[kdy1]

See https://github.com/swc-project/swc/actions/runs/3467460473/jobs/5792360658
It's using binding_macros@ v0.20.94

[kwonoj]

It does not work. With the latest version wasm CI fails

Do you mean previous version of swc_core, or one more bump of swc_core with revert? if it's reverted + swc_core has been bumped up and still same compilation error occurs?

[kdy1]

No, it's not reverted yet and the broken version (with #6436) is the latest version at the moment

[kwonoj]

I see.

What I meant

Let bindings use published version of swc_core serves well,

was not for this specific case, it's for more general cases (aka when it works, it works well). As said above, seems we're hitting bumps bit more than we expected - I'll try to see if I can come up with some plan.

[swc-bot]

Automated review comment generated by auto-rebase script