Skip to content

style(format): normalize master promotion range #226

Description

@kattsushi

Problem

The dev → master beta-promotion PR #225 runs changed-file formatting over the full promotion range. Oxfmt reports 51 historical files that are valid on incremental dev PRs but not normalized against the older master baseline. This keeps promotion CI red.

Scope

Apply the pinned repository formatter to exactly the 51 files reported by promotion CI across:

  • React Router example Hatchet/runtime tests and routes
  • @effectify/hatchet source/tests/scripts/project config
  • React Router and Better Auth runtime/test/config files

Acceptance criteria

  • No semantic/manual edits; formatter output only.
  • Exact promotion command pnpm nx run @effectify/repo:format:check --args="--base=origin/master --head=HEAD" passes.
  • Affected lint/typecheck/build/test and focused Hatchet/RR8 suites pass.
  • No package versions, lockfile, release workflows, docs, OpenSpec, generated outputs, tags, or publication change.
  • After merge to dev, PR chore(promotion): promote dev to master for beta #225 is refreshed and reruns green CI.

Review boundary

This is a dedicated mechanical formatting prerequisite for beta promotion. Large generated formatter churn, if any, must be measured and explicitly recorded rather than mixed into #225.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    status:approvedApproved for implementation / PR linkagetype:choreMaintenance/tooling work

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions