Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CCIP - Version based changesets #16504

Merged
merged 7 commits into from
Feb 21, 2025
Merged

CCIP - Version based changesets #16504

merged 7 commits into from
Feb 21, 2025

Conversation

AnieeG
Copy link
Contributor

@AnieeG AnieeG commented Feb 21, 2025

Ensures that each versioned folders use specific versioned contracts

Copy link
Contributor

github-actions bot commented Feb 21, 2025

AER Report: CI Core ran successfully ✅

aer_workflow , commit

AER Report: Operator UI CI ran successfully ✅

aer_workflow , commit

bukata-sa
bukata-sa previously approved these changes Feb 21, 2025
Comment on lines 21 to 22
"github.com/smartcontractkit/chainlink/deployment/ccip/changeset"
cs "github.com/smartcontractkit/chainlink/deployment/ccip/changeset"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

duplicate import

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Shouldn't we put the solana directory under v1_6? Or only after their contracts are frozen?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can discuss with solana team and create a new PR for that

@@ -49,7 +50,7 @@ type TestConfigs struct {
// TODO: This should be CreateContracts so the booleans make sense?
CreateJobAndContracts bool
PrerequisiteDeploymentOnly bool
V1_5Cfg changeset.V1_5DeploymentConfig
V1_5Cfg v1_6.V1_5DeploymentConfig
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Kinda odd to have V1_5DeploymentConfig in the v1_6 package no?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

oh right. good catch. I should move this changeset DeployPrerequisite to common. It deploys a mix of all 1.2, 1.5, 1.6

@AnieeG AnieeG enabled auto-merge February 21, 2025 17:32
@AnieeG AnieeG added this pull request to the merge queue Feb 21, 2025
Merged via the queue into develop with commit bedf941 Feb 21, 2025
183 of 184 checks passed
@AnieeG AnieeG deleted the cs-versions branch February 21, 2025 18:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants