Skip to content

feat(cli): add publish-manifest with S3/HTTP registry support#14

Open
fotopixel wants to merge 1 commit into
mainfrom
feat/publish-manifest
Open

feat(cli): add publish-manifest with S3/HTTP registry support#14
fotopixel wants to merge 1 commit into
mainfrom
feat/publish-manifest

Conversation

@fotopixel

Copy link
Copy Markdown
Contributor

Summary

  • Adds fwiz publish-manifest to generate versioned mf-manifest.json files from fwiz.config.yaml and publish them to a configurable registry
  • Extends config schema with an optional registry section supporting HTTP PUT and S3-compatible backends
  • Maintains a central remotes-registry.json with version history and supports rollback via --rollback

Closes #6

Test plan

  • pnpm nx test @federation-wizards/core — manifest generation, local registry round-trip, HTTP mock server, mocked S3
  • pnpm nx test @federation-wizards/fwiz — CLI publish/rollback smoke test
  • pnpm nx build @federation-wizards/core
  • pnpm nx build @federation-wizards/fwiz
  • Configure registry in fwiz.config.yaml and run fwiz publish-manifest --dry-run
  • Publish to a real HTTP or S3-compatible endpoint and verify remotes-registry.json updates
  • Run fwiz publish-manifest --rollback --remote <name> against a multi-version registry

Made with Cursor

Enable versioned mf-manifest.json generation, central remotes-registry.json
updates, and rollback so hosts can consume remotes from a configurable CDN.

Co-authored-by: Cursor <cursoragent@cursor.com>
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.

Implement fwiz publish-manifest & Registry Management

1 participant