Skip to content

ci: point release-gate AMOY_RPC at eRPC — public amoy endpoint retired - #92

Merged
shan8851 merged 1 commit into
masterfrom
ci/release-gate-amoy-erpc
Aug 13, 2026
Merged

ci: point release-gate AMOY_RPC at eRPC — public amoy endpoint retired#92
shan8851 merged 1 commit into
masterfrom
ci/release-gate-amoy-erpc

Conversation

@shan8851

Copy link
Copy Markdown
Contributor

The Docker release gate's AMOY_RPC still pointed at rpc-amoy.polygon.technology, which no longer resolves (retired); ci-trigger.yml had already moved to the eRPC URL, which is why PR CI stayed green while every release-tag run for 2.0.0 failed (5×, run 31686169287 + rc proofs). One-line swap to the same eRPC pattern as the other three chains, plus the MD022 changelog lint fix that was blocking CI.

After merge: no new version needed — re-dispatch the existing proof-generation-api@2.0.0 tag (workflow_dispatch uses this fixed workflow from master while building the tag's code). Supersedes the warm-up approach in #91.

🤖 Generated with Claude Code

ci-trigger.yml already used the eRPC URL; docker-release-trigger.yml was the only consumer of rpc-amoy.polygon.technology, which no longer resolves. This is why CI stayed green while every release-tag run failed. Also fixes the MD022 lint error in the 2.0.0 changelog entry that blocked CI.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@shan8851
shan8851 marked this pull request as ready for review August 13, 2026 10:53
@shan8851
shan8851 merged commit 56c3360 into master Aug 13, 2026
8 of 9 checks passed
@shan8851
shan8851 deleted the ci/release-gate-amoy-erpc branch August 13, 2026 10:54
@claude

claude Bot commented Aug 13, 2026

Copy link
Copy Markdown

Code review

No issues found. Checked for bugs and CLAUDE.md compliance.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant