Repository navigation
Use built-in AI Search storage and direct document ingestion - #186
Merged
Merged
Conversation
jonbeckman
marked this pull request as ready for review
November 9, 2026 16:47
Contributor
TegamiThis repository uses Tegami to manage releases. When your changes affect published packages, add a changelog file under Create a changelog → · Changelog format Release preview
Changelogs in this PR
Run Managed by Tegami. |
Contributor
🟢 e2e solzero-core: 32 passed4 agent steps · 4 replayed from cache Change 49 files changed since All 32 tests in 13 files
e2e 0.21.3 · 3m 23s · local-cloudflare · run artifacts |
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
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.
New AI Search sources now use Cloudflare built-in storage and the namespace binding's Items API. Administrators can upload documents, inspect indexing status, and delete items without an external-storage service token. Workflows can ingest text or JSON through the new Upload to AI Search node, which requires an administrator workflow owner.
The external-storage token reference is removed from deployment configuration, Worker bindings, deployment workflows, and secret synchronization. An explicit local configuration option enables native remote namespace bindings for isolated integration tests; the ordinary local stack keeps them disabled.
This is a breaking source transition. Existing R2/website records remain visible and exportable with a migration-required state, and retrieval excludes them until operators migrate their originals to a new built-in source and update selections. The legacy content bucket and separate artifact/skill storage remain available. AI Search migration guidance defines inventory, copy, verification, reference switch, and retirement. Deployment does not convert or discard legacy content.
The manual recording workflow also completes its requested recording-commit step after successful tests when release detection is skipped.
Validation:
Current PR checks cover the published head. An authenticated ordinary-member role check, historical-source content transfer, and standing pre/prod deployment remain separate unverified rollout gates. No standing stage was deployed and no existing application data was migrated.