Skip to content

chore(deps): upgrade @agentskit/doc-bridge to 2.0.0 - #1839

Merged
EmersonBraun merged 2 commits into
mainfrom
chore/doc-bridge-2.0
Oct 12, 2026
Merged

EmersonBraun merged 2 commits into
mainfrom
chore/doc-bridge-2.0

Conversation

@EmersonBraun

Copy link
Copy Markdown
Member

What

  • Bump @agentskit/doc-bridge from the 1.12.0 pin to the published 2.0.0 npm package in package.json.
  • Remove the codeload.github.com tarball allowBuilds entry from pnpm-workspace.yaml. The dependency now resolves from the npm registry, so the git-tarball build allowance is no longer needed.
  • Regenerate pnpm-lock.yaml with pnpm install. A frozen install succeeds afterwards.
  • Regenerate the committed .doc-bridge/index.json and .doc-bridge/capabilities.json under sha256-semantic-v1.

Transitive @agentskit/* packages that doc-bridge 2.0.0 depends on (adapters, core, harness, ink, memory, rag, plus new net and cross-platform entries) move with it. No direct dependency other than doc-bridge changed.

Why

2.0.0 is the published release of the doc-bridge major. The 1.x index is now migration-only. The freshness gate fails with "Legacy index is migration-only" until the index is regenerated with ak-docs index.

Migration steps applied (docs/migration/1.x-to-2.0.md)

  • Step 1 (upgrade readers before regenerating): the CLI and CI both run pnpm docs:bridge:* from the same lockfile.
  • Step 2 (semantic index identity): ran ak-docs index, then ak-docs discover and ak-docs reconcile. doc-bridge.config.json has no index.contentHash setting, so there was nothing to replace.
  • Steps 3-5 (region remediation, human-only approval): the repo does not call fix propose/approve/apply or the whole-file MCP actions. Nothing to migrate.
  • Step 6 (reserved memory adapters): doc-bridge.config.json has no session-export or bootstrap-delta entries. ak-docs validate-config passes.
  • Step 7 (memory directories): the config has no intelligence.memory block. Nothing to migrate.
  • Scripts and CI: scripts/doc-bridge-benchmark.mjs, the docs:bridge:* scripts, and the ci.yml, docs.yml, and doc-bridge-index.yml workflows use only commands that 2.0 still supports (index, query package --agent --json --config, gate run, conformance run, doctor). No edits were needed. scripts/generate-doc-bridge-config.mjs does not exist in this repo.
  • agents/ecosystem-doc-bridge-corpus-scanner/doc-bridge-adapter.js still writes contentHashAlgo: 'sha256-normalized-v1' on a Registry agent proposal. The migration table lists the normalized algorithm as a retained, independent contract, so it is left unchanged. The Registry-agent dogfood test passes with it.

Reuse

No new package or dependency was added. The change only upgrades an existing @agentskit/* dependency.

Type of change

  • Bug fix (non-breaking)
  • New feature (non-breaking)
  • Breaking change
  • Docs only
  • Chore / internal

Refs AgentsKit-io/doc-bridge#20

Validation

  • pnpm install --frozen-lockfile succeeds.
  • ak-docs --version reports 2.0.0.
  • pnpm docs:bridge:index, pnpm docs:bridge:freshness, pnpm docs:bridge:gate (index-freshness, human-guide-links, and documentation-standard-v1 all pass), pnpm docs:bridge:conformance, and pnpm docs:bridge:doctor (score 95/100, gates 3/3, index fresh) all pass.
  • ak-docs validate-config passes.
  • scripts/registry-agent-dogfood.test.mjs and scripts/doc-bridge-benchmark.test.mjs are node --test suites, not vitest. Both pass under node --test. scripts/ecosystem-documentation-quality.test.mjs passes under vitest, with the other vitest files in the same run passing 20 of 20 tests.
  • pnpm docs:bridge:benchmark --check fails. Retrieval latency and response-size metrics and quality counters are compared against .doc-bridge/benchmarks/baseline.json, which was captured against a ~113 KB index with 27 knowledge entries. The committed index at the base commit is already ~7.9 MB with 2,433 entries, so the size-related regressions predate this upgrade. The baseline is intentionally not replaced here, because the migration guide keeps benchmark baselines unchanged. Maintainers need to decide whether to refresh the baseline in a separate change. The quality counters (stale 1, undocumented 16, unresolved 4) were not compared against 1.12.0 output on the same index, so that remains unverified.
  • Not run: full pnpm typecheck && pnpm test && pnpm build. No TypeScript source changed. CI is the gate.

Move from the 1.12.0 pin and the codeload tarball build allowance to the
published 2.0.0 package, and regenerate the committed index under
sha256-semantic-v1 as the 2.0 migration guide requires. The repository's
doc-bridge config needs no changes: it defines no reserved memory adapters,
legacy index.contentHash, or removed flags.
@EmersonBraun
EmersonBraun merged commit 8539a2c into main Oct 12, 2026
30 checks passed
@EmersonBraun
EmersonBraun deleted the chore/doc-bridge-2.0 branch October 12, 2026 12:30
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.

1 participant