You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
chore(release): bump to v1.0.0 for React 19 compatibility (#182)
* chore(release): bump to v1.0.0 for React 19 compatibility
This release marks the stable 1.0.0 major version for the React 19 line. All packages have been bumped to 1.0.0.
Key updates include:
- Finalizing Tailwind CSS v4 migration.
- Comprehensive accessibility improvements.
- Updated documentation to reflect the new major release and branch strategy.
- Add `@halvaradop/ui-utils`
- Add `@halvaradop/ui-slot`
- Clean up `@halvaradop/ui-core`
* docs(changelogs): document bumped version
* docs(changelog): add `v1.0.0` version
* docs(standards): update `CONTRIBUTING.md` for `v1.0.0` stable releas
* docs(standards): update `ARCHITECTURE.md` file for `v1.0.0`
* docs(standards): document `[SYNC]` preffix
* docs(contributing): document `[SYNC]` preffix
* docs(changelogs): add missing text
* chore(ui-radio): remove `@halvaradop/ui-radio` package in v1.0.0
* docs(readme): update `README.md` files
* build(deps): update `peerDependencies`
- After the next major release, `main` will track React 19, and React 18 will move to `react-18` for legacy maintenance.
77
+
-`master`: This is the **primary development branch** for the library. It is currently optimized for **React 19** and leverages **Tailwind CSS v4**. All new features, major improvements, and active development efforts are focused here.
78
+
-`legacy/react-18`: This branch serves as a **legacy support line** for **React 18**. It will receive critical bug fixes and security updates but is not intended for new feature development.
79
+
80
+
### Strategy for Branch Transition
81
+
82
+
This diagram illustrates the process of transitioning the primary development line:
80
83
81
84
```mermaid
82
85
sequenceDiagram
83
-
participant Master
84
-
participant Beta
85
-
Master->>Beta: Create sync branch
86
-
Beta->>Beta: Resolve React 19 conflicts
87
-
Beta->>Beta: Update dependencies
88
-
Beta->>Beta: Verify functionality
86
+
participant OldMaster as master (React 18)
87
+
participant Beta as beta (React 19 Development)
88
+
participant NewMaster as master (React 19)
89
+
participant LegacyBranch as legacy/react-18
90
+
91
+
OldMaster->>LegacyBranch: Renamed to legacy/react-18
92
+
Beta->>NewMaster: Renamed to master (now main development branch)
93
+
94
+
Note over NewMaster, LegacyBranch: After transition:
95
+
NewMaster->>NewMaster: Active development for React 19
96
+
LegacyBranch->>LegacyBranch: Support and critical fixes for React 18
89
97
```
90
98
99
+
### Current Synchronization Strategy
100
+
101
+
While `master` (React 19) is the primary branch, if critical fixes or foundational changes are applied to `legacy/react-18` that also benefit `master`, synchronization will occur.
102
+
103
+
```mermaid
104
+
sequenceDiagram
105
+
participant Master(React 19)
106
+
participant Legacy/react-18(React 18)
107
+
108
+
Legacy/react-18->>Master(React 19): If critical fixes occur, synchronize
During the parallel development phase—when the beta branch (now `master`) was being prepared for React 19 while the `master` branch (now `legacy/react-18`) remained active for React 18—we used a specific commit prefix:
115
+
116
+
-[SYNC]: Commits prefixed with [SYNC] indicate changes that were synchronized from the `master` branch (React 18) into the beta branch (React 19). This ensured that critical bug fixes, security updates, or foundational changes from the stable React 18 line were consistently integrated into the upcoming React 19 version.
117
+
118
+
Although the presence of these [SYNC] prefixes can add some noise to the commit history of the current `master` branch, we have chosen to preserve them rather than remove them. This decision was made to maintain the integrity of the repository tree and avoid breaking the commit history between the previous branches (`master` and beta). Removing these prefixes would have resulted in greater issues with traceability and understanding the complete repository history in the future.
119
+
91
120
## Internal Utilities
92
121
93
122
-`@halvaradop/ui-core`: Shared logic (e.g., `merge`, SlotProps, HTML typing).
Copy file name to clipboardExpand all lines: CHANGELOG.md
+26Lines changed: 26 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,6 +12,32 @@ Per-package version history is maintained inside each package’s own `CHANGELOG
12
12
13
13
---
14
14
15
+
## [1.0.0] - 2025-06-09
16
+
17
+
> **Stable release for React 19**
18
+
>
19
+
> Version **1.0.0** is published as the first stable release of the library, now fully compatible and optimized for **React 19**.
20
+
>
21
+
> **This version is a direct promotion of the latest pre-release (`1.0.0-next.n`)** after successfully passing stability and regression tests in real-world environments. It includes all changes, improvements, and fixes introduced during the `next` phase.
22
+
>
23
+
> **Recommended update for all users**
24
+
>
25
+
> It is strongly recommended to update to this stable version to take advantage of the latest features, performance improvements, and security optimizations. Users who still depend on React 18 can continue using the `legacy/react-18` support branch, available on npm under the `legacy` tag.
26
+
>
27
+
> ### Main changes in version 1.0.0
28
+
>
29
+
> -**Full compatibility with React 19:** All components have been reviewed, validated, and optimized to ensure correct and efficient operation with React 19.
30
+
> -**Complete migration to Tailwind CSS v4:** Finalizes the migration started in the pre-release, adopting the new capabilities, performance improvements, and configuration changes of Tailwind CSS v4.
31
+
> -**Accessibility (a11y) improvements:** The components now includes WAI-ARIA attributes and adjustments for a more inclusive and standards-compliant accessibility experience.
32
+
33
+
-**Removal of the Radio package:** The `@halvaradop/ui-radio` package has been removed in this release. If your project depends on radio components, please migrate to an alternative or continue using a previous version.
34
+
> ### Important notes
35
+
>
36
+
> - This version **does not introduce additional changes** compared to the pre-release `1.0.0-next.1`, except for its promotion to stable after passing all validation and regression tests.
37
+
> - From this version onward, maintenance and new features will focus on compatibility with React 19 and Tailwind CSS v4.
38
+
39
+
---
40
+
15
41
## [next pre-publish] - 2025-06-08
16
42
17
43
- Published pre-release (`next`) versions for all major monorepo packages ([#170](https://github.com/halvaradop/ui/pull/170)):
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+17-17Lines changed: 17 additions & 17 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -60,10 +60,9 @@ pnpm clean # Clean the project
60
60
61
61
## 🌿 Branching Strategy
62
62
63
-
-`master`: Current stable branch (React 18, will become legacy)
64
-
-`beta`: React 19 development branch (will become new `main`)
65
-
66
-
Use `[SYNC]` prefix to indicate synchronization PRs between branches.
63
+
-**`master`**: The main development branch. Represents the latest stable release (currently React 19).
64
+
-**`legacy/react-18`**: Maintains support for React 18. Only accepts critical fixes, bug patches, and minimal changes required for legacy compatibility.
65
+
- Use the `[SYNC]` prefix in pull request titles to clearly indicate synchronization PRs that merge changes between branches (e.g., from `master` to `legacy/react-18`).
67
66
68
67
---
69
68
@@ -144,18 +143,19 @@ chore: upgrade dependencies
144
143
145
144
## 🚀 Pull Request Process
146
145
147
-
1. Use a descriptive title and body
148
-
2. Reference any related issues or PRs
149
-
3. Add screenshots for UI changes
150
-
4. Ensure all tests and builds pass
151
-
5. Label PRs appropriately:
152
-
- `breaking`
153
-
- `accessibility`
154
-
- `[SYNC]`
155
-
6. Get approval from a code owner
146
+
1. Use a descriptive title and body that follow
147
+
2. Reference any related issues or PRs in the body.
148
+
3. Add screenshots or GIFs for UI changes to facilitate review.
Only maintainers listed in the [CODEOWNERS](https://github.com/halvaradop/ui/blob/master/.github/CODEOWNERS) file can approve PRs related to their assigned areas.
158
155
156
+
> Note on [SYNC] commits:
157
+
> Historically, during the transition phase, some commits in the master branch (formerly beta) might be prefixed with [SYNC]. These indicate changes synchronized from the legacy/react-18 branch. As a contributor, you should not use this prefix for new commits; it was specific to a past internal synchronization workflow.
158
+
159
159
---
160
160
161
161
## 🔖 Release Process
@@ -184,10 +184,10 @@ Each package follows [Semantic Versioning](https://semver.org/) independently:
184
184
185
185
Responsibilities:
186
186
187
-
- Review and merge PRs only inassigned scope (see `CODEOWNERS`)
188
-
- Maintain consistency across versions and branches
189
-
- Ensure all packages follow naming and changelog conventions
190
-
- Coordinate `[SYNC]` PRs between `master`, `beta`, and `react-18`
187
+
- Reviewing and merging PRs only within their assigned scope (see `CODEOWNERS`).
188
+
- Maintaining consistency across different versions and branches.
189
+
- Ensuring all packages adhere to naming and changelog conventions.
190
+
- Coordinating any necessary synchronizations between `master`and `legacy/react-18` (though the [SYNC] commit prefix is no longer in active use for new contributions, historical context remains).
Copy file name to clipboardExpand all lines: README.md
+14-9Lines changed: 14 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,15 +1,20 @@
1
-
# @halvaradop/ui@beta
1
+
# @halvaradop/ui
2
2
3
3
A modern, accessible, and customizable React UI component library, organized as a monorepo and styled with TailwindCSS v4. This library provides pre-styled, reusable components to help you build user interfaces faster and more consistently.
4
4
5
5
## Version Compatibility
6
6
7
7
Supports both `React 18` and `React 19`. Use the table below to select the correct library version for your React version:
Copy file name to clipboardExpand all lines: packages/ui-button/CHANGELOG.md
+26Lines changed: 26 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,6 +9,32 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
9
9
10
10
---
11
11
12
+
## [1.0.0] - 2025-06-09
13
+
14
+
> **Stable release for React 19**
15
+
>
16
+
> Version **1.0.0** is published as the first stable release of the library, now fully compatible and optimized for **React 19**.
17
+
>
18
+
> **This version is a direct promotion of the latest pre-release (`1.0.0-next.n`)** after successfully passing stability and regression tests in real-world environments. It includes all changes, improvements, and fixes introduced during the `next` phase.
19
+
>
20
+
> **Recommended update for all users**
21
+
>
22
+
> It is strongly recommended to update to this stable version to take advantage of the latest features, performance improvements, and security optimizations. Users who still depend on React 18 can continue using the `legacy/react-18` support branch, available on npm under the `legacy` tag.
23
+
>
24
+
> ### Main changes in version 1.0.0
25
+
>
26
+
> -**Full compatibility with React 19:** All components have been reviewed, validated, and optimized to ensure correct and efficient operation with React 19.
27
+
> -**Complete migration to Tailwind CSS v4:** Finalizes the migration started in the pre-release, adopting the new capabilities, performance improvements, and configuration changes of Tailwind CSS v4.
28
+
> -**Accessibility (a11y) improvements:** The components now includes WAI-ARIA attributes and adjustments for a more inclusive and standards-compliant accessibility experience.
29
+
30
+
-**Removal of the Radio package:** The `@halvaradop/ui-radio` package has been removed in this release. If your project depends on radio components, please migrate to an alternative or continue using a previous version.
31
+
> ### Important notes
32
+
>
33
+
> - This version **does not introduce additional changes** compared to the pre-release `1.0.0-next.1`, except for its promotion to stable after passing all validation and regression tests.
34
+
> - From this version onward, maintenance and new features will focus on compatibility with React 19 and Tailwind CSS v4.
35
+
36
+
---
37
+
12
38
## [1.0.0-next.1] - 2025-06-08 (Version @next for React 19)
13
39
14
40
> **Pre-release for React 19:** This `next` version is published for testing and validation with **React 19** as the base. It allows evaluation in real-world environments before being promoted to a stable release. The previous `rc` version was based on React 18.
Copy file name to clipboardExpand all lines: packages/ui-checkbox/CHANGELOG.md
+26Lines changed: 26 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,6 +9,32 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
9
9
10
10
---
11
11
12
+
## [1.0.0] - 2025-06-09
13
+
14
+
> **Stable release for React 19**
15
+
>
16
+
> Version **1.0.0** is published as the first stable release of the library, now fully compatible and optimized for **React 19**.
17
+
>
18
+
> **This version is a direct promotion of the latest pre-release (`1.0.0-next.n`)** after successfully passing stability and regression tests in real-world environments. It includes all changes, improvements, and fixes introduced during the `next` phase.
19
+
>
20
+
> **Recommended update for all users**
21
+
>
22
+
> It is strongly recommended to update to this stable version to take advantage of the latest features, performance improvements, and security optimizations. Users who still depend on React 18 can continue using the `legacy/react-18` support branch, available on npm under the `legacy` tag.
23
+
>
24
+
> ### Main changes in version 1.0.0
25
+
>
26
+
> -**Full compatibility with React 19:** All components have been reviewed, validated, and optimized to ensure correct and efficient operation with React 19.
27
+
> -**Complete migration to Tailwind CSS v4:** Finalizes the migration started in the pre-release, adopting the new capabilities, performance improvements, and configuration changes of Tailwind CSS v4.
28
+
> -**Accessibility (a11y) improvements:** The components now includes WAI-ARIA attributes and adjustments for a more inclusive and standards-compliant accessibility experience.
29
+
30
+
-**Removal of the Radio package:** The `@halvaradop/ui-radio` package has been removed in this release. If your project depends on radio components, please migrate to an alternative or continue using a previous version.
31
+
> ### Important notes
32
+
>
33
+
> - This version **does not introduce additional changes** compared to the pre-release `1.0.0-next.1`, except for its promotion to stable after passing all validation and regression tests.
34
+
> - From this version onward, maintenance and new features will focus on compatibility with React 19 and Tailwind CSS v4.
35
+
36
+
---
37
+
12
38
## [1.0.0-next.1] - 2025-06-08 (Version @next for React 19)
13
39
14
40
> **Pre-release for React 19:** This `next` version is published for testing and validation with **React 19** as the base. It allows evaluation in real-world environments before being promoted to a stable release. The previous `rc` version was based on React 18.
0 commit comments