syntaqxBrokered secrets keep working after a job's token is swapped. The runner Worker looks up a job's stand-ins (brokered_secrets) with the token the job started with, which a harness that asks for rotation spends on its first spec fetch. The swap now keeps that token's hash beside the new one (first_token_hash, migration 0020), and brokered_secrets alone accepts it; reporting, logs, artifacts, cache, job_auth, actions and the spec itself take only the current token, and no API route passes brokered_secrets on, so the kept token is reachable only through g1t's own service bindings. It is cleared when the job ends, is cancelled, is claimed again or is re-run. The self-hosted runners guide says which lookup still takes it.495a2cbHistory
- ..
- accounts.rs
- ai.rs
- attribution.rs
- budget.rs
- cards.rs
- catalogue.rs
- catalogue_tests.rs
- charged.rs
- closing.rs
- compute.rs
- costs.rs
- credits.rs
- cycle.rs
- details.rs
- features.rs
- gateway.rs
- gateway_tests.rs
- grants.rs
- invoices.rs
- keeper.rs
- lib.rs
- limits.rs
- margin.rs
- overages.rs
- platform.rs
- pricing.rs
- rename.rs
- report.rs
- requests.rs
- reset.rs
- retention.rs
- sales.rs
- statement.rs
- storage.rs
- stripe.rs
- stripe_sync.rs
- subscriptions.rs
- tax.rs
- tokens.rs
- webhooks.rs