Skip to content

ci(deploy): bump azure/login@v2 → v3 (Node 24 runtime)#41

Merged
judedanbo merged 1 commit into
mainfrom
chore/azure-login-v3-node24
Jun 6, 2026
Merged

ci(deploy): bump azure/login@v2 → v3 (Node 24 runtime)#41
judedanbo merged 1 commit into
mainfrom
chore/azure-login-v3-node24

Conversation

@judedanbo

Copy link
Copy Markdown
Owner

Summary

azure/login@v2 runs on the deprecated Node 20 Actions runtime — GitHub surfaces this on every Deploy run:

Node.js 20 actions are deprecated ... azure/login@v2 ... Actions will be forced to run with Node.js 24 by default starting June 16th, 2026.

Bumps all four OIDC Azure login steps in deploy.yml (build-and-push, deploy-data-tier, migrate, deploy-app) from @v2@v3.

Why v3 is a safe drop-in

Verified against the action's action.yml at each tag:

Ref runs.using
azure/login@v2 / @v2.3.0 node20
azure/login@v3 / @v3.0.0 node24

v3.0.0's release notes list a single change — "Upgrade nodejs from 20 to 24 and update dependencies" (Azure/login#578). No input or behavior changes; the client-id/tenant-id/subscription-id interface is unchanged.

actions/checkout@v6 already runs node24, and ci.yml pins its actions by SHA, so azure/login was the only node20 holdout flagged.

Test plan

  • Deploy workflow runs on merge; the Node 20 deprecation annotation is gone and the OIDC login steps still authenticate.

🤖 Generated with Claude Code

azure/login@v2 runs on the deprecated Node 20 actions runtime, which
GitHub flagged on every Deploy run ("Node.js 20 actions are
deprecated ... forced to Node.js 24 by June 16th, 2026"). v3.0.0's
sole change is upgrading the action runtime from Node 20 to Node 24
(Azure/login#578) — same inputs, drop-in replacement. Updates all four
OIDC login steps (build-and-push, deploy-data-tier, migrate, deploy-app).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@judedanbo judedanbo merged commit dcb4bbb into main Jun 6, 2026
1 check passed
@judedanbo judedanbo deleted the chore/azure-login-v3-node24 branch June 6, 2026 20:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant