Skip to content

Run dependency updates as App-authenticated pull requests only - #572

Merged
woksin merged 2 commits into
mainfrom
l163/215-pr-only-updates
Nov 21, 2026
Merged

woksin merged 2 commits into
mainfrom
l163/215-pr-only-updates

Conversation

@woksin

@woksin woksin commented Nov 21, 2026

Copy link
Copy Markdown
Contributor

Changed

  • The dependency-update workflow now opens reviewed pull requests only: it selects pull-request publication explicitly, uses the Cratis automation App instead of a personal access token, and fails before any change when the App is not configured. It stays manual-only (part of Restore dependency updates through reviewed pull requests #215)

Require complete automation App configuration before the reusable updater runs. Keep updates manual-only and block credential fallback while preserving the existing package exclusions.
@woksin woksin added the no-release Merging publishes no package, image, release, or deployment label Nov 21, 2026
@woksin woksin self-assigned this Nov 21, 2026
@woksin

woksin commented Nov 21, 2026

Copy link
Copy Markdown
Contributor Author
  • Deep review (security lens; Opus and GPT-6 Astra, checked against the shared Cratis/Workflows updater) passed with no blocking findings. Advisory left as is: the preflight job receives the App key only to test that it is set.
  • Local: root yarn ci passed on this head; the 12 workflow contract specs, actionlint and lint pass.
  • Not verified: an actual run. The automation App (CRATIS_AUTOMATION_APP_ID variable and AUTOMATION_APP_PRIVATE_KEY secret) must be provisioned by an organization admin; until then a manual run fails in preflight by design. The schedule stays paused; restoring it is the remaining part of Restore dependency updates through reviewed pull requests #215 after a verified manual run.
  • The reusable workflow is still referenced at @main (pre-existing).

@woksin
woksin merged commit e378baf into main Nov 21, 2026
44 of 45 checks passed
@woksin
woksin deleted the l163/215-pr-only-updates branch November 21, 2026 23:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

no-release Merging publishes no package, image, release, or deployment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant