@tempots/beatui 0.0.2 → 0.0.3

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -129,6 +129,12 @@ pnpm run release:major
129
129
  # Prerelease (0.0.1 → 0.0.2-0) - for beta/alpha versions
130
130
  pnpm run release:prerelease
131
131
 
132
+ # Release without automatic git commit (manual git handling)
133
+ pnpm run release:patch:no-commit
134
+ pnpm run release:minor:no-commit
135
+ pnpm run release:major:no-commit
136
+ pnpm run release:prerelease:no-commit
137
+
132
138
  # Test publishing without actually publishing
133
139
  pnpm run release:dry
134
140
 
@@ -143,6 +149,9 @@ pnpm run version:next:prerelease # Shows next prerelease version
143
149
 
144
150
  # Prepare package for release (clean, build, test) without publishing
145
151
  pnpm run release:prepare
152
+
153
+ # Test what commit message would be created
154
+ pnpm run release:commit:dry
146
155
  ```
147
156
 
148
157
  ### Release Process
@@ -151,12 +160,14 @@ Each release script follows this workflow:
151
160
  1. **Prepare**: Clean previous builds, build package, run all tests
152
161
  2. **Version**: Update the version number in package.json and create git tag
153
162
  3. **Publish**: Publish to npm (bypassing git checks since version step creates changes)
163
+ 4. **Commit**: Add package.json changes and commit with release message
154
164
 
155
165
  The workflow ensures that:
156
166
  - All tests pass before any version changes
157
167
  - Package builds successfully before publishing
158
168
  - Git tags are created for version tracking
159
169
  - Git check conflicts are avoided by using `--no-git-checks` after versioning
170
+ - Release commits are automatically created with descriptive messages
160
171
 
161
172
  ### Release Guidelines
162
173
 
@@ -167,6 +178,30 @@ The workflow ensures that:
167
178
 
168
179
  **Note**: Prerelease versions are published with the `next` tag, so they won't be installed by default with `npm install @tempots/beatui`.
169
180
 
181
+ ### Git Integration
182
+
183
+ **Automatic Git Commits (Default)**
184
+
185
+ The main release scripts automatically commit version changes after successful publish:
186
+ - Add the updated `package.json` to git staging
187
+ - Create a commit with the message: `chore: release @tempots/beatui@{version}`
188
+ - This keeps your git history in sync with published versions
189
+
190
+ Example commit messages:
191
+ - `chore: release @tempots/beatui@1.0.0`
192
+ - `chore: release @tempots/beatui@1.1.0`
193
+ - `chore: release @tempots/beatui@1.0.1`
194
+
195
+ **Manual Git Handling**
196
+
197
+ If you prefer to handle git commits manually, use the `:no-commit` variants:
198
+ - `pnpm run release:patch:no-commit`
199
+ - `pnpm run release:minor:no-commit`
200
+ - `pnpm run release:major:no-commit`
201
+ - `pnpm run release:prerelease:no-commit`
202
+
203
+ These scripts will publish successfully but leave git operations to you.
204
+
170
205
  ## License
171
206
 
172
207
  MIT