Files
OmniRoute/.github/pull_request_template.md
Diego Rodrigues de Sa e Souza a71402083f chore(release): dormant LTS release infra — labels, PR templates, RELEASE_STRATEGY (rail 3.8.54) (#16073)
* chore(release): declarative rail labels + labels:sync script

Add .github/labels.yml with the dormant LTS-rail labels (v4-feature, lts,
forward-port, channel:latest|next|nightly, preview-artifact) and
scripts/release/sync-labels.mjs (npm run labels:sync): dry-run by default,
--apply creates missing / edits divergent labels, never deletes and never
touches labels outside the file. gh runs via execFile argv (Hard Rule #13).

Colors must be quoted in the YAML: unquoted hex such as 5319E7 is parsed as
a float and 012345 as an int, so the parser refuses non-string colors.

* chore(release): feature and bugfix PR templates + target-branch checklist

Add .github/PULL_REQUEST_TEMPLATE/feature.md and bugfix.md (selected with
?template=feature.md / ?template=bugfix.md). The bugfix template requires a
failing-then-passing test or a recorded real-environment validation (Hard
Rule #18). The default template gains a short target-branch checklist that
links the release strategy, the contribution golden path and the ROADMAP.

* docs(release): RELEASE_STRATEGY for the dormant LTS rail

Document the 3.9.0 branch model (stable/v3, develop, main), what lands in each
branch, the npm dist-tags (latest = v3 until 4.0 GA, next = rc, nightly),
forward-port with Co-authored-by credit, the 3.8.55-3.8.59 validation window
and the v4-feature label rule. States what the publish workflow wires today
and what is still missing (nightly dist-tag, post-GA v3 patch tag). Linked
from ROADMAP.md, docs/README.md and the ops sidebar.
2026-10-10 09:53:32 -03:00

1.7 KiB

Summary

  • Describe the user-facing or operational change.
  • Closes #
  • Related to #

Target Branch

See the Release Strategy, the Contribution Golden Path and the ROADMAP:

  • Base is the active release/v3.8.x branch (the highest open release/v*), not main
  • New feature? From 3.8.55 on it is held with the v4-feature label for the v4 channel
  • Focused templates: append ?template=feature.md or ?template=bugfix.md to the compare URL

Validation

Choose the change type and focused loop from the Contribution Golden Path. The full unit suite, Vitest, the 60% coverage gate, and the production build all run in CI on this PR (#8329):

  • Change type: provider / routing / UI / i18n / CLI / DB / build-deploy / other
  • Focused tests and category gates from the golden path
  • npm run lint
  • Reconciled with the current active release base; focused checks rerun afterward
  • Production-code changes include a new or updated automated test in this PR
  • SonarQube is temporarily opt-in while the private project has no quota; it is not a PR gate.

Tests Added Or Updated

  • List every changed or added automated test file.
  • If no production code changed, state that here.

Coverage Notes

  • If this PR changes src/, open-sse/, electron/, or bin/, explain which tests cover the change.
  • If coverage moved down in any touched file, explain why and what follow-up task will recover it.

Reviewer Notes

  • Call out any risky areas, migrations, feature flags, or manual validation that reviewers should know about.