singlaamitesh opened a new pull request, #1434:
URL: https://github.com/apache/tooling-trusted-releases/pull/1434
Fixes #1049
## Pull request summary <!-- markdownlint-disable-line MD041 -->
**Meaningful subject (required):**
<!--
Provide a clear, concise subject line.
Good:
"Fix schema endpoint auth bypass for OpenAPI"
"Refactor report authorization filters"
Bad:
"Fix"
"Updates"
-->
**Description:**
<!-- Explain what this PR changes and why -->
---
## Required acknowledgements
Please replace each `[ ]` with `[x]` to confirm.
PRs missing confirmations may be closed or converted to Draft.
* [ ] I have read and followed **CONTRIBUTING.md**
* [ ] I have read **DEVELOPMENT.md**
* [ ] I have run the required tests and checks locally
* [ ] All required checks are currently passing
* [ ] This branch is **rebased on the current `main` branch**
---
## Draft requirement
If **any** of the following are true:
* Tests or checks are failing
* Work is incomplete
* Rebase on `main` is pending
**This PR MUST be opened or converted to a Draft**:
Convert to a ready PR only after all acknowledgements above can be confirmed.
---
## Rebase confirmation details (optional but encouraged)
<!--
If helpful, note how the rebase was done:
git fetch origin
git rebase origin/main
-->
---
## Additional notes
<!--
Anything reviewers should know:
- Design decisions
- Follow-up work
- Compatibility concerns
-->
---
Verified the documentation gap by reading the storage writers, SSH server,
and admin blueprint, then added six new sections (Distribution, SSH/rsync, Key,
Policy, Project, Admin operations) plus a consolidated Phase-based access
control matrix to atr/docs/authorization-security.md, grounding every claim in
the actual permission-tier code and cross-checking phase transitions in
release.py/vote.py/announce.py rather than assuming the issue's suggested table.
**How this was tested:** `make your changes** following our [code
conventions](https://release-test.apache.org/docs/code-conventions)`
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
