warning: unexpected `cfg` condition value: `anchor-debug` --> programs/example_program/src/lib.rs:5:1 | 5 | #[program] | ^^^^^^^^^^ | = note: expected values for `feature` are: `cpi`, `default`, `idl-build`, `no-entrypoint`, `no-idl`, and `no-log-ix-name` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `program` crate for guidance on how handle this unexpected cfg = help: the attribute macro `program` may come from an old version of the `anchor_attribute_program` crate, try updating your dependency with `cargo update -p anchor_attribute_program` = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration = note: `#[warn(unexpected_cfgs)]` on by default = note: this warning originates in the attribute macro `program` (in Nightly builds, run with -Z macro-backtrace for more info)

warning: unexpected `cfg` condition value: `anchor-debug` --> programs/example_program/src/lib.rs:5:1 | 5 | #[program] | ^^^^^^^^^^ | = note: expected values for `feature` are: `cpi`, `default`, `idl-build`, `no-entrypoint`, `no-idl`, and `no-log-ix-name` = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `Accounts` crate for guidance on how handle this unexpected cfg = help: the derive macro `Accounts` may come from an old version of the `anchor_derive_accounts` crate, try updating your dependency with `cargo update -p anchor_derive_accounts` = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration = note: this warning originates in the derive macro `Accounts` (in Nightly builds, run with -Z macro-backtrace for more info)

warning: unexpected `cfg` condition value: `anchor-debug` --> programs/example_program/src/lib.rs:5:1 | 5 | #[program] | ^^^^^^^^^^ | = note: expected values for `feature` are: `cpi`, `default`, `idl-build`, `no-entrypoint`, `no-idl`, and `no-log-ix-name` = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `Accounts` crate for guidance on how handle this unexpected cfg = help: the derive macro `Accounts` may come from an old version of the `anchor_derive_accounts` crate, try updating your dependency with `cargo update -p anchor_derive_accounts` = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration = note: this warning originates in the derive macro `Accounts` (in Nightly builds, run with -Z macro-backtrace for more info)

warning: unexpected `cfg` condition value: `anchor-debug` --> programs/example_program/src/lib.rs:5:1 | 5 | #[program] | ^^^^^^^^^^ | = note: expected values for `feature` are: `cpi`, `default`, `idl-build`, `no-entrypoint`, `no-idl`, and `no-log-ix-name` = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `Accounts` crate for guidance on how handle this unexpected cfg = help: the derive macro `Accounts` may come from an old version of the `anchor_derive_accounts` crate, try updating your dependency with `cargo update -p anchor_derive_accounts` = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration = note: this warning originates in the derive macro `Accounts` (in Nightly builds, run with -Z macro-backtrace for more info)

warning: unexpected `cfg` condition value: `anchor-debug` --> programs/example_program/src/lib.rs:5:1 | 5 | #[program] | ^^^^^^^^^^ | = note: expected values for `feature` are: `cpi`, `default`, `idl-build`, `no-entrypoint`, `no-idl`, and `no-log-ix-name` = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `Accounts` crate for guidance on how handle this unexpected cfg = help: the derive macro `Accounts` may come from an old version of the `anchor_derive_accounts` crate, try updating your dependency with `cargo update -p anchor_derive_accounts` = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration = note: this warning originates in the derive macro `Accounts` (in Nightly builds, run with -Z macro-backtrace for more info)

warning: unexpected `cfg` condition value: `anchor-debug` --> programs/example_program/src/lib.rs:5:1 | 5 | #[program] | ^^^^^^^^^^ | = note: expected values for `feature` are: `cpi`, `default`, `idl-build`, `no-entrypoint`, `no-idl`, and `no-log-ix-name` = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `Accounts` crate for guidance on how handle this unexpected cfg = help: the derive macro `Accounts` may come from an old version of the `anchor_derive_accounts` crate, try updating your dependency with `cargo update -p anchor_derive_accounts` = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration = note: this warning originates in the derive macro `Accounts` (in Nightly builds, run with -Z macro-backtrace for more info)

warning: unexpected `cfg` condition value: `anchor-debug` --> programs/example_program/src/lib.rs:5:1 | 5 | #[program] | ^^^^^^^^^^ | = note: expected values for `feature` are: `cpi`, `default`, `idl-build`, `no-entrypoint`, `no-idl`, and `no-log-ix-name` = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `Accounts` crate for guidance on how handle this unexpected cfg = help: the derive macro `Accounts` may come from an old version of the `anchor_derive_accounts` crate, try updating your dependency with `cargo update -p anchor_derive_accounts` = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration = note: this warning originates in the derive macro `Accounts` (in Nightly builds, run with -Z macro-backtrace for more info)

warning: unexpected `cfg` condition value: `anchor-debug` --> programs/example_program/src/lib.rs:20:10 | 20 | #[derive(Accounts)] | ^^^^^^^^ | = note: expected values for `feature` are: `cpi`, `default`, `idl-build`, `no-entrypoint`, `no-idl`, and `no-log-ix-name` = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `Accounts` crate for guidance on how handle this unexpected cfg = help: the derive macro `Accounts` may come from an old version of the `anchor_derive_accounts` crate, try updating your dependency with `cargo update -p anchor_derive_accounts` = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration = note: this warning originates in the derive macro `Accounts` (in Nightly builds, run with -Z macro-backtrace for more info)

warning: unexpected `cfg` condition value: `anchor-debug` --> programs/example_program/src/lib.rs:26:10 | 26 | #[derive(Accounts)] | ^^^^^^^^ | = note: expected values for `feature` are: `cpi`, `default`, `idl-build`, `no-entrypoint`, `no-idl`, and `no-log-ix-name` = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `Accounts` crate for guidance on how handle this unexpected cfg = help: the derive macro `Accounts` may come from an old version of the `anchor_derive_accounts` crate, try updating your dependency with `cargo update -p anchor_derive_accounts` = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration = note: this warning originates in the derive macro `Accounts` (in Nightly builds, run with -Z macro-backtrace for more info)