Complete and verify the Bun CI cutover #293

New Issue

2026-10-17T02:35:38+02:00

nessar commented

2026-10-17 02:35:38 +02:00

What to build

The maintainer can rely on one reproducible Bun toolchain from
a clean checkout through required CI checks and the production container, with
evidence that no project-owned JavaScript step still falls back to Node.

Acceptance criteria

Complete project-owned policy and image-publisher invocation under Bun,
including their regression scripts, child processes, executable fixtures,
and CI entry points. Preserve their temporary-repository and fake-Docker
tests so local verification performs no real registry writes.
Preserve policy/publisher outcomes for push, pull-request, fork, manual, and
stable-release events. Runtime changes must not alter GitFlow, Conventional
Commit enforcement, publication eligibility, or existing image promotion.
Audit every project command, child executable, CI step, container stage,
and documented prerequisite. Use the same exact verified Bun release and
frozen dependencies throughout; remove obsolete callers, configuration,
and dependencies after confirming they have no remaining use.
Exercise the documented developer workflow, full native functional suite,
coverage, lint, formatting, standalone type checks, Angular production
build, benchmark protocol, and production container on the integrated
branch. Demonstrate Bun execution with Node unavailable to project commands.
Preserve security scans, artifact retention and failure-path coverage
uploads, required benchmark and publication dependencies, and the aggregate
required check. Do not weaken tests, budgets, or gates to claim completion.
Verify any third-party Gitea action runtime requirement separately. Do not
treat infrastructure-provided Node as permission to run project commands
with it; surface unresolved infrastructure changes or exceptions.
Rebase the scoped feature integration branch onto current origin/develop
before the PR to develop, and rerun affected checks if the base advances.
Use the repository's required PR/maintainer integration process; do not push
directly to protected branches or merge without authorization.
Obtain successful required Gitea checks on the final PR revision under the
existing activation and publication process. Keep local evidence distinct
from live CI results; missing credentials or activation evidence must be
reported rather than bypassed or provisioned without authorization.
Hand off the verification results and any remaining blockers against the migration's
published acceptance criteria. No native-tool incompatibility, missing required report,
Node fallback, or unverified required gate may be described as complete.
Do not change branch protections, create release tags, or deploy.

Blocked by

#290 — Run development and quality checks with Bun
#291 — Run all tests and benchmarks with Bun
#292 — Serve the deployed application with Bun

## What to build The maintainer can rely on one reproducible Bun toolchain from a clean checkout through required CI checks and the production container, with evidence that no project-owned JavaScript step still falls back to Node. ## Acceptance criteria - [ ] Complete project-owned policy and image-publisher invocation under Bun, including their regression scripts, child processes, executable fixtures, and CI entry points. Preserve their temporary-repository and fake-Docker tests so local verification performs no real registry writes. - [ ] Preserve policy/publisher outcomes for push, pull-request, fork, manual, and stable-release events. Runtime changes must not alter GitFlow, Conventional Commit enforcement, publication eligibility, or existing image promotion. - [ ] Audit every project command, child executable, CI step, container stage, and documented prerequisite. Use the same exact verified Bun release and frozen dependencies throughout; remove obsolete callers, configuration, and dependencies after confirming they have no remaining use. - [ ] Exercise the documented developer workflow, full native functional suite, coverage, lint, formatting, standalone type checks, Angular production build, benchmark protocol, and production container on the integrated branch. Demonstrate Bun execution with Node unavailable to project commands. - [ ] Preserve security scans, artifact retention and failure-path coverage uploads, required benchmark and publication dependencies, and the aggregate required check. Do not weaken tests, budgets, or gates to claim completion. - [ ] Verify any third-party Gitea action runtime requirement separately. Do not treat infrastructure-provided Node as permission to run project commands with it; surface unresolved infrastructure changes or exceptions. - [ ] Rebase the scoped feature integration branch onto current `origin/develop` before the PR to `develop`, and rerun affected checks if the base advances. Use the repository's required PR/maintainer integration process; do not push directly to protected branches or merge without authorization. - [ ] Obtain successful required Gitea checks on the final PR revision under the existing activation and publication process. Keep local evidence distinct from live CI results; missing credentials or activation evidence must be reported rather than bypassed or provisioned without authorization. - [ ] Hand off the verification results and any remaining blockers against the migration's published acceptance criteria. No native-tool incompatibility, missing required report, Node fallback, or unverified required gate may be described as complete. Do not change branch protections, create release tags, or deploy. ## Blocked by - #290 — Run development and quality checks with Bun - #291 — Run all tests and benchmarks with Bun - #292 — Serve the deployed application with Bun

nessar added the ready-for-agent label 2026-10-17 02:35:38 +02:00

nessar added a new dependency 2026-10-17 02:35:38 +02:00

#290 Run development and quality checks with Bun

nessar added a new dependency 2026-10-17 02:35:38 +02:00

#291 Run all tests and benchmarks with Bun

nessar added a new dependency 2026-10-17 02:35:38 +02:00

#292 Serve the deployed application with Bun

nessar referenced this issue from a commit

2026-10-17 16:10:35 +02:00

ci: run development, quality checks and CI on Bun 1.4.3

nessar referenced this issue from a commit

2026-10-17 16:10:35 +02:00