Skip to content

chore: release main - #5287

Merged
eliseo-juan merged 1 commit into
mainfrom
release-please--branches--main
Aug 28, 2026
Merged

chore: release main#5287
eliseo-juan merged 1 commit into
mainfrom
release-please--branches--main

Conversation

@eliseo-juan

Copy link
Copy Markdown
Contributor

🤖 F0 React package stable release 🚀

f0-react: 6.64.0

6.64.0 (2026-08-28)

Features


This PR was generated with Release Please. See documentation.

@eliseo-juan
eliseo-juan merged commit e4e69b6 into main Aug 28, 2026
11 of 13 checks passed
@eliseo-juan
eliseo-juan deleted the release-please--branches--main branch August 28, 2026 07:55
@github-actions github-actions Bot added chore react Changes affect packages/react labels Aug 28, 2026
@eliseo-juan

Copy link
Copy Markdown
Contributor Author

🤖 Created releases:

🌻

@github-actions

Copy link
Copy Markdown
Contributor

🔍 Review policy: Code change

Default rule: any other change needs one approval from f0-devs (rule 4).

Required approvals

Team Why Status
@factorialco/f0-devs Every code change needs a dev approval ⏳ pending
How this was decided
  • PRs touching only sds/ modules require their owners and nothing else.
  • Otherwise, docs-only changes (*.md, *.mdx, *.stories.tsx, anything in __stories__/) → one f0-general approval.
  • Otherwise, feat: titles → one f0-devs and one f0-designers approval. Not a feature? Fix the title prefix.
  • Anything else → one f0-devs approval.
  • Add the needs-design-review label to also request a design approval on any PR.
  • Creating a new sds/ module (new package.yml) additionally requires an f0-general approval.

Policy source: ownership/review-policy.ts · Team members: ownership/teams.yml

@github-actions

Copy link
Copy Markdown
Contributor

✅ No untranslated copy added

Every user-visible string in this PR comes from the i18n layer. Codebase total unchanged at 133.

@github-actions

Copy link
Copy Markdown
Contributor

✅ No New Circular Dependencies

No new circular dependencies detected. Current count: 0

@github-actions

github-actions Bot commented Aug 28, 2026

Copy link
Copy Markdown
Contributor

✅ Storybook docs — no pages lost

Every page reachable on main is still reachable here.

Links point at this PR's Storybook build — browse the full Storybook.

Snapshot of the Storybook index (docs pages + stories) compared against main. Non-blocking.

@github-actions

Copy link
Copy Markdown
Contributor

🔍 Visual review for your branch is published 🔍

Here are the links to:

@github-actions

Copy link
Copy Markdown
Contributor

✅ No breaking public API changes

No public exports were removed, renamed, or had existing props/types changed in a breaking way compared to main.

Comparing f0, experimental and ai against main. Adding components, types, or optional props is safe. This check is non-blocking.

⚠️ Could not analyze component-status (no-base) — a build may have failed; results may be incomplete.

@github-actions

Copy link
Copy Markdown
Contributor

♿ Accessibility (axe) — components changed in this PR

✅ No a11y issues in the stories this PR changed.

Scope: only stories in the files/component folders this PR changed. It can't yet flag downstream ripple from shared-code/token changes, or diff against main (planned: base-vs-head delta).

@github-actions

Copy link
Copy Markdown
Contributor

Coverage Report for packages/react

Status Category Percentage Covered / Total
🔵 Lines 69.15% 29296 / 42360
🔵 Statements 68.11% 30994 / 45502
🔵 Functions 61.97% 6981 / 11264
🔵 Branches 61.87% 22005 / 35566
File CoverageNo changed files found.
Generated in workflow #17591 for commit a1c4044 by the Vitest Coverage Report Action

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

autorelease: tagged chore react Changes affect packages/react

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant