Tatsh / livecheck / 34039942957

100%

push

github

special.github,utils.portage: fix four wrong version detections

Four packages in the inode64 overlay were reported wrongly:

dev-util/graphify was "updated" from 0.9.55 to 1.0.0. The v1.0.0 tag
belongs to an abandoned branch cut months before v0.9.55. The tags.atom
feed never listed it because it only returned recent tags; the tags API
does. The GitHub handler now compares the commit date of the winning
tag with the packaged tag's commit and drops candidates that predate
it, trying the next one (up to STALE_TAG_CHECKS).

Every dev-libs/rocm-* ebuild (and the other ROCm monorepo consumers)
got a revision bump on each run. They pin the commit of the
`therock-10.0` release tag from a monorepo archive, and the pinned-SHA
path compared that commit with the head of master. When the pinned
commit is a tag, the handler now looks for newer tags following the
same scheme instead, and reports no change when there are none. Several
tags on one commit resolve to the one with the highest version.

dev-lang/go was "updated" to 2012.3.27 from the `weekly.2012-03-27`
tag. Without a version reference nothing filtered tags of another
scheme. get_last_version() now infers the reference from the result
naming the packaged version (`go1.27.1`), skipping the inference when a
transformation or regex rewrites the tags. Because GitHub sorts tags by
name, the release tags were on the second page, so the tag list is read
page by page (up to TAG_PAGES) until the packaged tag shows up or a
short page ends the list.

dev-python/opentelemetry-instrumentation-* lost the `0` of `0.65b0`,
becoming `0.65_beta`. The pypi eclass turns that into `0.65b`, which
PyPI does not serve. PEP 440 pre-release counters written directly
after the release segment keep their explicit zero; `1.2.3-alpha0` is
still shortened.

Verified against the inode64 and tatsh overlays: only the four cases
above changed.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/cod... (continued)

1228 of 1232 branches covered (99.68%)

Branch coverage included in aggregate %.

113 of 118 new or added lines in 2 files covered. (95.76%)

3233 of 3238 relevant lines covered (99.85%)

4.99 hits per line