Skip to content

Commit be49bdb

Browse files
committed
chore(release): update Trusted Publishing checklist Repository field
PR #2 review surfaced two `Repository: python-docs-mcp-server` references in the PyPI Trusted Publishing setup checklists (RELEASE.md lines 11 and 99). These refer to the GitHub repo name used for OIDC token issuance — must match the post-rename `python-stdlib-mcp` or Trusted Publishing will fail at v0.1.5 tag time. PyPI project name (line 9 and 97) stays `python-docs-mcp-server` — the PyPI package name is unchanged.
1 parent c5adbbe commit be49bdb

1 file changed

Lines changed: 2 additions & 2 deletions

File tree

.github/RELEASE.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ Before the first release, configure PyPI Trusted Publishing:
88
2. Add a new pending publisher:
99
- **PyPI project name**: `python-docs-mcp-server`
1010
- **Owner**: your GitHub username or org
11-
- **Repository**: `python-docs-mcp-server`
11+
- **Repository**: `python-stdlib-mcp`
1212
- **Workflow name**: `release.yml`
1313
- **Environment name**: `pypi`
1414
3. In the GitHub repo, go to Settings > Environments
@@ -96,7 +96,7 @@ Complete these steps in order. Each step has a checkbox -- do not skip ahead.
9696
- [ ] PyPI pending publisher configured at https://pypi.org/manage/account/publishing/:
9797
- PyPI project name: `python-docs-mcp-server`
9898
- Owner: `<your-github-username>`
99-
- Repository: `python-docs-mcp-server`
99+
- Repository: `python-stdlib-mcp`
100100
- Workflow name: `release.yml`
101101
- Environment name: `pypi`
102102
- [ ] GitHub environment `pypi` created in repo Settings > Environments

0 commit comments

Comments
 (0)