[docs] Self-healing documentation fixes from issue analysis - 2026-03-05#19755
Merged
[docs] Self-healing documentation fixes from issue analysis - 2026-03-05#19755
Conversation
The `julia` ecosystem identifier exists in ecosystem_domains.json and was actively updated today (added *.pkg.julialang.org wildcard and storage.julialang.net CDN domain), but was missing from both: - network-configuration.md Available Ecosystems table (guide) - network.md Ecosystem Identifiers table (reference) Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
github-actions
bot
added
automation
documentation
This was referenced Mar 5, 2026
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
1 participant
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.
Self-Healing Documentation Fixes
This PR was automatically created by the Daily Documentation Healer workflow.
Gaps Fixed
juliaecosystem identifier undocumented in network docs — Addedjuliato the Available Ecosystems table in the Network Configuration Guide and to the Ecosystem Identifiers table in the Network Permissions reference. The ecosystem has been inecosystem_domains.jsonfor some time and was actively updated today (commits 17022a6 and d3ef89b adding*.pkg.julialang.orgwildcard andstorage.julialang.net), yet neither documentation table listedjuliaas a usable ecosystem identifier.Root Cause
DDUw ran at 04:32 UTC and produced PR #19690. The two Julia ecosystem commits landed at 18:23 and 18:52 UTC — after DDUw had already merged its daily PR. The timing gap means DDUw never saw these changes on 2026-03-05.
More broadly, DDUw doesn't validate whether all keys in
ecosystem_domains.jsonappear in the network documentation tables.juliawas undocumented even before today's commits; DDUw's 24-hour commit scan never triggered on this long-standing drift.DDUw Improvement Suggestions
Add a new scan step to
daily-doc-updater.mdthat cross-checksecosystem_domains.jsonkeys against the Ecosystem Identifiers table indocs/src/content/docs/reference/network.mdand the Available Ecosystems table indocs/src/content/docs/guides/network-configuration.md. Any key present in the JSON but absent from both tables should be flagged as a documentation gap and fixed. This is a deterministic, low-cost check that catches drift between code and docs regardless of whether a matching PR was merged in the last 24 hours.Files Changed
docs/src/content/docs/guides/network-configuration.md— addedjuliarow to Available Ecosystems tabledocs/src/content/docs/reference/network.md— addedjuliato the Ecosystem Identifiers identifier listAnalyzed Issues (last 7 days, label: documentation, state: closed)
docs/docs/