David Stern
21cb7e56d1
## Description PRs from external forks have been failing CI because `google-github-actions/auth` cannot complete OIDC auth: our GCP Workload Identity Federation provider only trusts the base repository, so the OIDC token issued for a fork-PR run (which carries the fork's `repository` claim) is rejected. See [run #25071797593](https://github.com/warpdotdev/warp/actions/runs/25071797593/job/73455200680?pr=9280) for an example failure. The auth is only needed by SSH integration tests, which use `gcloud compute start-iap-tunnel` to reach a GCP-hosted Ubuntu VM. As a short-term unblock, this skips the `auth` and `setup-gcloud` steps on fork-PR runs and filters the SSH-dependent tests out of the test runs (they all match `_ssh_` in their test names). All other tests continue to run as before, and SSH integration coverage is unchanged on `master`, `workflow_dispatch`, `workflow_call`, and same-repo PRs — those tests still validate post-merge. A more complete fix (e.g. a `workflow_run`-triggered job that runs SSH tests in the base repo's context against the fork's SHA) is a possible follow-up if we decide fork PRs need full SSH coverage. ## Testing Validated via YAML parse. Will verify behavior on this PR's CI run (same-repo PR — SSH tests should still run) and on a fork PR before relying on it. ## Server API dependencies N/A — CI-only change. ## Agent Mode - [x] Warp Agent Mode - This PR was created via Warp's AI Agent Mode
Release Configurations
This README file documents the format of the release_configurations.json file located in this directory. The file defines Warp's various release channels, and provides values for the various variables that are necessary to run the create_new_releases.yml GitHub workflow.
At some point, we may want to replace this document with a JSON schema file (which could be used to validate the correctness of the configuration as part of PR presubmit).
Fields
- channel: The channel's unique identifier
- type: The release cadence. At present, the valid values are "nightly" or "weekly".
- is_prerelease: If true, the GitHub release for this channel will be marked as prerelease.
- is_autopush: If true, this channel uses the "latest" keyword in
channel_versions.jsonto automatically deploy new release candidates. Non-autopush channels require a manual change in order to deploy them. - release_base_name: The base name of GitHub releases created for this channel.
- release_body_text: The body text for GitHub releases created for this channel.
- sentry_project: Which Sentry project should receive crash and error reports for this channel.
- sentry_environment: The Sentry environment that corresponds to this channel.
- changelog_slack_channel: The Slack channel where new changelogs will be posted whenever a new release candidates is cut.
- gcs_cache_control_value: The value of the cache-control response header for release DMGs.
- IMPORTANT!!: the value of the cache-control header must be all lowercase; uppercase values will not be respected by Cloud CDN.