Repository navigation
julia: explain a <0.0.1 bound on a stdlib compat entry in the PR - #16308
Merged
Merged
Conversation
When the project's `julia` compat entry admits releases before 1.10, Dependabot gives each standard library's compat entry a `<0.0.1` bound, because `Pkg.test()` on those releases gave stdlibs version 0.0.0 (dependabot#16229). Nothing in the PR said so, and users read it as a bug. The file updater now adds one NOTE to the PR, naming each stdlib whose entry gains the bound, saying why, and suggesting raising the `julia` compat entry to 1.10 to drop it. It links the stdlib compat PSA. `Notice.markdown_mode` mapped INFO to `[!INFO]`, which GitHub does not render as an alert. No ecosystem showed an INFO notice in a PR before; it now maps to `[!NOTE]`. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
IanButterworth
changed the title
<0.0.1 bound on a stdlib compat entry in the PR
IanButterworth
force-pushed
the
julia-stdlib-notice
branch
from
October 6, 2026 13:26
141c36b to
a294e15
Compare
IanButterworth
marked this pull request as ready for review
October 6, 2026 13:27
Contributor
Author
|
@robaiken this should be ready to go. |
v-robaiken
approved these changes
Oct 8, 2026
5 tasks done
jonas-schulze
added a commit
to mpimd-csc/MORWiki.jl
that referenced
this pull request
Oct 12, 2026
See this for an explanation: dependabot/dependabot-core#16308
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What are you trying to accomplish?
When a project's
juliacompat entry admits releases before 1.10, Dependabot adds<0.0.1to the compat entry of each stdlib dependency it updates (#16229). Nothing in the PR says why, so it reads as a bug (Discourse thread).The PR now carries one note, only when an update adds that bound:
Note
LinearAlgebra,Printfare standard libraries. Before Julia 1.10,Pkg.test()gave standard libraries version 0.0.0, so while thejuliacompat entry admits those releases, a stdlib compat entry needs<0.0.1for tests to resolve. Raising thejuliacompat entry to1.10or later removes the need for it. See the stdlib compat PSA.Entries that already had the bound, and other stdlib widenings, get no note.
Anything you want to highlight for special attention from reviewers?
One change outside
julia/:Notice.markdown_modemapped INFO to[!INFO], which GitHub does not render as an alert. No ecosystem showed an INFO notice in a PR before; it now maps to[!NOTE].How will you know you've accomplished your goal?
New file updater specs cover a stdlib entry gaining the bound (one NOTE notice) and one that already had it (none). Locally
julia/spec(349 examples),common/spec/dependabot/notice_spec.rb, rubocop andsrb tc(no errors underjulia/) pass.Checklist