[IanButterworth]

Claude:

---

What are you trying to accomplish?

Since #16229, a Julia stdlib has no registry target, so its updated dependency gets an empty version. A grouped PR body then shows a blank line for every stdlib, e.g. JuliaCI/PkgEvalFarm.jl#84:

Updates `Dates` to 

Updates `SHA` to 

Now the update checker reports the newest bundled version the stdlib's compat entry admits ("Updates Dates to 1.11.0").

Anything you want to highlight for special attention from reviewers?

• The fix stays in julia/; the compat entry written is unchanged, and there is still no registry lookup for a stdlib.
• Open single-stdlib PRs were recorded with an empty version, so each will be superseded once by a new PR. Grouped PRs are matched by group name and only get their body refreshed.

How will you know you've accomplished your goal?

New update checker specs, and grouped end-to-end runs against IanButterworth/Julia-DependabotTest with stdlibs that have no compat entry (Dates, Random, SHA) next to a registry package:

Updates `Random` to 1.11.0
Updates `Example` to 0.5.5
Updates `SHA` to 1.0.0
Updates `Dates` to 1.11.0
Updates `Statistics` to 1.0.0

On main the same run gives Updates `Statistics` to with nothing after it. The compat entries written are the same with and without this change.

Checklist

• I have run the complete test suite to ensure all tests and linters pass.
• I have thoroughly tested my code changes to ensure they work as expected, including adding additional tests for new functionality.
• I have written clear and descriptive commit messages.
• I have provided a detailed description of the changes in the pull request, including the problem it addresses, how it fixes the problem, and any relevant details about the implementation.
• I have ensured that the code is well-documented and easy to understand.

Written with Claude Code (Claude Opus 5.5).