Repository navigation
chore(deps): upgrade @agentskit/doc-bridge to 2.0.0 - #1839
Merged
Merged
Conversation
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.
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.
What
@agentskit/doc-bridgefrom the1.12.0pin to the published2.0.0npm package inpackage.json.codeload.github.comtarballallowBuildsentry frompnpm-workspace.yaml. The dependency now resolves from the npm registry, so the git-tarball build allowance is no longer needed.pnpm-lock.yamlwithpnpm install. A frozen install succeeds afterwards..doc-bridge/index.jsonand.doc-bridge/capabilities.jsonundersha256-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)
pnpm docs:bridge:*from the same lockfile.ak-docs index, thenak-docs discoverandak-docs reconcile.doc-bridge.config.jsonhas noindex.contentHashsetting, so there was nothing to replace.fix propose/approve/applyor the whole-file MCP actions. Nothing to migrate.doc-bridge.config.jsonhas nosession-exportorbootstrap-deltaentries.ak-docs validate-configpasses.intelligence.memoryblock. Nothing to migrate.scripts/doc-bridge-benchmark.mjs, thedocs:bridge:*scripts, and theci.yml,docs.yml, anddoc-bridge-index.ymlworkflows 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.mjsdoes not exist in this repo.agents/ecosystem-doc-bridge-corpus-scanner/doc-bridge-adapter.jsstill writescontentHashAlgo: '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
Refs AgentsKit-io/doc-bridge#20
Validation
pnpm install --frozen-lockfilesucceeds.ak-docs --versionreports 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, andpnpm docs:bridge:doctor(score 95/100, gates 3/3, index fresh) all pass.ak-docs validate-configpasses.scripts/registry-agent-dogfood.test.mjsandscripts/doc-bridge-benchmark.test.mjsarenode --testsuites, not vitest. Both pass undernode --test.scripts/ecosystem-documentation-quality.test.mjspasses under vitest, with the other vitest files in the same run passing 20 of 20 tests.pnpm docs:bridge:benchmark --checkfails. 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.pnpm typecheck && pnpm test && pnpm build. No TypeScript source changed. CI is the gate.