upgrade to anchor 0.32, 2.2 solana crates

[cavemanloverboy]

problem:
cli cannot use ledger stax bc repo has old solana-remote-wallet crate without the stax PIDs

solution:
upgrade anchor/solana, which is needed to get new solana-remote-wallet which has the stax PIDs

[vercel]

@cavemanloverboy is attempting to deploy a commit to the squads Team on Vercel.

A member of the Team first needs to authorize it.

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	cargo/​solana-address-lookup-table-interface@​2.2.2
	cargo/​solana-borsh@​2.2.1
	cargo/​solana-message@​2.4.0
	cargo/​anchor-lang@​0.32.1
	cargo/​anchor-spl@​0.32.1
	cargo/​solana-security-txt@​1.1.2
	cargo/​solana-program@​1.18.26 ⏵ 2.3.0	+12		-7
	cargo/​solana-rpc-client-api@​1.18.26 ⏵ 2.3.13
	cargo/​solana-rpc-client@​1.18.26 ⏵ 2.3.13

View full report

[socket-security]

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert  (click "▶" to expand/collapse)
Warn		License policy violation: cargo hidapi under HIDAPI License: HIDAPI - the applicable license policy does not allow this license (4) (hidapi-2.6.4/etc/hidapi/LICENSE-orig.txt) License: GPL-3.0 - the applicable license policy does not allow this license (4) (hidapi-2.6.4/etc/hidapi/LICENSE-gpl3.txt) License: GPL-3.0-only - the applicable license policy does not allow this license (4) (hidapi-2.6.4/build.rs) From: ? → cargo/[email protected] ℹ Read more on: This package | This alert | What is a license policy violation? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected]. Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore cargo/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		License policy violation: cargo icu_properties_data under Unicode-3.0 License: Unicode-3.0 - the applicable license policy does not allow this license (4) (icu_properties_data-2.1.2/LICENSE) License: Unicode-3.0 - the applicable license policy does not allow this license (4) (icu_properties_data-2.1.2/Cargo.toml) From: ? → cargo/[email protected] → cargo/[email protected] → cargo/[email protected] ℹ Read more on: This package | This alert | What is a license policy violation? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected]. Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore cargo/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		License policy violation: cargo icu_properties under Unicode-3.0 License: Unicode-3.0 - the applicable license policy does not allow this license (4) (icu_properties-2.1.2/LICENSE) License: Unicode-3.0 - the applicable license policy does not allow this license (4) (icu_properties-2.1.2/Cargo.toml) From: ? → cargo/[email protected] → cargo/[email protected] → cargo/[email protected] ℹ Read more on: This package | This alert | What is a license policy violation? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected]. Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore cargo/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		License policy violation: cargo unicode-ident under Unicode-3.0 License: Unicode-3.0 - the applicable license policy does not allow this license (4) (unicode-ident-1.0.22/Cargo.toml) License: Unicode-3.0 - the applicable license policy does not allow this license (4) (unicode-ident-1.0.22/Cargo.toml) License: Unicode-3.0 - the applicable license policy does not allow this license (4) (unicode-ident-1.0.22/LICENSE-UNICODE) From: ? → cargo/[email protected] → cargo/[email protected] → cargo/[email protected] → cargo/[email protected] → cargo/[email protected] → cargo/[email protected] → cargo/[email protected] → cargo/[email protected] → cargo/[email protected] → cargo/[email protected] → cargo/[email protected] ℹ Read more on: This package | This alert | What is a license policy violation? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected]. Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore cargo/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		License policy violation: cargo webpki-roots under CDLA-Permissive-2.0 License: CDLA-Permissive-2.0 - the applicable license policy does not allow this license (4) (webpki-roots-1.0.4/LICENSE) License: CDLA-Permissive-2.0 - the applicable license policy does not allow this license (4) (webpki-roots-1.0.4/Cargo.toml) From: ? → cargo/[email protected] → cargo/[email protected] → cargo/[email protected] ℹ Read more on: This package | This alert | What is a license policy violation? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected]. Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore cargo/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		License policy violation: cargo zstd-sys under GPL-2.0+ License: GPL-2.0+ - the applicable license policy does not allow this license (4) (zstd-sys-2.0.16+zstd.1.5.7/zstd/COPYING) From: ? → cargo/[email protected] → cargo/[email protected] → cargo/[email protected]%2Bzstd.1.5.7 ℹ Read more on: This package | This alert | What is a license policy violation? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected]. Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore cargo/[email protected]%2Bzstd.1.5.7. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

[bguillaumat-squads]

ACK