rust-analyzer formula commit/tag mismatch

[Esgariot]

Output of brew config

HOMEBREW_VERSION: 4.6.3-19-g20eb1e1
ORIGIN: https://github.com/Homebrew/brew
HEAD: 20eb1e15b8db90e9d6d341dc66ea10276f380e2f
Last commit: 5 hours ago
Branch: main
Core tap HEAD: 2b9b6553aada686db69460e5c455d13e8ee4d157
Core tap last commit: 16 minutes ago
Core tap JSON: 12 Aug 22:35 UTC
Core cask tap JSON: 12 Aug 22:35 UTC
HOMEBREW_PREFIX: /opt/homebrew
HOMEBREW_CASK_OPTS: []
HOMEBREW_EDITOR: hx
HOMEBREW_FORBID_PACKAGES_FROM_PATHS: set
HOMEBREW_MAKE_JOBS: 10
HOMEBREW_SORBET_RUNTIME: set
Homebrew Ruby: 3.4.5 => /opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.4.5/bin/ruby
CPU: deca-core 64-bit arm_donan
Clang: 17.0.0 build 1700
Git: 2.50.1 => /opt/homebrew/bin/git
Curl: 8.7.1 => /usr/bin/curl
macOS: 15.6-arm64
CLT: 16.4.0.0.1.1747106510
Xcode: N/A
Rosetta 2: false

Output of brew doctor

�[1mPlease note that these warnings are just used to help the Homebrew maintainers
with debugging if you file an issue. If everything you use Homebrew for is
working fine: please don't worry or file an issue; just ignore this. Thanks!�[0m

Warning: The following formulae have the same name as core formulae:
  yqrashawn/goku/goku
Their taps are in use, so you must use these full names throughout Homebrew.

Description of issue

There was a hotfix for rust-analyzer, but I think their new 2025-08-11 release description is incorrect, it should be

"Commit: 9db0550"

instead of

"Commit: 4e147e7"
(which was the commit 2025-08-10 pointed at)

Homebrew/homebrew-core@9702cbb
tied the 2025-08-11 release to that previous commit, and the 2025-08-10 tag it was tied to no longer exists.

The error in this case is in the release description on rust-analyzer's side, but I wonder if this specific formula should check for this kind of mismatch

counterpart comment - rust-lang/rust-analyzer#20427 (comment)

[p-linnane]

We pull the latest tag, and build off that. At the time we built the bottles, that tag and hash were correct. Upstream may have re-tagged, which the git manual correctly calls "the insane thing to do". There's not much we can do about upstreams that play loose with tags, other than update when someone notices. I'll open a PR to update this.

[Esgariot]

The release just got corrected, I don't know what happened tag-wise or if there was re-release under same tag/name. Thanks for correcting the ref in formula!

[SMillerDev]

If a tag gets made, the assumption from both git and everyone using the tag will be that it never changes. If it does change, people have to go figure out if it was intentional or if someone compromised your repo.

[Esgariot]

Yes, the "don't rewrite shared history" rule, ofc that makes sense. I was trying to see how it got overwritten and why

[Esgariot]

rust-lang/rust-analyzer#20427 (comment) it was recreated because it introduced regression, and it also was a second release of that day which updated tag, because of tag date format :<