Fix R2 sync region: force AWS_REGION=auto for Cloudflare endpoint#407
Merged
Conversation
The configure-aws-credentials step exports AWS_REGION=us-west-1 into the job env for the S3 artifact publish. The AWS CLI prefers AWS_REGION over AWS_DEFAULT_REGION, so the R2 sync inherited us-west-1 and R2 rejected it (InvalidRegionName; R2 only accepts auto/wnam/enam/...). Override AWS_REGION=auto in the step env and pass --region auto explicitly (CLI flag wins regardless of env precedence) on both the dev and prod sync steps. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
AOT Provider Analysis (aot.yml) and Integration Testing and Analysis (regression.yml) are merge gates. They ran on both pull_request and push to main/dev, so every merge re-ran the same expensive suite that already passed on the PR. Drop the branch entries from their push triggers, keeping pull_request (the gate) and the tag triggers (aot*/robot*/regression*/integration* on-demand runs). No push/main-only publish exists in either workflow - their publish steps are gated on IS_TAG/ref_type == 'tag', which is unaffected. main.yml is unchanged: it must run on push to deploy, and its heavy steps are already gated on NUM_PROVIDERS > 0. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
stackql-core is built from main and its go.mod now requires go >= 1.25.3, but the workflows requested ~1.22. The newer setup-go (bumped to silence Node 20 warnings) sets GOTOOLCHAIN=local, so it would not auto-download a newer toolchain and the "Build stackql from core source" step failed with "go.mod requires go >= 1.25.3 (running go 1.22.12)". Use GO_VERSION: stable in aot.yml and regression.yml. go.mod requirements only ever name released Go versions, so the latest stable always satisfies them (including future core bumps) and works with GOTOOLCHAIN=local. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The configure-aws-credentials step exports AWS_REGION=us-west-1 into the job env for the S3 artifact publish. The AWS CLI prefers AWS_REGION over AWS_DEFAULT_REGION, so the R2 sync inherited us-west-1 and R2 rejected it (InvalidRegionName; R2 only accepts auto/wnam/enam/...). Override AWS_REGION=auto in the step env and pass --region auto explicitly (CLI flag wins regardless of env precedence) on both the dev and prod sync steps.