Repository navigation
fix(connectors): expose public Factory installation guidance - #110
Merged
Merged
Conversation
github-actions Bot
pushed a commit
that referenced
this pull request
Oct 29, 2026
## [0.45.1](v0.45.0...v0.45.1) (2026-10-29) ### Bug Fixes * **connectors:** expose public Factory installation guidance ([#110](#110)) ([35fe808](35fe808))
Contributor
|
🎉 This PR is included in version 0.45.1 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
volod-vana
added a commit
that referenced
this pull request
Oct 29, 2026
Resolve conflicts with the Factory connector build (#108/#110/#111), mainnet app registration (BUI-938) and the approved onboarding (#112). - Welcome, source picker and missing-source flow follow main's approved screens; `vana skills setup` keeps this PR's three-skill offer. - Create Connector keeps main's Factory workflow and adds this PR's CLI bootstrap, discovery and collect-through-Vana readiness guidance; the deleted legacy references are no longer mentioned (version 1.4.0). - Builder keeps this PR's description (version 1.2.1). - README and LOG keep both sides' sections. - Ingest-failure tests keep main's gated cases with this PR's readiness setup.
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.
Agents discovering Factory through Vana currently receive a private supplied-tarball placeholder. Replace it with the exact public
@vana/factory-core@0.0.1release artifact, local tools prefix, real Node 24 requirements and public data-connectors setup. The current agent continues using the existing job, check and same-run collection actions.The offline-instructions regression failed before repair; all 45 focused tests and full validation (952 tests, typecheck, ESLint and formatting) pass. The built CLI exposes the guide with no Factory installation present.
Refs BUI-951. Active CLI work and #106 are untouched. No runtime/orchestration/release-pipeline changes. Public-only synthetic acceptance follows publication of the package and this CLI release.
CI identified an incomplete legacy registry fixture that fetched optional metadata from GitHub. A rejecting fetch guard/no-call assertion reproduced it; a complete local fixture repairs it without changing production code or timeouts. Full validation remains 952 passing tests.
A manual publication workflow can use the existing Actions npm credential to publish only the reviewed public Factory 0.0.1 artifact, pinned by SHA256. It extracts no credential and accepts no arbitrary artifact input. Anonymous public tarball installation already passed with private-checkout reads denied.