Repository navigation
Bump omercnet/omp to 1.3.0 - #161
github-actions[bot] wants to merge 1 commit into
Conversation
There was a problem hiding this comment.
Needs from you: answers
- Accept the build command
node scripts/prepare-dependencies.mjsfor this listing, because from an npm install it finds nocatalogand installs nothing? (yes) - If you accept it, is the outcome changes requested for the missing
OVERVIEW.md, the same as the other omercnet bumps (#159, #160, #162)? (yes)
REVIEW.md rejects a command that installs a package the lockfile does not fix. scripts/prepare-dependencies.mjs:8-16 walks up from the plugin directory looking for a package.json with a catalog field. Only if it finds one does it run npm install --omit=dev --ignore-scripts --no-package-lock --workspaces=false (scripts/prepare-dependencies.mjs:42-50), which resolves yaml ^2.9.0 without a lockfile. In Paseo's npm install layout the nearest package.json above the package is Paseo's installation manifest, which has no catalog, so the script returns at line 41 unless a package.json higher up on the host has one. The script is unchanged from the listed 1.2.0. The policy doesn't settle a command that is a no-op in practice, so this goes to you.
@omercnet, whatever the answer above, this version also needs OVERVIEW.md next to paseo-plugin.json in paseo-omp/, published in the package, before a bump can merge. It replaces the registry copy plugins/omercnet/omp.md, whose first line calls the plugin an alpha preview while 1.3.0's README calls it stable. The shape is in REVIEW.md.
Review data
- Artifact: npm
@omercnet/paseo-omp1.3.0 (from 1.2.0),https://registry.npmjs.org/@omercnet/paseo-omp/-/paseo-omp-1.3.0.tgz. npm provenance namesomercnet/paseo-pluginsat8e8dfa1aebbe7c23673f344e75d93dfac91daba9, built by.github/workflows/release-please.ymlonmain. - Integrity: SHA-512 of both tarballs matches the record (old and new pin), npm's
dist.integrity, and the provenance subject digest. - Validation:
npm testpasses (140/140).node scripts/validate.ts --online --changedfails with one error:omercnet/omp/OVERVIEW.md is required. - Extracted and inspected: both tarballs (96 files each), extracted and diffed locally.
README.mdchanges "Alpha preview" to "Stable";client/omp-config-surface.tsx:199-210adds a static "Tool access boundary" card whose claims matchserver/provider/host-tools.ts:242-246andserver/provider/config-normalization.ts:49-55;client/quota-popover.tsx:104-106adds static text; model list limits rise from 256 to 4096 (server/provider/catalog.ts:52,shared/omp-models.ts:8) and theget_available_modelsresponse cap from 16 KiB to 128 KiB (server/provider/omp-rpc-transport.ts:890);package.jsonmoves runtime@getpaseo/protocoland dev@getpaseo/*to 0.11.0-beta.5. - Install-time commands:
paseo-plugin.jsonbuildisnode scripts/prepare-dependencies.mjs, read in full and described above; byte-identical to 1.2.0. No manifestinstall.package.jsonhas nopreinstall,install,postinstall, orprepare. - Dependencies: runtime
@getpaseo/protocol0.11.0-beta.5 (Paseo's protocol types, depends onzodandsemver, no install scripts),@modelcontextprotocol/sdk1.30.0,yaml^2.9.0; only the protocol version changes. The monorepo hasbun.lockand no npm lockfile: all 1076 registry entries carry sha512integrity, with no git or tarball sources. - Hosts: none added; only the existing
github.comlinks. - Credentials and environment: none added; existing reads such as
PASEO_OMP_RUN_DIRinserver/paths.tsare unchanged. - Filesystem: no change.
- Execution: none added. Existing
spawncalls inserver/provider/omp-rpc-process.ts,server/provider/omp-rpc-transport.ts,server/provider/mcp-transport.ts, andserver/provider-diagnostics.tsstart OMP and MCP processes, unchanged. Noeval,new Function, or dynamicimport(). - Runtime installs: none.
- Source match: every file is byte-identical to
paseo-omp/at8e8dfa1exceptpackage.json, wherecatalog:specifiers are replaced by the root catalog's versions. Readable TypeScript, nothing bundled. - Listing media:
plugin-manager.pngandworkspace-settings.png, each HTTP 200image/png. - Overview: missing in the 1.3.0 package and in
paseo-omp/at8e8dfa1; the registry copy still says alpha preview. - Decision: needs-maintainer, on question 1.
- Reviewed commit:
f0b773febc0a22d5400c7c9262d94628fc474abb
omercnet/omp: {"kind":"npm","package":"@omercnet/paseo-omp","version":"1.2.0","resolved":"https://registry.npmjs.org/@omercnet/paseo-omp/-/paseo-omp-1.2.0.tgz","integrity":"sha512-ueZede5D34hoNrdF4y6DBaomErA+hHcv+bcz0Sd6eArQKqF8L6ecKXdBe2tEZd3Ev8uQwxMHuiDQhMBx3q6gOw=="} -> {"kind":"npm","package":"@omercnet/paseo-omp","version":"1.3.0","resolved":"https://registry.npmjs.org/@omercnet/paseo-omp/-/paseo-omp-1.3.0.tgz","integrity":"sha512-XWhtFVbCZujr9trSQZWdfR5XqLuKtO10BR+o9vykNaR6Hwh0Siweom8mmokwqxscLXIp/yYfWlf2OBbY9WMpQQ=="}Provenance verified: built from https://github.com/omercnet/paseo-plugins/tree/HEAD/paseo-omp at
8e8dfa1aebbe7c23673f344e75d93dfac91daba9.Submitted by @omercnet.
Merging approves this version. The published index keeps pointing at the previous one until then.
Artifact diff
This version has no OVERVIEW.md. The registry requires one to update a listing; the bump cannot merge until the repository adds it.
Inline validation failed. See the Bump workflow log.