ci: restore docs CI — GITHUB_TOKEN for version fetch + skip bot-blocked link (via testing-ci)#464
Merged
Conversation
…site is live) The community PHP client author link (docs/weaviate/client-libraries/community.md) returns 200 in a browser but 403s GitHub-runner traffic via linkinator, failing PR link validation. Add it to the shared domainsToIgnore list, matching the existing convention for db-engines.com and similar bot-protected domains.
…ed PAT The custom GH_API_TOKEN secret (a PAT) expired, so update-config-versions.js got 401 Unauthorized from the GitHub API and failed the whole job at the 'Update versions from GitHub' step in both PR link validation and the production Build-and-deploy workflow. Switch both to the built-in secrets.GITHUB_TOKEN, matching llms_txt_tests.yml, which already fetches the same public release listings successfully. The env var name GH_API_TOKEN is unchanged so the script needs no edit; GITHUB_TOKEN never expires and needs no rotation.
![orca-security-eu[bot]](https://avatars.githubusercontent.com/in/276244?s=60&v=4){kind=small}
There was a problem hiding this comment.
Orca Security Scan Summary
| Status | Check | Issues by priority | |
|---|---|---|---|
 Passed |
Infrastructure as Code |  0  0  0  0 |
View in Orca |
| Passed |
SAST | 0 0 0 0 |
View in Orca |
| Passed |
Secrets | 0 0 0 0 |
View in Orca |
| Passed |
Vulnerabilities | 0 0 0 0 |
View in Orca |
The Query Agent service now requires the search-mode `filtering` argument to be "recall" or "precision"; the latest client (weaviate-agents 1.6.0) still defaults it to None and sends null, so every `.search()` call that omits `filtering` fails with a 422. Document `filtering` as required (recommending "recall") and pass `filtering="recall"` in every initial search-mode snippet (Python + TypeScript); the precision FilteringExample and pagination/ask calls are unchanged.
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
1 participant
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.
Runs the full docs test suite (Docs Code Tests / Indexability / llms.txt / link validation / deploy) from
testing-ciagainst the freshly-restored Weaviate Cloud test cluster. Supersedes #463 (same two commits); merging fromtesting-cionce green.Changes (2 commits)
fix(ci): use built-inGITHUB_TOKENfor version fetch instead of expired PAT — the customGH_API_TOKENsecret expired, soupdate-config-versions.jsgot 401 from the GitHub API and failed the job at the Update versions from GitHub step (both PR link validation and production Build-and-deploy). Switches the 3 refs tosecrets.GITHUB_TOKEN, matchingllms_txt_tests.yml. Env var name unchanged; script untouched; never expires.fix(ci): skiptim-kleyersburg.dein link validator — community PHP-client author link returns 200 in a browser but 403s runner traffic; added to the shareddomainsToIgnorelist.Context
The scheduled Docs Code Tests failures (~124 across all 5 languages, all identical
404 on GET /v1/meta) were caused by the WCD test cluster being deleted, not snippet bugs. The cluster has been restored from thetests/backupssnapshot (20 collections, counts verified,near_textworking) and the cluster secrets updated. This run validates end-to-end against it.