fix: change skipping chains messages to info level [OPT-374]#712
Merged
fix: change skipping chains messages to info level [OPT-374]#712
Conversation
🦋 Changeset detectedLatest commit: e5c239d The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
ecPablo
changed the title
Contributor
There was a problem hiding this comment.
Pull request overview
This PR reduces log verbosity by changing the log level of chain-skipping messages from WARN to DEBUG, addressing log noise issues when chains are intentionally skipped due to missing credentials.
Changes:
- Changed log level from
lggr.Warntolggr.Debugfor all chain-skipping messages across six different blockchain families (EVM, Tron, Solana, Aptos, Sui, and Ton) - Added a changeset documenting this as a patch-level change
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| engine/cld/chains/chains.go | Updated six log statements from WARN to DEBUG level when chains are skipped due to missing configuration |
| .changeset/strong-phones-cheer.md | Added changeset entry documenting the log level reduction |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
ecPablo
changed the title
gustavogama-cll
approved these changes
Feb 5, 2026
|
Merged
github-merge-queue bot
pushed a commit
that referenced
this pull request
Feb 6, 2026
This PR was opened by the [Changesets release](https://github.com/changesets/action) GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated. # Releases ## chainlink-deployments-framework@0.80.0 ### Minor Changes - [#713](#713) [`643bbb7`](643bbb7) Thanks [@bytesizedroll](https://github.com/bytesizedroll)! - refactor: update stale migration terminology to changeset Replace legacy "migration" terminology with "changeset" throughout comments, variable names, and error messages for consistency with durable pipelines. Changes include: - Rename function params: loadMigration → loadChangesets - Rename variables: migDirPath → dirPath, migration → registry - Rename test mocks: mockMigrationDS → mockSourceDS - Update doc comments and error messages - Remove dead commented-out migration test code ### Patch Changes - [#707](#707) [`52eb9f5`](52eb9f5) Thanks [@patricios-space](https://github.com/patricios-space)! - bump chainlink-ton and mcms to bring latest version that uses new exit code interface - [#705](#705) [`50640db`](50640db) Thanks [@bytesizedroll](https://github.com/bytesizedroll)! - remove migration archive functionality - [#709](#709) [`461acc5`](461acc5) Thanks [@ajaskolski](https://github.com/ajaskolski)! - refactor: adds modular cmd for datastore - [#715](#715) [`124dfef`](124dfef) Thanks [@gustavogama-cll](https://github.com/gustavogama-cll)! - chore: add ton to mcms chain access adapter - [#712](#712) [`3584647`](3584647) Thanks [@ecPablo](https://github.com/ecPablo)! - reduce log level of skipping chains logs from WARN to INFO - [#710](#710) [`3c33586`](3c33586) Thanks [@ecPablo](https://github.com/ecPablo)! - fix nil values handling during upf yaml marshalling - [#708](#708) [`d357cb6`](d357cb6) Thanks [@gustavogama-cll](https://github.com/gustavogama-cll)! - fix: run health check and try multiple RPCs in fork tests - [#711](#711) [`a72317e`](a72317e) Thanks [@bytesizedroll](https://github.com/bytesizedroll)! - Rename all "Migration" terminology in domain layer methods to "Changeset" for consistency with durable pipelines terminology. EnvDir: - MergeMigrationDataStore -> MergeChangesetDataStore - MergeMigrationDataStoreCatalog -> MergeChangesetDataStoreCatalog - MergeMigrationAddressBook -> MergeChangesetAddressBook - RemoveMigrationAddressBook -> RemoveChangesetAddressBook ArtifactsDir: - MigrationDirPath -> ChangesetDirPath - CreateMigrationDir -> CreateChangesetDir - RemoveMigrationDir -> RemoveChangesetDir - MigrationDirExists -> ChangesetDirExists - MigrationOperationsReportsFileExists -> ChangesetOperationsReportsFileExists - LoadAddressBookByMigrationKey -> LoadAddressBookByChangesetKey - LoadDataStoreByMigrationKey -> LoadDataStoreByChangesetKey Internal helpers: - loadDataStoreByMigrationKey -> loadDataStoreByChangesetKey - loadAddressBookByMigrationKey -> loadAddressBookByChangesetKey Parameter renames: migKey/migkey -> csKey BREAKING CHANGE: All public domain layer methods with "Migration" in their name have been renamed to use "Changeset" instead. Update all callers to use the new method names. --------- Co-authored-by: app-token-issuer-engops[bot] <144731339+app-token-issuer-engops[bot]@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The skipping chain messages are causing a lot of noise in logs - we are making them debug level to reduce the noise of stack traces in WARN level. Rationale behind making the
INFOis that skipping chains will be a common thing in most domains. Only CCIP ha support of all non evm chains now.