Skip to content

[pull] develop from smartcontractkit:develop - #569

Merged
pull[bot] merged 9 commits into
bit-cook:developfrom
smartcontractkit:develop
Aug 25, 2026
Merged

[pull] develop from smartcontractkit:develop#569
pull[bot] merged 9 commits into
bit-cook:developfrom
smartcontractkit:develop

Conversation

@pull

@pull pull Bot commented Aug 25, 2026

Copy link
Copy Markdown

See Commits and Changes for more details.


Created by pull[bot] (v2.0.0-alpha.4)

Can you help keep this open source service alive? 💖 Please sponsor : )

jmank88 and others added 9 commits August 25, 2026 13:47
* core/services/gateway: gate user traffic on relay readiness

* core/services/gateway: use generic DON readiness terms

* core/services/gateway/connectionmanager.go: describe traffic readiness threshold

* core/services/gateway: log disconnected readiness nodes

* core/services/gateway/network: fix readiness test lint

* core/services/gateway/monitoring/metrics_test.go: keep readiness metrics test serial
#23524)

* plugins/plugins.public.yaml: update confidential plugin refs for 1.4.0

* fix test

---------

Co-authored-by: vreff <104409744+vreff@users.noreply.github.com>
…#23407)

* add fetch on demand ref resolution for changelog script

* normalize ccip image tag formatting to actual git tags

* make more product-agnostic

* lint
…#23514)

* fix: wrapp user errors on vaultSecretError to avoid misclassification as system errors

* fix: keep vault system errors classified as internal (#23517)

* fix: keep vault system errors classified as internal

The vault OCR plugin already classifies per-secret failures via
userFacingError: user errors surface their raw message, while system
failures are replaced with a generic fallback ("failed to handle get
secret request"). That classification is lost at the protobuf
SecretResponse.error string boundary, so the relay handler cannot
recover the Go type.

vaultSecretError.Unwrap previously returned a *vaulttypes.UserError
unconditionally, which made IsUserError true for every per-secret
error — including the system fallback. A KV-store outage or decryption
failure would have been mapped to jsonrpc.ErrInvalidParams (a user
error) instead of ErrInternal, suppressing system-error alerts: the
opposite of the intended fix.

Export the fallback as vaulttypes.SecretGetSystemErrorFallback so the
vault plugin and relay handler share one marker, and have Unwrap return
nil for that message so IsUserError reports false. User errors still
unwrap to a UserError and map to ErrInvalidParams; system errors keep
falling through to ErrInternal.

Co-Authored-By: Claude <noreply@anthropic.com>

* fix lint

---------

Co-authored-by: Claude <noreply@anthropic.com>

* fix lint 2

* fix lint

* chore: add explicit isUser flag

* get rid of useless wrapper

* fix lint

---------

Co-authored-by: vreff <104409744+vreff@users.noreply.github.com>
Co-authored-by: Claude <noreply@anthropic.com>
* lint(core/capabilities/ccip/ccipsolana): fix violations (batch_003)

* lint(core/capabilities/ccip): fix violations (batch_004)

* lint: ccipocr3 rename

* lint
* core: misc fixes

* feedback
bump pinned curl version
@pull pull Bot locked and limited conversation to collaborators Aug 25, 2026
@pull pull Bot added the ⤵️ pull label Aug 25, 2026
@pull
pull Bot merged commit 87e7c13 into bit-cook:develop Aug 25, 2026
10 of 18 checks passed
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants