Skip to content

chore: resolve PR #65 conflicts#76

Open
dev-carapulse[bot] wants to merge 25 commits into
feature/pla-1355-erpc-harden-release-workflow-against-version_tag-templatefrom
hermes/pr-65-conflict-resolution
Open

chore: resolve PR #65 conflicts#76
dev-carapulse[bot] wants to merge 25 commits into
feature/pla-1355-erpc-harden-release-workflow-against-version_tag-templatefrom
hermes/pr-65-conflict-resolution

Conversation

@dev-carapulse
Copy link
Copy Markdown

@dev-carapulse dev-carapulse Bot commented May 11, 2026

Summary

Verification

  • git diff --check origin/feature/pla-1355-erpc-harden-release-workflow-against-version_tag-template...HEAD
  • Python YAML parse for .github/workflows/release.yml
  • /tmp/actionlint-1.7.7/actionlint .github/workflows/release.yml

0x666c6f and others added 25 commits May 6, 2026 11:04
Tygo regen was missing after the PLA-1345 upstream sync; generated.ts
referenced X402StrategyConfig without defining it, breaking the docker
build. CI's release workflow runs tygo generate, so the gap was hidden.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
…pc-typescript-config-types-for-x402-strategy

chore(typescript:PLA-1394): regenerate config types for X402 strategy
Refs PLA-1398

Extend the release workflow to publish eRPC and eRPC validator images to Morpho ECR in addition to GHCR.
Refs PLA-1398

Allow the prd-carapulse bot to trigger Claude review and keep the ECR publish workflow changes in the same PR.
…pply-chain-hardening-across-morpho-infra-morpho

ci(erpc:PLA-1349): harden release workflows
…ic-to-1151-and-audit-pgx-stack-for-v5-migration

chore(erpc:PLA-1353): bump sonic to 1.15.1
…-postgres-connector-table-identifiers-to-close

fix(erpc:PLA-1354): validate postgres table identifiers
Remove skipped release preparation jobs from the Docker build job dependencies so morpho-main pushes actually start the image publishing jobs instead of producing a startup_failure check suite.

Use only actions allowed by morpho-org policy by replacing the third-party release PR action with gh commands and using Docker Buildx setup instead of Blacksmith.

Generated with [Devin](https://cli.devin.ai/docs)

Co-Authored-By: Devin <158243242+devin-ai-integration[bot]@users.noreply.github.com>
…artup

fix(release:PLA-1398): unblock docker publish jobs
Add a request directive to probe every selected upstream and return a per-upstream compatibility report.
Addresses inline feedback from automated PR review:

- networks.go: wrap revert/call/transaction-rejected JSON-RPC errors into
  ErrEndpointExecutionException so HasErrorCode detects them and the
  documented "execution exceptions count as success" behavior holds when
  doForward returns (resp with embedded error, nil err).
- networks.go: cloned probe forces SkipCacheRead so EVM hook paths
  (e.g. handleUserMulticall3) can't return a cache hit and report a
  fake upstream success without hitting the wire.
- networks.go: surface jrr parse errors instead of swallowing them.
- networks.go: capture isRetryable from checkUpstreamBlockAvailability
  and expose as RetryableSkip in the diagnostic entry.
- networks.go: switch to errors.As for StandardError code extraction so
  wrapped errors are unwrapped per project guidelines.
- networks.go: add ExecutionExceptions counter so operators can tell
  plain successes from upstreams that reverted with execution data.
- networks.go: AllSucceeded=false when Total==0 (empty fleet was
  misleadingly reporting success).
- networks.go: extract per-upstream probe into helper, log marshal
  failures, use bytes.Clone.
- eth_call.go: skip multicall3 batching when CheckAllUpstreams is set,
  otherwise the directive propagates into the synthetic aggregate3 call
  and probes run twice with confusing fallback warnings.
- common/request.go: directive doc spells out the multiplex/cache/eth_call
  side effects so future maintainers don't strip them.
- request_test.go: move stray ValidateTransactionsRoot doc comment back
  to its function; add directive parsing edge cases and ShouldCheck
  AllUpstreams nil-safety tests.
- networks_check_all_upstreams_test.go: follow project gock guidelines
  (ResetGock first), assert all diagnostic fields, and add coverage for
  the EVM execution-exception path.
- docs: clarify cache-write bypass, multicall3 disable, and that
  allSucceeded does not compare result payloads.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
feat: add all-upstreams diagnostic mode
# Conflicts:
#	.github/workflows/release.yml
@wiz-c998a0ef2b
Copy link
Copy Markdown

Wiz Scan Summary

Scanner Findings
Vulnerability Finding Vulnerabilities -
Data Finding Sensitive Data -
Secret Finding Secrets -
IaC Misconfiguration IaC Misconfigurations -
SAST Finding SAST Findings 1 Medium
Software Management Finding Software Management Findings -
Total 1 Medium

View scan details in Wiz

To detect these findings earlier in the dev lifecycle, try using Wiz Code VS Code Extension.

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