47af9f816a
Per user request: 'use the local Gitea and make sure all packages in Gitea are up to date'. Built all packages from learning_ai_common_plat/packages/* and ran scripts/gitea/publish-outdated-packages.sh against the local Gitea npm registry (http://localhost:3300/api/packages/bytelyst/npm/). Manifest-based hash comparison flagged 4 packages whose built dist/ content has changed since the last published tarball: @bytelyst/auth-ui 0.1.5 → 0.1.6 @bytelyst/config 0.1.7 → 0.1.8 @bytelyst/dashboard-shell 0.1.5 → 0.1.6 @bytelyst/mcp-client 0.1.0 → 0.1.1 All four bumped + published successfully. Remaining 60 packages verified up-to-date. One package skipped by design: @bytelyst/react-native-platform-sdk (RN — not in npm publish set) Also incidentally fixed an mcp-client build break before this run: stale dist/ + node_modules/.cache made tsc think MCPClient was missing a 'log' property, even though the source had been correctly refactored to use a private 'log: McpLogger' field. A clean 'rm -rf dist node_modules/.cache && pnpm build' resolved it; no source changes needed. Files updated: - packages/auth-ui/package.json - packages/config/package.json - packages/dashboard-shell/package.json - packages/mcp-client/package.json - scripts/gitea/.publish-manifest.json (new content hashes) After this commit, every published @bytelyst/* tarball in local Gitea matches the source tree exactly. |
||
|---|---|---|
| .. | ||
| src | ||
| package.json | ||
| tsconfig.json | ||