Consider publishing Homebrew bottles for xdk-latest to avoid non-bottled dependent warnings and local source installs

[lagergren]

Summary

xdk-latest is currently updated correctly by the Homebrew tap automation, but the formula is source-only (no bottle do block). That means Homebrew reports warnings like:

Warning: The following dependents of upgraded formulae are outdated but will not
be upgraded because they are not bottled:
  xdk-latest

This appears when a dependency such as openjdk@25 is upgraded. Nothing is actually broken, but the UX makes the formula look unhealthy and requires local source installation/reinstallation.

Current behavior

• xdk-latest depends on openjdk@25
• the Homebrew update workflow writes a timestamped dynamic version and pushes the formula to xtclang/homebrew-xvm
• installs/upgrades work, but xdk-latest is built locally rather than poured from a bottle
• after dependency upgrades, Homebrew can mark xdk-latest as an outdated dependent and warn that it will not be upgraded because it is not bottled

Suggested improvement

Investigate adding bottle publishing for xdk-latest as part of the release/update automation.

That would likely mean:

• building bottles for supported platforms/architectures in CI
• publishing the bottle artifacts somewhere Homebrew can fetch them
• updating the formula metadata with bottle hashes

Expected benefit

• faster brew install / brew upgrade
• fewer confusing warnings around outdated non-bottled dependents
• less local work on user machines
• clearer Homebrew experience for snapshot users

Notes

This is not a replacement for depends_on "openjdk@25"; Java would still remain a dependency. Bottling would only change how xdk-latest itself is delivered and upgraded.

There may be snapshot-specific complexity here because xdk-latest uses timestamped dynamic versions, so the CI/release cost should be evaluated against the user benefit.