Skip to content

Clarify v1 workflow references in maintenance docs #33

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
omry merged 1 commit into from
Oct 20, 2026
Merged

Clarify v1 workflow references in maintenance docs #33

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 2 additions & 1 deletion docs/audit-schedules.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -53,7 +53,8 @@ In the [setup guide's caller](node-maintenance.md#3-add-the-caller-workflow), us
- upgrades
```

Keep the remaining caller jobs, permissions, SHA pins, and audit input forwarding:
Keep the remaining caller jobs, permissions, workflow references (`@v1` or matching
full commit SHAs), and audit input forwarding:

```yaml
with:
Expand Down
5 changes: 3 additions & 2 deletions node/maintenance.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -168,5 +168,6 @@ to the built-in token. See [credential setup and PR CI behavior](../docs/node-ma

The workflow does not add CI-skip markers. Consumer CI follows its configured
triggers and token rules. Neither authentication mode waits for additional PR CI
or merges the PR. Consumers call both shared workflows at the same full commit
SHA; update both pins together using the [update instructions](../docs/node-maintenance.md#update-or-migrate-an-installation).
or merges the PR. Consumers call both shared workflows at the same major release
tag, such as `@v1`, or the same full commit SHA. Change both references together
using the [update instructions](../docs/node-maintenance.md#update-or-migrate-an-installation).
Loading