mirror of https://github.com/diegosouzapw/OmniRoute.git synced 2026-08-05 14:52:09 +03:00

Files

Diego Rodrigues de Sa e Souza 764d91fdfa fix(oauth): mirror ghe-copilot into the OAuth id map and MITM host list

#7546 registered the ghe-copilot provider in src/lib/oauth/providers/index.ts but
left it out of two mirrors that are asserted to stay in lock-step:

- PROVIDERS in src/lib/oauth/constants/oauth.ts (the canonical id map), which made
  oauth-providers-config.test.ts fail three assertions at once;
- MITM_TOOL_HOSTS, the client-safe projection of ALL_TARGETS, which made
  mitm-tool-hosts.test.ts fail its drift guard.

Both reds reproduce on the pure release tip and turned every open PR's unit shards
red, so this unblocks the whole queue. The test expectations are extended (not
weakened) to cover the new provider.

2026-07-20 06:52:05 -03:00

features

feat(providers): Complete GHE Copilot OAuth provider implementation (#7546 )

2026-07-19 21:22:37 -03:00

fixes

fix(docs): document CREDENTIAL_REDACTION_ENABLED and GHE_COPILOT_OAUTH_CLIENT_ID (#7793 ) (#7833 )

2026-07-20 02:18:14 -03:00

maintenance

fix(oauth): mirror ghe-copilot into the OAuth id map and MITM host list

2026-07-20 06:52:05 -03:00

README.md

feat(release): changelog.d/ fragments — eliminate the CHANGELOG merge-storm cascade (#6783 )

2026-07-10 07:22:49 -03:00

README.md

changelog.d/ — changelog fragments

A PR never edits CHANGELOG.md directly during the cycle. Instead it adds ONE new file here — its changelog entry as a fragment. Two PRs never touch the same file, so changelog merge conflicts (the "CHANGELOG-eat" cascade that forced a re-sync push + full CI re-run after every sibling merge) are structurally impossible.

Convention

Directory	Aggregates under
`features/`	`### ✨ New Features`
`fixes/`	`### 🐛 Bug Fixes`
`maintenance/`	`### 📝 Maintenance`

Filename: <PR-number>-<short-slug>.md (e.g. fixes/6700-dockerfile-better-sqlite3.md). The PR number prefix keeps aggregation order deterministic.
Content: the exact bullet line(s) that should land in CHANGELOG.md, starting with - . Multi-line (continuation) bullets are fine. Keep the repo's credit format: (#PR — thanks @user).
One fragment per PR (rarely more, e.g. a PR that both fixes and adds).

Example

changelog.d/fixes/6496-cloudflare-relay-worker-syntax.md:

- **fix(providers):** Cloudflare relay Worker deploys use Service Worker syntax with `body_part` metadata ([#6496](https://github.com/diegosouzapw/OmniRoute/pull/6496)) — thanks @SeaXen

Aggregation

The release captain (or /generate-release) folds all fragments into CHANGELOG.md and deletes them:

node scripts/release/aggregate-changelog.mjs            # write + delete fragments
node scripts/release/aggregate-changelog.mjs --dry-run  # preview only

Fragment well-formedness is enforced by npm run check:changelog-integrity (the same gate that guards against CHANGELOG-eat for legacy direct edits).