@ainame/tuzuru 0.2.0 → 0.3.0
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 +16 -0
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -325,3 +325,19 @@ When files are modified, the blog is regenerated on the next HTTP request, provi
|
|
|
325
325
|
|
|
326
326
|
- Swift 6.1+
|
|
327
327
|
- macOS v15+
|
|
328
|
+
|
|
329
|
+
## Release
|
|
330
|
+
|
|
331
|
+
Tuzuru uses a PR-based release flow with automated tagging.
|
|
332
|
+
|
|
333
|
+
- Prepare PR (bumps versions, updates composite actions, runs build/tests):
|
|
334
|
+
- `scripts/release.sh 1.2.3` (shortcut for `prepare`)
|
|
335
|
+
- `scripts/release.sh prepare 1.2.3`
|
|
336
|
+
|
|
337
|
+
- After the PR is merged into `main`, a GitHub Actions workflow automatically creates and pushes the git tag (no `v` prefix). That tag triggers the Release workflow to build binaries, create the GitHub Release, and publish to npm.
|
|
338
|
+
|
|
339
|
+
Notes:
|
|
340
|
+
- The script updates `Sources/Command/Command.swift`, `package.json`, `Formula/tuzuru.rb` (if present), and internal composite actions to reference the new npm version.
|
|
341
|
+
- Tags do not use a `v` prefix (e.g., use `1.2.3`).
|
|
342
|
+
- If automation is ever unavailable, a fallback command exists: `scripts/release.sh tag <version>`.
|
|
343
|
+
- If `gh` (GitHub CLI) is installed, the script opens a PR automatically; otherwise, push branch `release/<version>` and open a PR manually.
|