Bump chainlink-aptos for Aptos account tx window fix

[cawthorne]

Summary

• bump the public chainlink-aptos plugin pin to v0.0.0-20260430175646-295a7f9a1500 (smartcontractkit/chainlink-aptos@295a7f9)
• sync the chainlink-aptos Go module pin to the same merged version across Chainlink's Go modules
• include the transitive go.uber.org/zap v1.28.0 bump required by the updated chainlink-aptos module
• consume the merged fix from Fix Aptos account transaction limit windows chainlink-aptos#449 for limit-only Aptos account transaction queries

Context

The CRE Aptos write/read roundtrip merge-queue job failed because the Aptos capability requested recent transmitter account transactions with start=nil, limit=N. The previously pinned relayer passed that shape through to the Aptos SDK, which can underflow the previous-page cursor for accounts with fewer than N transactions and issue REST calls with start=18446744073709551615.

The exposure came from the Aptos capability tx-search path switching its phase-1 probe to a bounded latest-page request (start=nil, limit=10). The relayer fix resolves that limit-only request into an explicit latest transaction window before calling the Aptos SDK.

Failing job investigated: https://github.com/smartcontractkit/chainlink/actions/runs/25151620823/job/73724531635

Why Multiple Files Changed

This PR does not change Chainlink source code. The diff is dependency metadata only.

Chainlink has multiple Go modules that either directly or indirectly pin github.com/smartcontractkit/chainlink-aptos: root, deployment, integration-tests, integration-tests/load, system-tests/lib, system-tests/tests, and core/scripts. Updating only the root module and plugin manifest would leave some CI/test paths on the old relayer version, so the module pins and sums are updated consistently.

Upstream Fix

• Fix Aptos account transaction limit windows chainlink-aptos#449 is merged
• merged commit: smartcontractkit/chainlink-aptos@295a7f9
• module pseudo-version used here: v0.0.0-20260430175646-295a7f9a1500

Testing

• make gomodtidy
• go run ./tools/plugout --go-mod ./go.mod --plugin-file ./plugins/plugins.public.yaml
• git diff --check
• upstream relayer test from Fix Aptos account transaction limit windows chainlink-aptos#449: go test ./relayer -count=1

Also includes commits from:
#22272

To unblock the failing ccip solana test.

[github-actions]

✅ No conflicts with other open PRs targeting develop

[trunk-io]

     

View Full Report ↗︎ ⋅ Docs

[github-actions]

I see you updated files related to core. Please run make gocs in the root directory to add a changeset as well as in the text include at least one of the following tags:

• #added For any new functionality added.
• #breaking_change For any functionality that requires manual action for the node to boot.
• #bugfix For bug fixes.
• #changed For any change to the existing functionality.
• #db_update For any feature that introduces updates to database schema.
• #deprecation_notice For any upcoming deprecation functionality.
• #internal For changesets that need to be excluded from the final changelog.
• #nops For any feature that is NOP facing and needs to be in the official Release Notes for the release.
• #removed For any functionality/config that is removed.
• #updated For any functionality that is updated.
• #wip For any change that is not ready yet and external communication about it should be held off till it is feature complete.

[Copilot]

Pull request overview

Risk Rating: LOW

This PR updates Chainlink’s pinned chainlink-aptos relayer/plugin version to consume the upstream fix for limit-only Aptos account transaction queries, and aligns the corresponding Go module pins across the repo’s multi-module setup.

Changes:

• Bump github.com/smartcontractkit/chainlink-aptos to v0.0.0-20260430175646-295a7f9a1500 across all relevant Go modules and the public plugins manifest.
• Bump go.uber.org/zap to v1.28.0 where required by the updated dependency graph.
• Refresh go.sum files to match the new module versions/hashes.

Areas requiring scrupulous human review:

• Confirm the pinned chainlink-aptos pseudo-version maps to the intended upstream commit (295a7f9a1500...) referenced in the PR description and that it contains the expected fix behavior.
• Confirm plugin installation workflows that consume plugins/plugins.public.yaml behave as expected with the updated gitRef.

Reviewed changes

Copilot reviewed 8 out of 15 changed files in this pull request and generated no comments.

Show a summary per file

File	Description
go.mod	Bumps root module pins for chainlink-aptos and zap.
go.sum	Updates root module sums for chainlink-aptos and zap.
deployment/go.mod	Aligns deployment module pins for chainlink-aptos and zap.
deployment/go.sum	Updates deployment module sums for the bumped dependencies.
integration-tests/go.mod	Aligns integration-tests module pins for chainlink-aptos and zap.
integration-tests/go.sum	Updates integration-tests module sums for the bumped dependencies.
integration-tests/load/go.mod	Aligns load-tests module pins for chainlink-aptos and zap (indirect).
integration-tests/load/go.sum	Updates load-tests module sums for the bumped dependencies.
system-tests/lib/go.mod	Aligns system-tests lib module pins for chainlink-aptos and zap.
system-tests/lib/go.sum	Updates system-tests lib module sums for the bumped dependencies.
system-tests/tests/go.mod	Aligns system-tests tests module pin for chainlink-aptos and zap (indirect).
system-tests/tests/go.sum	Updates system-tests tests module sums for the bumped dependencies.
core/scripts/go.mod	Aligns core/scripts module pins for chainlink-aptos (indirect) and zap.
core/scripts/go.sum	Updates core/scripts module sums for the bumped dependencies.
plugins/plugins.public.yaml	Updates public aptos plugin gitRef to the new chainlink-aptos pseudo-version.

[cawthorne]

Seems to be blocked by this (potentially unrelated) Solana tests:
https://github.com/smartcontractkit/chainlink/actions/runs/25181157355/job/73826561639?pr=22264

[github-actions]

CORA - Pending Reviewers

All codeowners have approved! ✅

Legend: ✅ Approved | ❌ Changes Requested | 💬 Commented | 🚫 Dismissed | ⏳ Pending | ❓ Unknown

For more details, see the full review summary.

[cl-sonarqube-production]

Quality Gate failed

Failed conditions
67.2% Duplication on New Code (required ≤ 10%)

See analysis details on SonarQube