// Guides the UUI package release process including stable and beta releases, changelog updates, and handling failed releases. Use when releasing UUI packages, updating changelog, or troubleshooting release issues. For maintainers only.
Helps create and modify UUI (EPAM Unified UI) components following established patterns. Use when creating new components, modifying existing components, working with withMods, component props, styling, or component architecture in the UUI library.
Helps work with UUI DataSources (ArrayDataSource, LazyDataSource, AsyncDataSource) powering PickerInput, DataTable, FiltersPanel, and other data-driven components. Use when implementing or fixing features that load, filter, sort, or display lists of data.
Helps update UUI documentation, add doc examples, configure Property Explorer, and manage component API documentation. Use when adding documentation examples, updating Property Explorer configs, generating API references, working with UUI documentation site, or when adding/removing/modifying public props on component interfaces.
Helps create and maintain E2E and screenshot tests for UUI components using Playwright. Use when adding E2E tests, creating screenshot tests, updating preview configurations, or working with Property Explorer previews for testing.
Fetches GitHub issues from URLs and creates implementation plans for UUI. Use when the user provides a GitHub issue link (github.com/.../issues/N), asks to plan work from an issue, or implement/fix an issue by URL.
Guides the UUI pull request process including branch naming, pre-PR checklist, changelog updates, and quality requirements. Use when preparing a pull request, writing commit messages, or following UUI PR requirements.
| name | uui-release-workflow |
| description | Guides the UUI package release process including stable and beta releases, changelog updates, and handling failed releases. Use when releasing UUI packages, updating changelog, or troubleshooting release issues. For maintainers only. |
Always ask for explicit user permission before running yarn release or yarn release-beta. These commands publish packages to npm and cannot be undone. Never publish to npm without confirming the user intends to do so.
Before asking for permission, provide a pre-publish summary:
changelog.md top section or Lerna)package.json workspaces)changelog.md entryThen ask the user to confirm before running the release command.
main branchchangelog.md with all released changesyarn buildyarn releaseProvide pre-publish summary, then ask user for permission before running. Use beta dist-tag instead of latest:
yarn release-beta
If using MFA, login with access token:
npm config set //registry.npmjs.org/:_authToken=your_token
If release fails and packages aren't published, revert Lerna commits and tags:
git tag -d <tag_name> (e.g., v5.7.0)git push --delete origin <tag_name>mainyarn build)