95668f5eab
- atlassian: /v1/sse was deprecated by Atlassian after June 30 2026 — installs OAuth'd fine then failed every handshake with 404 (#91538). Now points at /v1/mcp/authv2, the endpoint Atlassian's docs recommend for custom clients (live-probed: OAuth 2.1 + DCR intact). - grafana (on top of @cedricziel's #93183 entry): defensive default_excluded for ask_assistant (opaque Assistant delegation meta-tool, bills usage) and agento11y_* (Grafana's own agent-obs product suite) — both from Grafana's published tool tables, both no-ops until the Cloud surface serves them; billing note added to post_install.
Contributor email → GitHub login mappings
This directory replaces appending entries to AUTHOR_MAP in
scripts/release.py. The old dict caused constant merge conflicts when
several salvage PRs landed at once — every PR edited the same lines of the
same file. Here, each mapping is its own file, and file additions never
conflict.
Adding a mapping
One file per commit-author email, under emails/:
python3 scripts/add_contributor.py <email> <github-login>
# or by hand:
echo "<github-login>" > contributors/emails/<email>
- File name = the exact commit-author email (as shown by
git log --format='%ae'). - File content = the GitHub login on the first non-comment line.
Lines starting with
#are comments (use them for the PR reference).
Example — contributors/emails/jane.doe@example.com:
janedoe
# PR #12345 salvage (gateway: fix session key routing)
Rules
- Do NOT add new entries to
AUTHOR_MAPinscripts/release.py. That dict is frozen legacy data; the release tooling merges it with this directory (directory entries win on duplicates). - GitHub noreply emails (
<id>+<login>@users.noreply.github.comand<login>@users.noreply.github.com) auto-resolve — no file needed. - The
Contributor Attribution CheckCI job fails a PR whose commits carry an unmapped email; the failure message prints the exact command to run.