Greptile Summary

This PR fixes a CI setup failure by stripping a non-resolvable build-commit suffix from the pinned Bun version in the shared setup-node-env composite action, changing "1.3.9+cf6cdbbba" → "1.3.9".

The fix is correct and minimal — oven-sh/setup-bun@v2 only exposes stable release assets, so the +cf6cdbbba build identifier caused a 404 at download time and blocked every Bun-dependent CI job. No other inputs, steps, or downstream workflows are affected.

Confidence Score: 5/5

• Safe to merge — this is a one-line, targeted fix to a broken CI version string with no functional impact on application code.
• The change removes a non-publishable build suffix from a version pin, restoring the correct stable release string. The diff is trivial and the root cause is well-understood. No application code, dependencies, or other workflows are touched.
• No files require special attention.

_{Last reviewed commit: ef18f55}

Objective status snapshot:

• Current state is CLEAN with no failing checks and high review confidence (5/5).

Actionable next steps:

1. Consider adding one guard test in the composite action workflow to prevent reintroducing non-resolvable Bun build suffix pins.
2. If no new failures appear, this is merge-ready from my side.

This fix would unblock the checks (bun, test, ...) CI job that's currently failing across all open PRs due to the unresolvable Bun build pin. The 404 from oven-sh/setup-bun on 1.3.9+cf6cdbbba is a straightforward version resolution issue — stripping the build suffix to 1.3.9 is the right call. Would love to see this merged so CI goes green again.

Thanks for the detailed feedback. I kept this PR intentionally minimal to unblock CI quickly with the Bun version fix; I’m happy to add a separate guard test if maintainers want that follow-up.

Looks like its been fixed already