Safia AbdallaandOz Agent
e20fa7a86e
## Description The reusable workflows under [`warpdotdev/oz-for-oss`](https://github.com/warpdotdev/oz-for-oss/tree/main/.github/workflows) declare their Warp API key secret as `OSS_WARP_API_KEY`, but the local caller workflows in this repo were forwarding it as `WARP_API_KEY`. Because the name being passed didn't match the name declared by `workflow_call`, the required secret was effectively missing and an undeclared secret was being passed instead, which caused `startup_failure` on every invocation. Example failure: https://github.com/warpdotdev/warp/actions/runs/25058665906 (Triage New Issues (Local), `startup_failure`). This PR renames the forwarded secret to `OSS_WARP_API_KEY:` in all local adapter workflows so the names match what the reusable workflows declare. The underlying secret value is still pulled from `secrets.OSS_WARP_API_KEY` in this repo, so no repo secret changes are needed. Affected workflows: - `.github/workflows/create-implementation-from-issue-local.yml` - `.github/workflows/create-spec-from-issue-local.yml` - `.github/workflows/enforce-pr-issue-state.yml` - `.github/workflows/respond-to-pr-comment-local.yml` - `.github/workflows/respond-to-triaged-issue-comment-local.yml` - `.github/workflows/review-pull-request.yml` - `.github/workflows/triage-new-issues-local.yml` - `.github/workflows/trigger-implementation-on-plan-approved-local.yml` - `.github/workflows/update-dedupe-local.yml` - `.github/workflows/update-pr-review-local.yml` - `.github/workflows/update-triage-local.yml` - `.github/workflows/verify-pr-comment-local.yml` ## Testing Manual review of the rename. After merge, re-run the failing `Triage New Issues (Local)` workflow to confirm it no longer hits `startup_failure` due to a missing required secret. ## Server API dependencies N/A — CI workflow change only. ## Agent Mode - [x] Warp Agent Mode - This PR was created via Warp's AI Agent Mode _Conversation: https://staging.warp.dev/conversation/fbace74a-9da2-445f-8486-e5a5907dce57_ _Run: https://oz.staging.warp.dev/runs/019dd47c-42e0-7072-8206-e6be4df5cde7_ _This PR was generated with [Oz](https://warp.dev/oz)._ Co-authored-by: Oz Agent <oz-agent@warp.dev>
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.