---
title: "Record from CI without a stored record key"
description: "Your CI jobs can now record to Currents with their OIDC token. No CURRENTS_RECORD_KEY secret to store, leak or rotate."
canonical: "https://currents.dev/changelog/record-from-ci-without-a-record-key"
updated: "2026-11-16"
---

# Record from CI without a stored record key

2026-11-16, New (tracks: platform, reporters, cli)

Your CI jobs can now record to Currents with their OIDC token. No CURRENTS_RECORD_KEY secret to store, leak or rotate.

---


A record key stored in CI secrets is a long-lived credential. If it shows up in a log or a shared pipeline config, anyone who has it can record to your organization until an admin deletes it. Rotating it means updating every repository and pipeline that uses it.

With OIDC there is no secret to store or rotate. Every key is short-lived, and you decide in one place which repositories and pipelines can record. Removing a trust policy revokes every key it issued.

Each job exchanges its CI provider's OIDC token for a record key that expires after 6 hours. Org admins choose which repositories and pipelines can record by adding a trust policy under Organization → API and Record Keys.

Works with GitHub Actions, GitLab.com, CircleCI, Buildkite and Bitbucket Pipelines.

## Required versions

- `@currents/playwright` 2.8.0+ (Playwright 1.62+ when you run `npx playwright test`; `pwc` also works with older Playwright versions)
- `@currents/cmd` 3.1.0+ for Jest and node:test uploads
- `currents-dev/cancel-run-gh-action` 1.2.0+ and `currents-dev/playwright-last-failed` 2.2.0+

Setup for each provider: [Record from CI with OIDC](https://docs.currents.dev/guides/record-key/record-from-ci-with-oidc)

