Skip to content

docs: fix HexDocs source links; add a docs-only publish workflow - #14

Merged
kasvith merged 2 commits into
mainfrom
fix/docs-source-links
Oct 22, 2026
Merged

kasvith merged 2 commits into
mainfrom
fix/docs-source-links

Conversation

@kasvith

@kasvith kasvith commented Oct 22, 2026

Copy link
Copy Markdown
Contributor

Both 1.0.0 releases published their docs: durable and durable_dashboard, changelog included. But every "View source" link is broken. They point at blob/durable-v1.0.0/lib/durable.ex and leave out the package's folder in the monorepo, so GitHub returns 404.

Changes

  • Source links: source_url_pattern in both mix.exs files now includes the package folder, e.g. blob/durable-v1.0.0/durable/lib/durable.ex#L1. I checked links built locally for both packages, and they return 200 on GitHub.
  • Docs-only republish: a new Docs workflow, run manually from Actions with a package choice, runs mix hex.publish docs from main under the package's current version. Releases already publish docs, so this is only for doc fixes between releases. It doesn't run on every push to main, because main can document APIs that aren't released yet, and those would show up under the released version. actionlint passes.

After merging

Run Docs for durable, then for durable_dashboard, to republish 1.0.0's docs with working links.

https://claude.ai/code/session_012aEMFtJKJsMz1vGtbSijGR

"View source" linked blob/<tag>/lib/..., missing the package's directory
in the monorepo, so every link 404'd. source_url_pattern adds it.

Actions → Docs republishes a package's HexDocs from main under its current
version, so doc fixes like this one don't need a release.

Claude-Session: https://claude.ai/code/session_012aEMFtJKJsMz1vGtbSijGR
@kasvith
kasvith merged commit e6a4237 into main Oct 22, 2026
4 checks passed
@kasvith
kasvith deleted the fix/docs-source-links branch October 22, 2026 05:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant