Skip to content

Auto-update doc build config#19

Open
alauda-github-idpbot wants to merge 2 commits into
release-1.4from
feat/auto-update-doc-build-release-1.4-fix
Open

Auto-update doc build config#19
alauda-github-idpbot wants to merge 2 commits into
release-1.4from
feat/auto-update-doc-build-release-1.4-fix

Conversation

@alauda-github-idpbot
Copy link
Copy Markdown
Contributor

auto update doc build config for doc pipeline

chideat and others added 2 commits May 11, 2026 09:44
- install: built-in dump filenames carry literal _20260410 dates,
  not the <date> placeholder I had; init-container first-start steps
  re-described to match init-database.sh (BM25 ships in the dump on
  first install, the ensure-step is upgrade-only); the chat-history
  database is named via PG database name, not hardcoded; mention
  smartdoc.enableMCPServer separately from Enable MCP Tools.
- upgrade: re-order the auto-swap step list to match init-database.sh
  (advisory lock first, then kb_swap_state row, drop, restore, verify
  count=1, rename, BM25 + 001/002 migrations, stamp + clear). Replace
  the fabricated second log line ("data_version=... stamped;
  kb_swap_state cleared") with the actual "[upgrade] <stamp> applied."
  emitted at line 236, plus the no-op "already applied, skipping."
  variant. Drop the BYO-Knowledge label from docvec_user_kb.
- release notes: HMAC token format is the three-part colon string
  <username>:<unix_ts>:<hex_hmac_sha256(API_KEY, 'username:ts')>,
  not a bare HMAC. Recall@5 on hybrid_rrf is ≈ 0.91 (per-repo macro
  across 4.1/4.2/4.3) per reports/2026-05-08/SUMMARY.md, not 0.82
  (which mixed it up with the unrelated agent-eval tool_call_recall).
- build-custom-kb: replace the bogus "postgre-vec-0" StatefulSet
  ordinal with a Deployment-style pod lookup (the bundled pgvector
  is a Deployment, app=postgre-vec). Mode C used to instruct editing
  smart-doc-config directly, which gets reverted on chart re-roll
  and on every init-container restart — replaced with a
  pgconnect.pgCollectionName chart override and an explicit warning.
  Soften the BYO-Knowledge claim to "user knowledge-base database"
  rather than asserting BYO writes there. Note that the cs2000 /
  cs3000 selector dumps are added during image build and not
  visible in the repo's dumps/ directory. Clarify kb_version is
  accepted both as a top-level manifest key and as --kb-version CLI
  flag.
@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented May 11, 2026

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

🗂️ Base branches to auto review (3)
  • main
  • master
  • ^\d.x$

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 2bde4178-ee84-4e7c-97c4-e3c9e947b25e

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch feat/auto-update-doc-build-release-1.4-fix

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@cloudflare-workers-and-pages
Copy link
Copy Markdown

Deploying alauda-hyperflux with  Cloudflare Pages  Cloudflare Pages

Latest commit: 37c0fc5
Status: ✅  Deploy successful!
Preview URL: https://0494e3ca.alauda-hyperflux.pages.dev
Branch Preview URL: https://feat-auto-update-doc-build-r-rhl6.alauda-hyperflux.pages.dev

View logs

Base automatically changed from release-1.4-fix to release-1.4 May 12, 2026 06:42
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