You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Release v1.0.0 and point the open rollout pull requests at it #8
Release the shared workflow as v1.0.0 and point every open rollout pull request at it, so exactly one copy of the review-request logic is in use.
Acceptance criteria
v1.0.0 is tagged on main and published as a GitHub release whose notes describe the three kinds of review request, the team check, and the secrets and inputs a caller passes.
Status 2026-11-18: everything this release needs is in review as a stack: #10 (checks, closes #2) → #11 (Ready, closes #5) → #12 (comment command, closes #6) → #13 (requested reviewer, closes #7). Each needs an approving review from someone other than its author before it can merge. Once all four are on main, this ticket tags v1.0.0 and re-pins the rollout pull requests; the example caller and the ore.rs pilot currently pin pre-release commits on the feature branches.
Activity
cipherstash-agent commentedon Nov 18, 2026
Status 2026-11-18: everything this release needs is in review as a stack: #10 (checks, closes #2) → #11 (Ready, closes #5) → #12 (comment command, closes #6) → #13 (requested reviewer, closes #7). Each needs an approving review from someone other than its author before it can merge. Once all four are on
main, this ticket tagsv1.0.0and re-pins the rollout pull requests; the example caller and the ore.rs pilot currently pin pre-release commits on the feature branches.Generated by Claude Code
fix(react): grant pull-requests: write so the 👀 reaction can be added
feat!: name the membership App by its client ID, from an organisation…
ci(examples): pin the example caller to the v1.0.0 release