Skip to content

Stop updating the ollama.com pages from the workflow - #15

Draft
Tromset wants to merge 1 commit into
mainfrom
claude-code/relaxed-tesla-2eix4r
Draft

Tromset wants to merge 1 commit into
mainfrom
claude-code/relaxed-tesla-2eix4r

Conversation

@Tromset

@Tromset Tromset commented Oct 23, 2026

Copy link
Copy Markdown
Owner

Summary

The "Update the model pages" step of publish-ollama never worked: ollama.com answers HTTP 401 to the page edit request with a freshly created API key, exactly as it does with no key or an invalid one (run with the new key). It accepts page edits only from a signed-in browser.

  • .github/workflows/publish-ollama.yml: removes the page step, the OLLAMA_API_KEY secret and its check, and the docs/ollama/** and scripts/update-ollama-pages.sh triggers; the none input (pages only) is gone.
  • scripts/update-ollama-pages.sh: removed.
  • readme and Documentation (section 8, layout, troubleshooting): the pages are pasted by hand from docs/ollama/.
  • Tests: the workflow test now checks OLLAMA_KEY only.

Publishing the models is unchanged and works (last run).

Note: merging changes the workflow file, so publish-ollama republishes all models once (same content), then publish-huggingface mirrors them again.

Test plan

  • npm test: 66/66 pass.
  • Workflow YAML parses.

Generated by Claude Code

ollama.com answers 401 to page edits with an API key, the same as with no key
or an invalid one: it accepts them only from a signed-in browser. Remove the
page step, its script and the OLLAMA_API_KEY secret; the pages in docs/ollama/
are pasted by hand.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Cw7NFZ1kjsaaLELfRZLFv9
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.

2 participants