mirror of
https://github.com/diegosouzapw/OmniRoute.git
synced 2026-11-16 17:09:09 +00:00
Release v3.8.52 — 1,442 documented changes (135 features, 1,112 fixes, 195 maintenance) from 1,386 cycle commits and 306 external contributors; full changelog in CHANGELOG.md → [3.8.52]. Local pre-flight on c754707d: check:release-green --quick --full-ci RELEASE-GREEN (0 HARD / 0 drift), webpack production build + build:cli OK; the release-PR ci.yml run was never dispatched (Actions FIFO backlog), merged with --admin by owner decision at STOP #1. ⚠️ base-red inherited: #15306 (i18n translation drift pinned by 3 unit tests + Docs Sync strict — translation backlog, not code).
1.7 KiB
1.7 KiB
Summary
- Describe the user-facing or operational change.
Related Issues
- Closes #
- Related to #
Target Branch
See the Release Strategy, the Contribution Golden Path and the ROADMAP:
- Base is the active
release/v3.8.xbranch (the highest openrelease/v*), notmain - New feature? From 3.8.55 on it is held with the
v4-featurelabel for the v4 channel - Focused templates: append
?template=feature.mdor?template=bugfix.mdto 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/, orbin/, 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.