[codex] Resolve source alpha readiness items#12
Merged
Conversation
Frame package install snippets as future publish guidance, remove stale no-CI wording, and keep npm publishing out of the current release scope.
Bump the demo apps to @module-federation/vite 1.16.4 so the DTS tooling resolves patched ws 8.21.0 while preserving pnpm strict peer handling and the TypeScript 6 allowance.
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.
TL;DR
Resolved the source/demo alpha release-readiness docs cleanup and the moderate module-federation tooling audit finding without adding npm publishing or release automation.
What changed?
How to test?
Why make this change?
This keeps the public source/demo alpha posture honest: docs no longer imply packages are already available on npm, the root README no longer contradicts the checked-in CI workflow, and the module-federation demo no longer carries the moderate ws advisory. The fix uses an upstream patch-level tooling bump rather than weakening pnpm strict peer handling, changing the TypeScript 6 setup, replacing module federation tooling, or accepting a residual demo-tooling vulnerability.
Need help on this PR? Tag
@codesmithwith what you need. Autofix is disabled.Note
Low Risk
Documentation-only messaging plus devDependency patch bumps in demo apps; no runtime SDK or auth/data-path changes.
Overview
Clarifies source/demo alpha posture in root and package READMEs: workspace clone/
pnpm installis the supported path,pnpm addsnippets are future published-package guidance, and there is no npm publishing workflow. Root non-goals and CLI docs no longer claim Latch lacks CI; they state checked-in CI is quality gates only (includingpnpm latch report), not deploy or publish automation.Bumps
@module-federation/vite1.16.2 → 1.16.4 in all three MF demo apps and refreshes the lockfile so DTS tooling pulls@module-federation/dts-plugin2.5.1 andws8.21.0, addressing the moderatewsaudit via upstream tooling.AGENTS.mdrecords that fix and that TypeScript 6peerDependencyRules.allowedVersionsshould stay until the DTS plugin peer range widens.Reviewed by Cursor Bugbot for commit 84125a5. Bugbot is set up for automated code reviews on this repo. Configure here.