Skip to content

Align Components public entry points - #180

Merged
woksin merged 8 commits into
feat/react-aria-foundationfrom
public-surface/ecosystem-readme
Aug 25, 2026
Merged

Align Components public entry points#180
woksin merged 8 commits into
feat/react-aria-foundationfrom
public-surface/ecosystem-readme

Conversation

@woksin

@woksin woksin commented Aug 25, 2026

Copy link
Copy Markdown
Contributor

Summary

Stack the ecosystem README and canonical Components entry work on the Components 4 foundation in #177. Align public wording with the current package manifest, migration boundary, and exact Arc relationship without turning the major release evidence into broad quality or accessibility claims.

Dependency and merge order: this PR targets feat/react-aria-foundation and should be human-reviewed and merged into that feature branch before the authorized human final merge of #177. This PR is no-release because merging it into the feature branch publishes nothing. Its commits then become part of #177's reviewed major effect packet and the Components 4 package/site release. Do not merge #177 to main until this public wording is included and reviewed.

Declared effects: merging this PR into the feature branch changes only the unmerged Components 4 candidate. The later human-final merge of #177 may publish the Components 4 npm package, GitHub release, package README, and dispatched cratis.io page under #177's complete major effect packet. Workflow changes also become part of that major candidate and affect later release-intent/no-release verification.

Changed

  • Lead with the exact Arc-aligned React component-library scope and the Components 4 package's Cratis-owned markup, public types, semantic-token, stable-part, provider, and migration boundaries.
  • Align repository, package, and canonical documentation entry points with the Components 4 manifest and remove obsolete PrimeReact 11/PrimeUI setup from the public path.
  • Preserve explicit non-claims for design-system completeness, accessibility conformance, browser coverage, support, security, and production suitability.
  • Accept exactly one major, minor, patch, or no-release intent and keep genuine release-action errors fail-closed.
  • Reconcile the advanced Components 4 base without rebasing, preserve the setup-only package root and explicit capability subpaths, and document migration/codemod behavior without claiming publication before release.

Fixed

  • Make root/package links and verification package-rendering safe.
  • Add contribution and private security routes without creating support or response-time commitments.
  • Keep package/license language bounded to exact manifests, notices, and packaged artifacts.
  • Replace unsupported accessibility/support/security/compatibility/roadmap/legal conclusions with concrete current implementation facts and nearby non-inference limits.
  • Correct provider imports, the custom Dialog example, branch-only links, capability-profile language, and package migration wording against the advanced source.

Verification

Current head: d2ffdc0fd9518ade92eceafa9c387697c92e72e0 after concurrent Components 4 hardening was merged into this branch.

  • Reconciled current feat/react-aria-foundation through true merge commits; PR conflict is resolved without history rewriting.
  • Documentation gate: 103 files, 0 lint issues; 168 local links and 26 package-context links, 0 broken.
  • Workspace tests: Components 276/276 files and 852/852 tests; ESLint 78/78; codemods 45/45.
  • Package build: bundled CSS/assets, source maps, style isolation, 25/25 exports, and public API/TSDoc gates passed.
  • Provisional exact-head RC.10 archives from d2ffdc0: @cratis/components 637,795 bytes / 6d2b1c920f73d730ab4085eab2a966b8845c0266213dbaf23fddfb9958534c8b; @cratis/components-codemods 8,432 bytes / 8dad5c25f877562153659841b77097ea9c0676b2fb45fced07e8499cb966acd2; @cratis/eslint-plugin-components 12,928 bytes / 2d6ab3615923a2ab88c7666d29030d2abb4d0c61c44eedbc56058f333d5f2f24.
  • Archive/notices/CSS budget, 21-subpath dependency graph, no-Pixi consumer, spatial consumer, provider-context identity, strict TypeScript 6 public types, ESLint package, and codemod package gates passed.
  • This archive is pre-merge candidate evidence only. After an authorized human merges Align Components public entry points #180 into the feature branch, regenerate and bind the complete three-workspace archive/effect packet to the resulting exact Ship the renderer-independent Components 4 foundation #177 head before major human-final merge.

@woksin woksin added the no-release Merging publishes no package, image, release, or deployment label Aug 25, 2026
@woksin
woksin changed the base branch from main to feat/react-aria-foundation August 25, 2026 09:51
# Conflicts:
#	.github/workflows/publish.yml
#	Codemods/README.md
#	Documentation/ui-foundation.md
@woksin

woksin commented Aug 25, 2026

Copy link
Copy Markdown
Contributor Author

Reconciled this branch with the latest Components 4 hardening head (04a7017) in merge commit d2ffdc0; #180 is now conflict-free and mergeable.

Conflict resolution preserved both claim-safe public-surface wording and the final technical contracts:

  • publish and JavaScript caches no longer restore ignored generated lockfiles;
  • setup-only root and explicit migration wording remain accurate;
  • exact public-type exception pairing/version bounds remain documented;
  • npm/pnpm/Yarn-PnP Pixi absent/present topology claims match the CI matrix;
  • codemod README remains valid from the packed package context without claiming an unpublished stable package.

Fresh reconciliation checks passed locally:

  • codemod: 50 tests + packed CLI;
  • ESLint: 87 tests + packed plugin;
  • Markdown lint and local links: clean;
  • Components packed archive notices, migration file/links, assets, and CSS budgets: clean;
  • all three owned workflows pass actionlint;
  • public privacy scan: clean.

Human review is still required by #177's declared merge order; this update does not enable auto-merge or merge #180.

@woksin
woksin requested a review from einari August 25, 2026 15:18
@woksin

woksin commented Aug 25, 2026

Copy link
Copy Markdown
Contributor Author

Provisional exact-head RC.10 artifacts packed from reconciled commit d2ffdc0fd9518ade92eceafa9c387697c92e72e0 (for review only; not publication/final #177 evidence):

Package Bytes SHA-256
@cratis/components@4.0.0-rc.10 637,795 6d2b1c920f73d730ab4085eab2a966b8845c0266213dbaf23fddfb9958534c8b
@cratis/components-codemods@4.0.0-rc.10 8,432 8dad5c25f877562153659841b77097ea9c0676b2fb45fced07e8499cb966acd2
@cratis/eslint-plugin-components@4.0.0-rc.10 12,928 2d6ab3615923a2ab88c7666d29030d2abb4d0c61c44eedbc56058f333d5f2f24

The Components archive gate passed, including LICENSE/notices/assets, shipped MIGRATION.md, packed-context links, and aggregate CSS budgets. Regenerate after any review change or after integration; these receipts deliberately remain provisional while #180 is open.

@woksin

woksin commented Aug 25, 2026

Copy link
Copy Markdown
Contributor Author

Hosted CI is green for exact reconciled head d2ffdc0fd9518ade92eceafa9c387697c92e72e0: 18 completed check runs, zero pending, zero failures. The PR is MERGEABLE/CLEAN. Required human review remains pending; no auto-merge is enabled.

@woksin
woksin merged commit d2ffdc0 into feat/react-aria-foundation Aug 25, 2026
18 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

no-release Merging publishes no package, image, release, or deployment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant