fix(bun): prefer baseline linux releases (fix #879)

[Tori0419]

Fixes #879

Summary

• keep Bun's -baseline Linux assets instead of filtering them out
• prefer the baseline build over the default build for the same Linux x64 target
• keep debug/profile builds excluded
• add a narrow regression test for release ordering

Why

bun can select a non-baseline Linux binary that crashes with SIGILL on older/container CPUs.
This change makes the release list prefer the baseline variant when both assets exist for the same target.

Testing

• added bun/releases.test.js covering:
  • baseline preferred over default Linux x64 assets
  • non-Linux asset order unchanged

Notes

I could not run the repo's Node-based lint/test commands locally in this environment because node/npm were unavailable.

[coolaj86]

Weird, I thought I had fixed this years ago. Looks good. Testing now.

note: GitHub Releases seems to be having an outage (release downloads aren't working on my server or my home laptop), making it difficult to get a new testing environment up. I'll try again tomorrow.

[Copilot]

Pull request overview

Updates Bun’s release normalization so Linux -baseline assets are retained and preferred over the default Linux x64 assets to avoid SIGILL on older/container CPUs.

Changes:

• Stop filtering out Bun Linux -baseline assets; continue filtering out -profile builds.
• Prefer -baseline over default for the same Linux x64 target (including -musl) via release ordering.
• Add a narrow regression test for Linux baseline preference and non-Linux ordering.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.

File	Description
bun/releases.js	Refactors release filtering/normalization and adds baseline-preferred ordering logic for Linux x64 targets.
bun/releases.test.js	Adds a node:test regression test for baseline ordering and non-Linux order preservation.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[coolaj86]

The sort strategy alone didn't work, but I changed it to just use baseline when baseline is available and that solves the problem.

[coolaj86]

@detox-24 This was also kinda Ai slop (it didn't actually understand the problem to fix it correctly). However, it was at least attempting to address an actual problem.

[detox-24]

Ah! I gotta keep a sharper eye!