Add admin-gated Release workflow - #610
Draft
MaddyMicrosoft wants to merge 4 commits into
Draft
Conversation
Reproduces the Azure Login Action release runbook as a manually dispatched workflow: checkout master, build, test, commit the built lib/ to a releases/vX.Y.Z branch, tag that commit, force-move the major tag (e.g. v3), and publish a GitHub Release. Admin-only is enforced two ways: - environment: release, which pauses the run until a required reviewer (admin) approves. This is the primary gate and must be configured with required reviewers in repo settings before the first real release. - an 'Ensure triggered by an admin' step that fails fast for non-admins. Actions are pinned to @v6 to match the rest of the repo.
Undo a bad release by re-pointing the major tag (e.g. v3) back to a known-good, already-published version tag. This is the fast consumer-facing fix: anyone on azure/login@v3 recovers immediately. - Admin-gated the same two ways as release.yml: environment: release approval plus an actor-admin check. - Shares the 'release' concurrency group so a rollback can never race an in-flight release (both push the same major tag). - Verifies the target tag exists and carries both built entry points (lib/main/index.js and lib/cleanup/index.js) before moving the major tag, so it can never point consumers at unbuilt code. - Optionally resets the 'Latest' release badge; tolerates a missing Release object so a cosmetic badge failure never fails a successful tag rollback. - Does NOT delete the bad tag/branch/release (someone may have pinned the exact version); left as a deliberate manual step. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
MaddyMicrosoft
requested a deployment
to
Automation test
August 17, 2026 03:09 — with 
GitHub Actions
Waiting
GitHub Actions
Waiting
MaddyMicrosoft
requested a deployment
to
Automation test
August 17, 2026 03:09 — with
GitHub Actions
Waiting
GitHub Actions
Waiting
MaddyMicrosoft
requested a deployment
to
Automation test
August 17, 2026 03:09 — with
GitHub Actions
Waiting
GitHub Actions
Waiting
MaddyMicrosoft
requested a deployment
to
Automation test
August 17, 2026 03:09 — with
GitHub Actions
Waiting
GitHub Actions
Waiting
MaddyMicrosoft
requested a deployment
to
Automation test
August 17, 2026 03:09 — with
GitHub Actions
Waiting
GitHub Actions
Waiting
MaddyMicrosoft
requested a deployment
to
Automation test
August 17, 2026 03:09 — with
GitHub Actions
Waiting
GitHub Actions
Waiting
MaddyMicrosoft
requested a deployment
to
Automation test
August 17, 2026 03:09 — with
GitHub Actions
Waiting
GitHub Actions
Waiting
MaddyMicrosoft
requested a deployment
to
Automation test
August 17, 2026 03:09 — with
GitHub Actions
Waiting
GitHub Actions
Waiting
MaddyMicrosoft
requested a deployment
to
Automation test
August 17, 2026 03:09 — with
GitHub Actions
Waiting
GitHub Actions
Waiting
MaddyMicrosoft
requested a deployment
to
Automation test
August 17, 2026 03:09 — with
GitHub Actions
Waiting
GitHub Actions
Waiting
MaddyMicrosoft
requested a deployment
to
Automation test
August 17, 2026 03:09 — with
GitHub Actions
Waiting
GitHub Actions
Waiting
MaddyMicrosoft
requested a deployment
to
Automation test
August 17, 2026 05:37 — with
GitHub Actions
Waiting
GitHub Actions
Waiting
MaddyMicrosoft
requested a deployment
to
Automation test
August 17, 2026 05:37 — with
GitHub Actions
Waiting
GitHub Actions
Waiting
MaddyMicrosoft
requested a deployment
to
Automation test
August 17, 2026 05:37 — with
GitHub Actions
Waiting
GitHub Actions
Waiting
MaddyMicrosoft
requested a deployment
to
Automation test
August 17, 2026 05:37 — with
GitHub Actions
Waiting
GitHub Actions
Waiting
MaddyMicrosoft
requested a deployment
to
Automation test
August 17, 2026 05:37 — with
GitHub Actions
Waiting
GitHub Actions
Waiting
MaddyMicrosoft
requested a deployment
to
Automation test
August 17, 2026 05:37 — with
GitHub Actions
Waiting
GitHub Actions
Waiting
MaddyMicrosoft
requested a deployment
to
Automation test
August 17, 2026 05:37 — with
GitHub Actions
Waiting
GitHub Actions
Waiting
MaddyMicrosoft
requested a deployment
to
Automation test
August 17, 2026 05:37 — with
GitHub Actions
Waiting
GitHub Actions
Waiting
MaddyMicrosoft
requested a deployment
to
Automation test
August 17, 2026 05:37 — with
GitHub Actions
Waiting
GitHub Actions
Waiting
MaddyMicrosoft
requested a deployment
to
Automation test
August 17, 2026 05:37 — with
GitHub Actions
Waiting
GitHub Actions
Waiting
MaddyMicrosoft
requested a deployment
to
Automation test
August 17, 2026 05:37 — with
GitHub Actions
Waiting
GitHub Actions
Waiting
MaddyMicrosoft
had a problem deploying
to
Automation test
August 17, 2026 05:38 — with
GitHub Actions
Error
GitHub Actions
Error
MaddyMicrosoft
had a problem deploying
to
Automation test
August 17, 2026 05:38 — with
GitHub Actions
Error
GitHub Actions
Error
MaddyMicrosoft
had a problem deploying
to
Automation test
August 17, 2026 05:38 — with
GitHub Actions
Error
GitHub Actions
Error
MaddyMicrosoft
had a problem deploying
to
Automation test
August 17, 2026 05:38 — with
GitHub Actions
Error
GitHub Actions
Error
MaddyMicrosoft
had a problem deploying
to
Automation test
August 17, 2026 05:38 — with
GitHub Actions
Error
GitHub Actions
Error
MaddyMicrosoft
had a problem deploying
to
Automation test
August 17, 2026 05:38 — with
GitHub Actions
Error
GitHub Actions
Error
MaddyMicrosoft
had a problem deploying
to
Automation test
August 17, 2026 05:38 — with
GitHub Actions
Error
GitHub Actions
Error
MaddyMicrosoft
had a problem deploying
to
Automation test
August 17, 2026 05:38 — with
GitHub Actions
Error
GitHub Actions
Error
MaddyMicrosoft
had a problem deploying
to
Automation test
August 17, 2026 05:38 — with
GitHub Actions
Error
GitHub Actions
Error
MaddyMicrosoft
had a problem deploying
to
Automation test
August 17, 2026 05:38 — with
GitHub Actions
Error
GitHub Actions
Error
MaddyMicrosoft
had a problem deploying
to
Automation test
August 17, 2026 05:38 — with
GitHub Actions
Error
GitHub Actions
Error
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Reproduces the Azure Login Action release runbook as a manually dispatched workflow: checkout master, build, test, commit the built lib/ to a releases/vX.Y.Z branch, tag that commit, force-move the major tag (e.g. v3), and publish a GitHub Release.
Admin-only is enforced two ways:
Actions are pinned to Nathan Basanese (@v6) to match the rest of the repo.