Update Sui go mod

[stackman27]

Requires

Supports

[github-actions]

👋 stackman27, thanks for creating this pull request!

To help reviewers, please consider creating future PRs as drafts first. This allows you to self-review and make any final changes before notifying the team.

Once you're ready, you can mark it as "Ready for review" to request feedback. Thanks!

[github-actions]

I see you updated files related to core. Please run pnpm changeset 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

This pull request updates the chainlink-sui dependency across the codebase from version v0.0.0-20260217210647-11c42009ec1f to v0.0.0-20260210215559-36077b5fee17, effectively downgrading it by 7 days. The change is applied consistently across all go.mod and go.sum files in various modules (main, integration-tests, deployment, system-tests, core/scripts, and load tests). The plugins configuration file has also been updated with helpful comments about consulting the chainlink-sui team before version updates.

Changes:

• Downgraded chainlink-sui dependency from Feb 17, 2026 version to Feb 10, 2026 version across all modules
• Updated plugins.public.yaml with new version reference and added warning comments
• Synchronized go.sum files across all affected modules

Reviewed changes

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

Show a summary per file

File	Description
go.mod	Updated main module's chainlink-sui dependency to earlier version
go.sum	Updated checksums for new chainlink-sui version in main module
deployment/go.mod	Updated chainlink-sui dependency in deployment module
deployment/go.sum	Updated checksums for new chainlink-sui version in deployment module
core/scripts/go.mod	Updated chainlink-sui dependency in core scripts module
core/scripts/go.sum	Updated checksums for new chainlink-sui version in core scripts module
integration-tests/go.mod	Updated chainlink-sui dependency in integration tests module
integration-tests/go.sum	Updated checksums for new chainlink-sui version in integration tests module
integration-tests/load/go.mod	Updated chainlink-sui dependency in load tests module
integration-tests/load/go.sum	Updated checksums for new chainlink-sui version in load tests module
system-tests/lib/go.mod	Updated chainlink-sui dependency in system tests lib module
system-tests/lib/go.sum	Updated checksums for new chainlink-sui version in system tests lib module
system-tests/tests/go.mod	Updated chainlink-sui dependency in system tests module
system-tests/tests/go.sum	Updated checksums for new chainlink-sui version in system tests module
plugins/plugins.public.yaml	Updated gitRef for sui plugin with version comments and team consultation warning

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

Version mismatch: The main chainlink-sui package has been downgraded to v0.0.0-20260210215559-36077b5fee17, but the chainlink-sui/deployment subpackage remains at v0.0.0-20260217210647-11c42009ec1f (7 days newer). This creates an inconsistency where the deployment subpackage is from a later date than its parent package. This pattern is repeated across all go.mod files (integration-tests, system-tests, etc.). Consider whether the deployment subpackage should also be downgraded to match the main package version, or if there's a specific reason for this version mismatch.

Suggested change

	github.com/smartcontractkit/chainlink-sui/deployment v0.0.0-20260217210647-11c42009ec1f
	github.com/smartcontractkit/chainlink-sui/deployment v0.0.0-20260210215559-36077b5fee17

[Copilot]

Version mismatch: The main chainlink-sui package has been downgraded to v0.0.0-20260210215559-36077b5fee17, but the chainlink-sui/deployment subpackage remains at v0.0.0-20260217210647-11c42009ec1f (7 days newer). This creates an inconsistency where the deployment subpackage is from a later date than its parent package. Consider whether the deployment subpackage should also be downgraded to match the main package version, or if there's a specific reason for this version mismatch.

Suggested change

	github.com/smartcontractkit/chainlink-sui/deployment v0.0.0-20260217210647-11c42009ec1f
	github.com/smartcontractkit/chainlink-sui/deployment v0.0.0-20260210215559-36077b5fee17

[trunk-io]

     

Failed Test	Failure Summary	Logs
TestScripts/health/multi-chain-loopp	The test failed because it could not connect to the local server on the specified port, indicating the server did not start or was unreachable.	Logs ↗︎
TestScripts/health/multi-chain-loopp	The test failed because the server did not start or respond on the expected port, causing connection attempts to fail.	Logs ↗︎
TestScripts/health/multi-chain-loopp	The test failed because it couldn't connect to the local server on the specified port.	Logs ↗︎
TestScripts/health/multi-chain-loopp	The test failed because it couldn't connect to the local server on port 14101, causing the health check to fail.	Logs ↗︎

... and 4 more

View Full Report ↗︎ ⋅ Docs

[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