Problem
The public latest documentation is stale. It still identifies itself as PyProBound 1.4.0 at revision 498a7d88, while v1.5.0 has been released and development has continued on main.
The Read the Docs API currently reports the newest build as commit 498a7d88a5b81f0054ecba4949795d90c77815f6, created August 19, 2024. No later builds are listed.
Expected behavior
Updates to main should trigger a successful build of the latest documentation, and the public site should reflect the current package version and source revision.
Suggested maintainer checks
- confirm the Read the Docs project is still connected to
BussemakerLab/PyProBound
- verify the repository webhook/integration is installed and active
- confirm the
latest version tracks main
- manually trigger a build after repairing the integration
Related work
PR #1 refreshes the v1.5 narrative documentation and fixes broken examples, links, and references. Merging that PR alone will not update the public site until the Read the Docs integration is restored.
Problem
The public
latestdocumentation is stale. It still identifies itself as PyProBound 1.4.0 at revision498a7d88, while v1.5.0 has been released and development has continued onmain.The Read the Docs API currently reports the newest build as commit
498a7d88a5b81f0054ecba4949795d90c77815f6, created August 19, 2024. No later builds are listed.Expected behavior
Updates to
mainshould trigger a successful build of thelatestdocumentation, and the public site should reflect the current package version and source revision.Suggested maintainer checks
BussemakerLab/PyProBoundlatestversion tracksmainRelated work
PR #1 refreshes the v1.5 narrative documentation and fixes broken examples, links, and references. Merging that PR alone will not update the public site until the Read the Docs integration is restored.