In SDK v0.52, the client package now utilizes the Context to derive addresses. Your Context does not contain the valid settings

SDK v0.52 deprecated the BasicModuleManager. You should use the ModuleManager instead.

SDK v0.52 deprecated the BasicModuleManager. You should use the ModuleManager instead.

SDK v0.52 deprecated the BasicModuleManager. You should use the ModuleManager instead.

SDK v0.52 deprecated the BasicModuleManager. You should use the ModuleManager instead.

SDK v0.52 deprecated the BasicModuleManager. You should use the ModuleManager instead.

SDK v0.52 deprecated the BasicModuleManager. You should use the ModuleManager instead.

SDK v0.52 deprecated the BasicModuleManager. You should use the ModuleManager instead.

SDK v0.52 deprecated the BasicModuleManager. You should use the ModuleManager instead.

SDK v0.52 deprecated the BasicModuleManager. You should use the ModuleManager instead.

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

This run of the CodeQL Action does not have permission to access Code Scanning API endpoints. As a result, it will not be opted into any experimental features. This could be because the Action is running on a pull request from a fork. If not, please ensure the Action has the 'security-events: write' permission. Details: Resource not accessible by integration

Feature flags do not specify a default CLI version. Falling back to the CLI version shipped with the Action. This is 2.20.1.

1 issue was detected with this workflow: Please specify an on.push hook to analyze and see code scanning alerts from the default branch on the Security tab.

Unable to validate code scanning workflow: MissingPushHook