[gabipodolnikova]

What: Migrates Felt React task execution and the prerelease CI workflow from Lerna to Nx for FELT-144.

Draft: docs/chore policy is agreed and implemented. Remaining commit-type policy is still being aligned with the Core migration.

Implementation

• Pin Nx and @nx/js to 24.0.0 and replace root Lerna task commands with Nx.
• Configure independent releases for the ten public Felt packages. Native Nx change/dependent discovery is followed by explicit native prerelease bumps, preserving each selected package’s existing counter (for example, .3 → .4).
• Preserve Lerna’s package-specific {projectName}@{version} Git tags and release commit subject, chore(release): releasing packages [ci skip].
• Use Nx to stage version changes, generate changelogs, create the combined release commit and per-package tags, and push before publication. Yarn then packs the selected packages with resolved workspace references.
• Upload the complete .release/ bundle, including hidden files, before publishing through Nx using the existing npm trusted-publishing/OIDC setup. A missing expected artifact fails the upload step.
• Post PR release comments as a separate notification step. Notification failures emit warnings without marking successful publication as failed.

Behavior changes and discussion points

• Agreed docs/chore policy (implemented): docs: triggers release discovery so downstream consumers receive documentation updates, but is hidden from changelogs (semverBump: patch, changelog: false). Ordinary chore: commits neither independently trigger a release nor appear in changelogs (semverBump: none, changelog: false). Selected prerelease packages still increment their existing counters.
• Other commit types: fix and feat use the native Nx defaults. The current overrides for refactor, perf, test, style, build, and ci still trigger release discovery and appear in changelogs; alignment of those types remains open.
• Manual releases: a workflow to request a new release for otherwise non-releasing maintenance changes is deferred. The publishing-only recovery workflow below retries existing prepared versions; it does not create a new release.
• Non-conventional messages: ordinary unrecognized/non-conventional commits currently do not trigger a release or appear in changelogs. Discuss whether __INVALID__ should appear under “Uncategorized changes” without triggering a bump. Valid but unconfigured types such as misc: are separate from __INVALID__.
• Selection differs from Lerna: Nx uses its affected graph and conventional commits. Root build/configuration changes can select all ten packages, including the first cutover release. The historical Styles case matched the seven public packages selected by Lerna, but this does not establish universal selection parity.
• Independent versions: each package keeps its own counter; different package counters are normal. Private demo-app-ts is intentionally excluded from release version bumps.
• Changelogs: retain Nx’s default headings/icons and dependency-update entries. Actions uses the canonical origin; local fork rehearsals can pass --git-remote=upstream.
• Concurrency: normal and recovery releases share one felt-v1 concurrency group. New merges no longer automatically cancel an active publication. GitHub may replace pending runs; this does not promise a separate release for every merge. Manual cancellation during publishing can still leave a partial release.

Publishing-only recovery

A manual run of the same release.yml workflow on felt-v1 takes the failed workflow run ID, downloads its nx-release-packages artifact, and checks out the recorded release commit. It installs dependencies without rebuilding packages, then publishes the prepared versions.

• Recovery requires the complete original bundle and a matching checkout. It never recalculates versions, regenerates changelogs, or repacks/rebuilds packages.
• It fetches current release history and accepts only the latest recorded release commit on felt-v1. Older releases are rejected before publication to prevent moving the npm prerelease tag backward.
• Nx handles already-published versions; failed or missing publish results fail the job.
• Artifacts are retained for 30 days. Missing, expired, or incomplete bundles fail clearly rather than being silently regenerated.
• Dispatch must target felt-v1, for example: gh workflow run release.yml --repo patternfly/patternfly-react --ref felt-v1 -f publish-only-run-id=RUN_ID. The Actions UI dispatch button depends on the default-branch workflow definition; GitHub-hosted invocation still needs verification.

Testing

• Immutable install and full package/UMD builds passed in an isolated worktree.
• All 26 release tests passed, covering orchestration, counter-only increments, stale/incomplete bundles, missing metadata, and partial-publication failures.
• Prettier, ESLint, Actionlint, shell syntax, and diff checks passed.
• Historical Styles PR rehearsal selected the same seven public packages as the recorded Lerna release and advanced their versions from .2 to .3.
• Native Nx publish dry run passed for those seven prepared packages. Checksums confirmed the archives, package manifests, and changelogs remained byte-identical during the recovery rehearsal.
• Stale rejection was exercised against fetched release history. Successful recovery used an injected latest-release identity, with the native publisher forced to dry-run. No real release commits, tags, pushes, or npm publications were performed during the rehearsal.

follow-up:

• Define the prerelease → stable promotion lifecycle, migrate Promote (which still uses Lerna), then remove the remaining Lerna dependency/configuration. Stable promotion is not implemented by this PR.

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

Run configuration

• Source mode: Auto
• Repository: Unavailable
• Branch: Unavailable
• File: No configuration file from this repository applied
• Commit: Unavailable
• Layers: Organization UI
• Review profile: CHILL
• Plan: Advanced
• Run ID: f3c01ea8-7cc6-4363-ba51-cf4094b491de

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[rebeccaalpert]

Looks great to me! :)

[rebeccaalpert]

Confirming these are ok @kmcfaul @wise-king-sullyman?

[rebeccaalpert]

Do we need the message if we are not committing anything?