Chore: confirm soroban-sdk is latest; close out storage_change_events scanner noise

[0xdevcollins]

Severity: LOW · Chore · boundless-events + boundless-profile

Surfaced by the Scout scan of e1f17937. Covers the soroban_version enhancement and closes out the remaining storage_change_events enhancement noise.

Scope

• Confirm soroban-sdk (currently 23.5.2 in the workspace Cargo.toml) is the latest patch and bump if a newer one is out; re-run the build/test suites after.
• The missing ManagerChanged storage-change event is delivered by the manager two-step issue (Enhanced Milestone & Admin Management Functions for On-chain/Frontend Sync #3).
• The remaining ~44 storage_change_events flags were spot-checked and the flagged functions already publish an event; record as no action in the scanner-disposition doc rather than chasing each one.

Notes

Pure hygiene — no security impact. Batch with the next dependency-maintenance PR.

[coderabbitai]

🔗 Related PRs

#47 - test(events): added bounty pillar — apply / withdraw_application + c… [merged]
#59 - docs: rewrite README with deployed addresses and versions [merged]
#60 - Revise README and CI workflows for 1.1.0 deployment update [merged]

---

📝 Issue Planner

_{Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.}

• Create Plan

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!

[MorsH14]

I’d love to work on this issue

[Luchistack]

Hi Maintainer, i would love to work on this issue.

[Preciousuche]

Hi! I’d like to work on this chore.

I’ll verify that the project is using the latest soroban-sdk version, update it if necessary, and ensure the project builds and tests pass. I’ll also investigate the storage_change_events scanner warning to determine whether it’s a genuine issue or scanner noise, then resolve or suppress it appropriately while documenting the reasoning in the PR.

Looking forward to working on this!

[funds0033-cmyk]

I will like to work on this

[JamesVictor-O]

Hello! I’d love to take on this issue. I’ve reviewed the requirements and have a clear path forward for the implementation. I estimate I can have a PR ready within about 3 hours of being assigned. Could you please assign this to me?

[grantfox-oss]

🦊 GrantFox — @JamesVictor-O has been assigned to this issue as part of the Official Campaign | FWC26 campaign!

Next steps:

1. Open a Pull Request referencing this issue (e.g., Closes #77)
2. Your PR will be reviewed by the boundlessfi maintainers

Good luck! Track your progress on GrantFox.