[CAPPL-536] Workflow update not picked up by Syncer#80
Merged
Conversation
Contributor
|
@agparadiso Have you run go mod tidy? CI is failing |
agparadiso
force-pushed
the
CAPPL-536_update_not_picked_up_by_syncer_fix
branch
from
9f088d7 to
424a751
Compare
agparadiso
force-pushed
the
CAPPL-536_update_not_picked_up_by_syncer_fix
branch
from
424a751 to
3c49617
Compare
cedric-cordenier
approved these changes
Feb 25, 2025
ettec
approved these changes
Feb 25, 2025
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
3 participants
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.
Description
This pr bumps the
chainlink-commondependency that contains this fix. on the capabilities don the cron trigger need to send an ACK message that the client on the Workflow node will be waiting on