chore: upgrade shuttle dependency for example app

[aditiharini]

Why is this change needed?

The example app was fixed at an old version of shuttle that was missing more recent updates including storage lending.

Merge Checklist

Choose all relevant options below by adding an x now or at any time before submitting for review

• PR title adheres to the conventional commits standard
• PR has a changeset
• PR has been tagged with a change label(s) (i.e. documentation, feature, bugfix, or chore)
• PR includes documentation if necessary.

---

PR-Codex overview

This PR focuses on upgrading the @farcaster/shuttle dependency in the example app and making related adjustments in the codebase, including changes to request handling and variable names.

Detailed summary

• Updated @farcaster/shuttle dependency from ^0.5.0 to ^0.9.3.
• Replaced HubInfoRequest with GetInfoRequest in the App class.
• Changed handling of undefined instead of null for the hubSubscriber initialization.
• Modified the retrieval of maxFid to use numFidRegistrations instead of numFidEvents.

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

[changeset-bot]

🦋 Changeset detected

Latest commit: 043a1c8

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
@farcaster/shuttle	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[socket-security]

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

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	npm/​turbo-darwin-64@​1.10.3
	npm/​turbo-darwin-arm64@​1.10.3
	npm/​turbo-linux-64@​1.10.3
	npm/​turbo-linux-arm64@​1.10.3
	npm/​turbo-windows-64@​1.10.3
	npm/​turbo-windows-arm64@​1.10.3
	npm/​@​esbuild/​android-arm64@​0.17.11
	npm/​@​esbuild/​darwin-arm64@​0.17.11
	npm/​@​esbuild/​darwin-x64@​0.17.11
	npm/​@​esbuild/​freebsd-arm64@​0.17.11
	npm/​@​esbuild/​freebsd-x64@​0.17.11
	npm/​@​esbuild/​linux-arm@​0.17.11
	npm/​@​esbuild/​linux-arm64@​0.17.11
	npm/​@​esbuild/​linux-ia32@​0.17.11
	npm/​@​esbuild/​linux-loong64@​0.17.11
	npm/​@​esbuild/​linux-mips64el@​0.17.11
	npm/​@​esbuild/​linux-ppc64@​0.17.11
	npm/​@​esbuild/​linux-riscv64@​0.17.11
	npm/​@​esbuild/​linux-s390x@​0.17.11
	npm/​@​esbuild/​linux-x64@​0.17.11
	npm/​@​esbuild/​openbsd-x64@​0.17.11
	npm/​@​esbuild/​sunos-x64@​0.17.11
	npm/​@​esbuild/​win32-arm64@​0.17.11
	npm/​@​esbuild/​win32-ia32@​0.17.11
	npm/​@​esbuild/​win32-x64@​0.17.11
	npm/​@​esbuild/​netbsd-x64@​0.17.11
	npm/​@​swc/​core-darwin-arm64@​1.3.64
	npm/​@​swc/​core-darwin-x64@​1.3.64
	npm/​@​swc/​core-linux-arm-gnueabihf@​1.3.64
	npm/​@​swc/​core-linux-arm64-gnu@​1.3.64
	npm/​@​swc/​core-linux-arm64-musl@​1.3.64
	npm/​@​swc/​core-linux-x64-gnu@​1.3.64
	npm/​@​swc/​core-linux-x64-musl@​1.3.64
See 436 more rows in the dashboard

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		npm/@esbuild/[email protected] has Obfuscated code. Confidence: 0.90 Location: Package overview From: packages/hub-nodejs/examples/write-data/yarn.lock → npm/@esbuild/[email protected] ℹ Read more on: This package | This alert | What is obfuscated code? 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: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@esbuild/[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		npm/@esbuild/[email protected] has Obfuscated code. Confidence: 0.90 Location: Package overview From: packages/hub-nodejs/examples/write-data/yarn.lock → npm/@esbuild/[email protected] ℹ Read more on: This package | This alert | What is obfuscated code? 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: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@esbuild/[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		npm/[email protected] has Obfuscated code. Confidence: 0.94 Location: Package overview From: packages/hub-nodejs/examples/contract-signatures/yarn.lock → npm/[email protected] ℹ Read more on: This package | This alert | What is obfuscated code? 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: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/[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.

View full report