Repository navigation
docs: release-notes-from-GitHub-Releases (#135) and stable-link follow-up (#131); #133 needs no code change here - #153
Merged
Merged
Conversation
EpiAwarePackageTools#368 (kit v0.3.0) moves the release-notes docs page off a hand-maintained NEWS.md and onto the repo's published GitHub releases, fetched at build time. Rewrite the package-owned release_notes_header.jl to introduce those releases rather than describe a changelog file, and update the developer release-process docs to match. `docs/pages.jl` already carries the "Release notes" nav entry, so no change needed there. Keep NEWS.md rather than delete it: the docs env's EpiAwarePackageTools compat is still capped at 0.2 here (the workspace shares one Manifest across docs/, test/ and the root package, and test/Project.toml also caps it at 0.2 -- Dependabot's grouped Julia PR is what bumps all three together, not a hand-edit to one). Until that bump lands, the currently resolved 0.2.0 build_release_notes still literally prepends this header to NEWS.md; deleting NEWS.md now would make it skip generating release-notes.md entirely in the interim. The new header is inert either way, and starts working as soon as the compat bump merges.
#131 left this at /dev/ because both sibling /stable docs 404'd when it was filed. ConvolvedDistributions' stable docs have since deployed (confirmed 200); ComposedDistributions' have not (confirmed still 404), so that one stays at /dev/ for now. This package's own /dev -> /stable switch and the /stable linkcheck ignore (#131 items 1-2) stay out of scope: v0.1.0 is registered in General, but no git tag/GitHub release exists yet (see #150), so https://modifieddistributions.epiaware.org/stable/ still 404s.
Contributor
Try this Pull Request!Option 1: Julia Package ManagerOpen Julia and type: import Pkg
Pkg.activate(temp=true)
Pkg.add(url="https://github.com/EpiAware/ModifiedDistributions.jl", rev="fix/docs-build-133")
using ModifiedDistributionsOption 2: Local CheckoutIf you have the repo locally: git checkout fix/docs-build-133
julia --project=. -e "using Pkg; Pkg.instantiate()" |
Contributor
|
📖 Documentation preview is ready! View the docs for this PR at: https://EpiAware.github.io/ModifiedDistributions.jl/previews/PR153/ This preview will be updated automatically when you push new commits. |
Codecov Report✅ All modified and coverable lines are covered by tests.
Flags with carried forward coverage won't be shown. Click here to find out more. 🚀 New features to boost your workflow:
|
seabbs
approved these changes
Aug 12, 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
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.
#133 — docs build MethodError: no code change in this repo, root cause is upstream
#133 is NOT fixed by a commit in this PR — I could not find anything to
fix here, because there is nothing broken on current
main. Details:MethodErrorfrom the issue directly (not via thedocs build) by building a clean env with the registered
LoweredDistributionsv0.1.0 + this package and callinglower(modify(Exponential(2.0), -log(2.0); link = log)).lower()for aHazardLink-modified distribution is servedby
LoweredDistributionsModifiedDistributionsExt, an extension that livesin LoweredDistributions.jl, not here (by design — decision docs: add functionality tutorials and document the ComposedDistributions extension #23). That
extension was dropped from LoweredDistributions.jl so it could register
itself ahead of this package (this package was unregistered until
2026-08-06). Restoring it is a still-open draft PR,
LoweredDistributions.jl#105.
I verified directly against a fresh install of the real registered LD
v0.1.0 (tree-sha
b8f7606a) that it genuinely has noModifiedDistributionsweakdep/extension yet.
docs/src/getting-started/tutorials/lowering.jl(the file the MethodErrortraces to) was already excluded from the docs build by chore: sync the kit, clear every git pin, and unblock registration #129, merged
2026-08-03 — about 30 minutes after docs build broken on main: lower() MethodError for HazardLink-modified distributions in lowering.md #133 was filed against a pre-chore: sync the kit, clear every git pin, and unblock registration #129
main. I confirmed on a fresh checkout of currentmainthattask docs-fastdoes not buildlowering.jland does not hit this error.reasons unrelated to anything in this PR. I left comments explaining this
on #133
and #130
(the tracking issue for restoring the tutorial) so the two don't get
reopened/restored prematurely — registration alone isn't enough, LD#105
also needs to ship a release.
tutorial). Not doing that here since it's not this repo's fix to make.
#135 — point release notes at GitHub Releases
docs/release_notes_header.jlto introduce the fetched-at-buildGitHub releases instead of describing
NEWS.md, matchingEpiAwarePackageTools#368's convention.
docs/pages.jlalready had the "Release notes" nav entry from an earlierkit sync — no change needed.
docs/src/developer/release-process.md's "Release notes" sectionand pre-release checklist to stop telling contributors to write NEWS.md
entries.
NEWS.mdrather than deleting it (this repo capsEpiAwarePackageToolsat compat"0.2"in bothdocs/Project.tomlandtest/Project.toml, which share one Manifest via the Julia workspacefeature; Dependabot's grouped Julia PR is what bumps all of them together,
not a per-file hand-edit). Until that lands, the currently-resolved 0.2.0
kit still literally concatenates this header with
NEWS.md; deleting itnow would make the release-notes page render nothing in the interim. The
new header is inert either way and starts working the moment the compat
bump merges.
#131 — stable-link follow-ups
/stable/(confirmed 200 today). Left ComposedDistributions at
/dev/(confirmedstill 404).
/dev→/stableswitch and the/stablelinkcheck-ignore drop out of scope:
v0.1.0is registered in General,but no git tag/GitHub release exists yet, so
https://modifieddistributions.epiaware.org/stable/still 404s. Filed#150
— TagBot's only post-registration run fired before the registry PR
merged and logged "This package is not registered, skipping"; nothing has
re-dispatched it since.
I started; nothing to do.
Overlap with PR #140
None. #140 touches
docs/docs_config.jl'sLINKCHECK_IGNORE(thecommunity.epinowcast.org429 flake); this PR doesn't touch that file. Idid confirm from the CI logs that the actual failing
mainDocumenter run(2026-08-05) failed on exactly that flaky linkcheck, not on anything related
to #133 — so #140 is the real fix for that failure, and this PR is unrelated
to it.
Verification
task docs-fastbuilds clean on this branch (confirmed twice, most recentlyafter all commits above).
This was opened by a bot. Please ping @seabbs for any questions.