FixOps
Play now
Git Advanced About 30 min +250 XP

Release Token Appears in Commit History

A release token file is tracked at the tip of main, and the credential has to be treated as exposed until it is revoked.

Take this incident no signup All incidents

Stage 1 of 7 in Friday Deploy Meltdown.

Briefing

Friday's release train had barely left when the secret scanner flagged main: a debug commit added a file under tokens/ that holds a working release token.

The token can publish to the release registry, so it has to be treated as exposed from the moment it was committed, whether or not anyone has cloned the repository since.

Removing the file cleans up the tree but not the credential, and only the issuing team can revoke it.

Dev's first instinct is to rewrite main so the commit never happened.

The fix is yours to find: hints, the recovery checks and the debrief unlock inside the incident.

How it plays

  1. 01

    Get paged

    The alert fires and the clock starts. Read the page and the briefing.

  2. 02

    Investigate

    Work in a simulated shell with realistic output: logs, configs, services.

  3. 03

    Fix it

    Change the system the way you would in production. Hints are there if you get stuck.

  4. 04

    Prove it

    Automated checks verify the recovery, then the debrief explains what happened.

All 61 incidents
Git Intermediate

Checkout Errors Rise After Release

Checkout's error rate jumped from about 0.2% to 23% within minutes of the latest configuration release.

+210 XP30 minStage 2/7

Git Intermediate

Checkout Hotfix Is Missing From Main

The retry change that passed checkout testing is absent from main, so the release build would ship the old behaviour.

+210 XP30 minStage 3/7

Your pager is ready.

Free, instant, and it works on your phone. No signup: start as a guest and save your progress later.

Take this incident no signup Get it on Google Play