Bump bun version in CI to 1.3.10

[Copilot]

Bumps the pinned Bun version across all CI jobs from 1.3.9 → 1.3.10, and switches to a .bun-version file so future upgrades only require a single edit.

What's changed

• Added .bun-version file at the repo root pinning Bun to 1.3.10
• Updated all 8 oven-sh/setup-bun@v2 steps in .github/workflows/ci.yml to use bun-version-file: .bun-version instead of a hardcoded bun-version

Testing

• N/A — CI config change only; no runtime logic affected.

Checklist

• I have run bun run format.
• I have run relevant lint(s): bun run --cwd <workspace> lint.
• I added/updated tests for behavior changes (or documented why tests are not applicable).
• If I changed dimp-server runtime logic, I ran bun run --cwd dimp-server test.
• If I changed dimp-server GraphQL/HTTP/DB behavior, I ran bun run --cwd dimp-server test:integration:local (or documented why I skipped it).
• If I changed dimp-server runtime logic, I ran bun run --cwd dimp-server test:coverage.
• If applicable, I have updated Drizzle migrations:
  
  • bun run --cwd dimp-server drizzle-kit generate --name <migration_name>.
  • bun run --cwd dimp-auth drizzle-kit generate --name <migration_name>.
• If applicable, I regenerated the GraphQL schema: bun run --cwd dimp-server generate-schema.
• If applicable, I ran GraphQL codegen: bun run --cwd dimp-bot codegen.

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Bump bun version in CI to 1.3.10</issue_title>
<issue_description></issue_description>

Comments on the Issue (you are @copilot in this section)

• Fixes Bump bun version in CI to 1.3.10 #215

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[1spyral]

@copilot is there a better way to do this instead of having to bump the version every time? Like I could imagine if you didnt specify the version it would use whatever package.lock says

[Copilot]

@copilot is there a better way to do this instead of having to bump the version every time? Like I could imagine if you didnt specify the version it would use whatever package.lock s...

Yes — the oven-sh/setup-bun@v2 action supports a bun-version-file parameter. I've added a .bun-version file at the repo root (containing 1.3.10) and updated all CI steps to use bun-version-file: .bun-version instead of the hardcoded version. Future bumps only require editing .bun-version in one place (commit b97c8af).