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

sdk: Add deprecation warning to solana_program::nonce #3479

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

joncinque
Copy link

Problem

As pointed out at
#3370 (comment), the solana-nonce crate re-export in solana-program does not have a deprecated warning.

Summary of changes

Add the warning.

Note: for usage of solana-nonce in a BPF implementation of the system program, this will be backported after #3370 lands.

#### Problem

As pointed out at
anza-xyz#3370 (comment),
the solana-nonce crate re-export in solana-program does not have a
deprecated warning.

#### Summary of changes

Add the warning.
@joncinque joncinque added the v2.1 Backport to v2.1 branch label Nov 5, 2024
@joncinque joncinque requested a review from t-nelson November 5, 2024 11:29
Copy link

mergify bot commented Nov 5, 2024

Backports to the beta branch are to be avoided unless absolutely necessary for fixing bugs, security issues, and perf regressions. Changes intended for backport should be structured such that a minimum effective diff can be committed separately from any refactoring, plumbing, cleanup, etc that are not strictly necessary to achieve the goal. Any of the latter should go only into master and ride the normal stabilization schedule. Exceptions include CI/metrics changes, CLI improvements and documentation updates on a case by case basis.

@joncinque joncinque removed the v2.1 Backport to v2.1 branch label Nov 7, 2024
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.

1 participant