Provide pre-built musl targets

[vazub]

Closes #48.

As a minor improvement, also fixes Node20 deprecation warning for action runners.

[vercel]

@vazub is attempting to deploy a commit to the ecto's projects Team on Vercel.

A member of the Team first needs to authorize it.

[chojiai]

Choji review — Looks good

The musl target additions are well-structured and the build logic is correct. The only notable issue is a version mismatch between actions/checkout@v6 and actions/upload-artifact@v6 — v6 does not exist for either action (latest stable is v4), but the PR author has confirmed via a successful CI run that these resolve correctly in practice, so this is a NIT rather than a blocker.

No findings — looks good.

---

Reviewed f1e3730 · Choji updates this comment as you push · Mention @chojiai in a comment to discuss, re-review, or request a fix

Dismissing prior approval to re-evaluate f1e3730.

[chojiai]

@chptung — here's where things actually stand:

The previous Choji findings flagged the actions/checkout@v6, actions/upload-artifact@v6, and actions/download-artifact@v7 versions, but @vazub's linked run confirms those versions do work fine in practice, so those findings were false positives. The latest Choji review shows "No findings" as well, so the automated review is now clean.

The only open blocker visible in CI is the Vercel authorization — a team member on ecto's projects needs to approve the deployment. That's unrelated to the workflow changes in this PR.

The PR itself looks solid:

• Adds x86_64-unknown-linux-musl and aarch64-unknown-linux-musl targets ✅
• Uses cross for aarch64-musl (correct approach) ✅
• Adds a static linking verification step ✅
• Bumps Node20-deprecated actions ✅

Nothing blocking on the code side. 🟢

Heads up — your GitHub is linked to a Choji account, but not this repository's team, so I can't use your team's knowledge base here. Ask a team admin to add you, or switch your active team in Choji settings.

- Choji