Bump cl-solana ref

[ogtownsend]

Bump for this PR: smartcontractkit/chainlink-solana#1555

[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.

[github-actions]

✅ No conflicts with other open PRs targeting develop

[trunk-io]

     

View Full Report ↗︎ ⋅ Docs

[ajarcoronet5415-commits]

Hi! Professional smart contract auditor. 32+ findings across major DeFi protocols. Portfolio: https://ajarcoronet5415-commits.github.io/security-audit-portfolio/ - AGX

[ajarcoronet5415-commits]

Hi! Professional smart contract auditor. 32+ findings. Portfolio: https://ajarcoronet5415-commits.github.io/security-audit-portfolio/ - AGX

[Copilot]

Pull request overview

Risk Rating: LOW — this PR is a straightforward dependency ref bump (no functional code changes in this repo), but it does impact which chainlink-solana revision gets built/used by integration/system tests and plugin installation.

This PR bumps the github.com/smartcontractkit/chainlink-solana dependency and keeps the plugin install manifest in sync with go.mod, aligning this repo with the referenced upstream change (chainlink-solana PR #1555).

Changes:

• Bump github.com/smartcontractkit/chainlink-solana from v1.1.2-0.20260506142558-6d6e28042110 to v1.1.2-0.20260511210120-d8089350d729.
• Update plugins/plugins.public.yaml gitRef to match the root go.mod (so the plugout “Plugins Sync Check” remains green).
• Regenerate/update relevant go.sum entries across submodules that resolve the dependency.

Scrupulous human review recommended (targeted):

• Confirm the upstream chainlink-solana change set (PR #1555) is compatible with the expected plugin install/build behavior and any Solana-focused integration/system tests.

Reviewed changes

Copilot reviewed 5 out of 12 changed files in this pull request and generated no comments.

Show a summary per file

File	Description
system-tests/tests/go.sum	Updates chainlink-solana sum entries to the new pseudo-version.
system-tests/lib/go.sum	Updates chainlink-solana sum entries to the new pseudo-version.
plugins/plugins.public.yaml	Updates Solana plugin gitRef to the new pseudo-version to stay in sync with go.mod.
integration-tests/load/go.sum	Updates chainlink-solana sum entries to the new pseudo-version.
integration-tests/load/go.mod	Bumps indirect chainlink-solana requirement to the new pseudo-version.
integration-tests/go.sum	Updates chainlink-solana sum entries to the new pseudo-version.
integration-tests/go.mod	Bumps indirect chainlink-solana requirement to the new pseudo-version.
go.sum	Updates root module chainlink-solana sum entries to the new pseudo-version.
go.mod	Bumps root module chainlink-solana requirement to the new pseudo-version.
deployment/go.sum	Updates chainlink-solana sum entries to the new pseudo-version.
deployment/go.mod	Bumps deployment module chainlink-solana requirement to the new pseudo-version.
core/scripts/go.sum	Updates chainlink-solana sum entries to the new pseudo-version.

[jmank88]

You might need to update to get the test fix

[cl-sonarqube-production]

Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarQube