We investigated both CI failures and determined neither is caused by this PR's changes. The tanstack-react-start-e2e-rsc shard failure is a stale e2e-utils build artifact in the CI environment (a missing ESM export unrelated to handlebars), and the tanstack-vue-start-e2e-basic-vue-query failure is a pre-existing port conflict on 127.0.0.1:34365 left by a previous process. Re-running CI after the environment is cleaned up should resolve both failures.
Failed after Ddependabot[bot]View latest
Bump handlebars from 4.1.0 to 4.5.3
47e71d20Open on GitHubSelf-Healing CI
Classification: Environment state
An empty commit was applied to the branch to trigger a new CI pipeline execution to resolve the environment issue.
The PR is a Dependabot security bump of the handlebars package from 4.1.0 to 4.5.3. No application source files, test fixtures, or port configuration were modified — only the package manifest and lockfile changed.
Task 1 — tanstack-react-start-e2e-rsc:test:e2e--vite-ssr--shard-4-of-6 The error is a SyntaxError stating that ./fixture.js does not export collectBrowserErrors. This export lives in the compiled build artifact at e2e/e2e-utils/dist/esm/index.js, not in any file touched by this PR. handlebars is a templating engine with no relationship to ESM module exports in a Playwright test fixture. The touched_projects field contains * only because the lockfile changed — it does not indicate that the e2e-utils source or its dist output was intentionally modified. The ~0.51% flakiness rate is marginal and the error itself is deterministic (a missing export is not a race condition), so a flaky classification is not appropriate either. The root cause is a stale or inconsistently built e2e-utils dist directory in the CI environment.
Task 2 — tanstack-vue-start-e2e-basic-vue-query:test:e2e The error is EADDRINUSE: address already in use 127.0.0.1:34365. Port 34365 is dynamically mapped for the tanstack-vue-start-e2e-basic-vue-query-external server, and it was already occupied by another process when the test tried to bind. The handlebars bump introduces zero changes to port configuration, server setup, or test infrastructure. The flakiness rate for this task is exactly 0%, ruling out a flaky classification. The failure requires the occupying process to be cleared before a rerun will succeed — a classic environment state condition.