You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
API docs aren't updating with patch release #19570
It looks like the push to dokku was a no-op though as I don't see any build logs that a rebuild would create. I've tried enabling force pushes from GitHub actions. That might help with getting rebuilds each time the workflow runs. If that doesn't help, I can rework the action to include generated content on each action run so that there are changes on each workflow run.
It looks like the push to dokku was a no-op though as I don't see any build logs that a rebuild would create. I've tried enabling force pushes from GitHub actions. That might help with getting rebuilds each time the workflow runs. If that doesn't help, I can rework the action to include generated content on each action run so that there are changes on each workflow run.
Unless there is a change, I'm not sure force push will trigger a dokku build because it can still be up to date.
The current deployment workflow still checks out 2.x and force-pushes it to Dokku. In this incident, the release-triggered workflow completed but the Dokku push was a no-op, and a maintainer later forced the rebuild manually. That supports a specific recovery gap: when the requested CakePHP release changes but the docs repository does not, a successful push does not establish that a new docs build ran.
I could not independently verify the currently served API revision because my unauthenticated request received HTTP 403. The evidence here is limited to the workflow source and the manual-recovery record in this thread.
Activity
markstory commentedon Aug 3, 2026
The 5.4.1 tag did trigger a build of the API docs correctly https://github.com/cakephp/cakephp-api-docs/actions/runs/30417845070.
It looks like the push to dokku was a no-op though as I don't see any build logs that a rebuild would create. I've tried enabling force pushes from GitHub actions. That might help with getting rebuilds each time the workflow runs. If that doesn't help, I can rework the action to include generated content on each action run so that there are changes on each workflow run.
othercorey commentedon Aug 3, 2026
Unless there is a change, I'm not sure force push will trigger a dokku build because it can still be up to date.
LordSimal commentedon Aug 3, 2026
I forced a rebuild manually now.
othercorey commentedon Aug 3, 2026
I think the only other solution is running a remote ssh dokku build command.
yohimik commentedon Sep 9, 2026
The current deployment workflow still checks out
2.xand force-pushes it to Dokku. In this incident, the release-triggered workflow completed but the Dokku push was a no-op, and a maintainer later forced the rebuild manually. That supports a specific recovery gap: when the requested CakePHP release changes but the docs repository does not, a successful push does not establish that a new docs build ran.I could not independently verify the currently served API revision because my unauthenticated request received HTTP 403. The evidence here is limited to the workflow source and the manual-recovery record in this thread.