Skip to content

[codex] Resolve source alpha readiness items#12

Merged
Junnyyy merged 2 commits into
mainfrom
codex/release-alpha-readiness
Jun 9, 2026
Merged

[codex] Resolve source alpha readiness items#12
Junnyyy merged 2 commits into
mainfrom
codex/release-alpha-readiness

Conversation

@Junnyyy

@Junnyyy Junnyyy commented Jun 9, 2026

Copy link
Copy Markdown
Member

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?

  • Clarified root and package docs so package install snippets are future/when-published guidance for the current source/demo alpha
  • Removed stale README non-goal wording that said Latch does not include CI, while preserving that CI is quality gates only and not deployment or npm publishing
  • Bumped the module federation demo apps from @module-federation/vite 1.16.2 to 1.16.4
  • Updated the lockfile so @module-federation/dts-plugin resolves to 2.5.1 and ws resolves to patched 8.21.0
  • Recorded the durable module-federation audit/TypeScript peer learning in AGENTS.md

How to test?

  1. CI=true pnpm install --frozen-lockfile
  2. pnpm build
  3. pnpm test
  4. pnpm typecheck
  5. pnpm lint
  6. pnpm latch report --flags packages/cli/examples/flags.json --src "packages/cli/examples/src/**/*.{ts,tsx}" packages/cli/examples/fixtures/flags.dev.json
  7. pnpm audit --audit-level high
  8. pnpm audit

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.


View with Codesmith Autofix with Codesmith
Need help on this PR? Tag @codesmith with 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 install is the supported path, pnpm add snippets 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 (including pnpm latch report), not deploy or publish automation.

Bumps @module-federation/vite 1.16.2 → 1.16.4 in all three MF demo apps and refreshes the lockfile so DTS tooling pulls @module-federation/dts-plugin 2.5.1 and ws 8.21.0, addressing the moderate ws audit via upstream tooling. AGENTS.md records that fix and that TypeScript 6 peerDependencyRules.allowedVersions should 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.

Junnyyy added 2 commits June 8, 2026 22:41
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.
@Junnyyy Junnyyy marked this pull request as ready for review June 9, 2026 04:39
@Junnyyy Junnyyy merged commit 48c64f6 into main Jun 9, 2026
2 checks passed
@Junnyyy Junnyyy deleted the codex/release-alpha-readiness branch June 9, 2026 04:41
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