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

v2.0: token-2022: Use mainnet-beta binary in all tools (backport of #3165) #3166

Merged
merged 1 commit into from
Oct 15, 2024

Conversation

mergify[bot]
Copy link

@mergify mergify bot commented Oct 15, 2024

Problem

The binary of token-2022 bundled in program-test and fetch-spl.sh is very out of date with what's currently running on mainnet.

Summary of changes

Update the shared object and version to fetch.

Note: backporting this change to 2.0 only to reflect the current state of the chain. Technically, this could also be backported to 1.18, but people should start adopting the 2.0 tools / crates soon.


This is an automatic backport of pull request #3165 done by Mergify.

#### Problem

The binary of token-2022 bundled in program-test and fetch-spl.sh is
very out of date with what's currently running on mainnet.

#### Summary of changes

Update the shared object and version to fetch.

(cherry picked from commit 9695566)
@mergify mergify bot requested a review from a team as a code owner October 15, 2024 10:00
@joncinque
Copy link

As mentioned in the note in the PR description, the backport is to make solana-test-validator and program-test line up with the program deployed to mainnet.

Copy link

@bw-solana bw-solana left a comment

Choose a reason for hiding this comment

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

LGTM.

My read is this falls into the category of bug fix given how out of date the program is with what's on mainnet, which could lead to devex problems when trying to test with solana-test-validator and program-test. It's also low risk given changes are outside the core validator.

Also agree we don't need to backport to v1.18 given transition to v2.0 is coming soon ™️

@joncinque joncinque merged commit b271f1f into v2.0 Oct 15, 2024
39 checks passed
@joncinque joncinque deleted the mergify/bp/v2.0/pr-3165 branch October 15, 2024 16:52
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.

3 participants