Ensure js-sources are used only with JavaScript arch

[wismill]

Fixes #8741

---

• Patches conform to the coding conventions.
• Any changes that could be relevant to users have been recorded in the changelog.
• The documentation has been updated, if necessary.

[hsyl20]

LGTM! Thanks!

[wismill]

@hsyl20 I think now I got the test right. But I see no Javascript-capable compiler in the CI to check if they work.

[hsyl20]

@wismill Yeah I've only run the JS test locally too. I don't know if there is a plan to add a JS job in CI (@Mikolaj?). It would require using an unofficial GHC build because bindists won't be distributed with the JS backend enabled.

[Mikolaj]

@wismill Yeah I've only run the JS test locally too. I don't know if there is a plan to add a JS job in CI (@Mikolaj?).

Unfortunately not in the foreseeable future. We are currently unable to add newest 9.4 revisions due to some GHA quirks and getting to 9.6 soon enough after release will already be a big feat, if we make it.

Speaking about CI, please kindly rebase in 2h, after #8749 gets merged and then the CI breakage should be gone.

[Mikolaj]

I haven't cross-checked with the original PR, but the things I see LGTM.

[Mikolaj]

Let me rebase myself.

[Mikolaj]

@mergify rebase

[mergify]

⚠️ This pull request got rebased on behalf of a random user of the organization.
This behavior will change on the 1st February 2023, Mergify will pick the author of the pull request instead.

To get the future behavior now, you can configure bot_account options (e.g.: bot_account: { author } or update_bot_account: { author }.

Or you can create a dedicated github account for squash and rebase operations, and use it in different bot_account options.

[mergify]

rebase

✅ Branch has been successfully rebased

[mergify]

⚠️ This pull request got rebased on behalf of a random user of the organization.
This behavior will change on the 1st February 2023, Mergify will pick the author of the pull request instead.

To get the future behavior now, you can configure bot_account options (e.g.: bot_account: { author } or update_bot_account: { author }.

Or you can create a dedicated github account for squash and rebase operations, and use it in different bot_account options.

[wismill]

Will branch 3.10 be rebased on master or does it require a backport? Master branch is currently only a few commits ahead.

[Mikolaj]

I think we will backport manually --- it's usually easy thanks to mergify and leaves a paper trail of the history of our decisions. Let me start with the CI fixes though, now that CI finally stabilized (famous last words).

[Mikolaj]

@mergify backport 3.10

[mergify]

backport 3.10

✅ Backports have been created

• #8761 Ensure js-sources are used only with JavaScript arch (backport #8748) has been created for branch 3.10

[Mikolaj]

Backported and merged to 3.10. @wismill, @hsyl20: thank you again.