Skip to content

feat: [orgpolicy] Support adding constraints to new method types REMOVE_GRANTS and GOVERN_TAGS #11600

feat: [orgpolicy] Support adding constraints to new method types REMOVE_GRANTS and GOVERN_TAGS

feat: [orgpolicy] Support adding constraints to new method types REMOVE_GRANTS and GOVERN_TAGS #11600

Triggered via pull request September 17, 2024 23:13
Status Success
Total duration 4m 59s
Artifacts

presubmit.yaml

on: pull_request
Matrix: units
Fit to window
Zoom out
Zoom in

Annotations

4 warnings
units (18)
The following actions use a deprecated Node.js version and will be forced to run on node20: pnpm/action-setup@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
units (16)
The following actions use a deprecated Node.js version and will be forced to run on node20: pnpm/action-setup@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
units (14)
The following actions use a deprecated Node.js version and will be forced to run on node20: pnpm/action-setup@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
units (20)
The following actions use a deprecated Node.js version and will be forced to run on node20: pnpm/action-setup@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/