@winchsa/ui 0.1.9 → 0.1.10

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.
Files changed (2) hide show
  1. package/README.md +7 -22
  2. package/package.json +2 -2
package/README.md CHANGED
@@ -120,28 +120,13 @@ This script compiles the UI package, generates a tarball, and installs it into y
120
120
 
121
121
  ## Release Process
122
122
 
123
- This project uses a **tag-based release system** that automatically publishes to npm only when you push version tags. This ensures you have full control over when releases are published.
123
+ The `bump` command in `package.json` does the following:
124
124
 
125
+ 1. `pnpm version patch`: Increments the patch version of the package (e.g., from `0.1.9` to `0.1.10`).
126
+ 2. `pnpm run build`: Builds the project.
127
+ 3. `git add .`: Stages all changes for commit.
128
+ 4. `git commit -m "chore: release v$(node -p \"require('./package.json').version\")"`: Creates a new commit with a message indicating a release, including the new version number.
125
129
 
126
- ### **Option 1: Using the Release Script (Recommended)**
127
- ```bash
128
- # Complete automated release process
129
- pnpm run release
130
- ```
131
-
132
- ### **Option 2: Manual Tag-Based Release**
133
- ```bash
134
- # 1. Update version in package.json
135
- # 2. Build the package
136
- pnpm run build
137
-
138
- # 3. Commit your changes
139
- git add .
140
- git commit -m "feat: new features"
141
-
142
- # 4. Create and push a tag
143
- git tag v1.2.3
144
- git push origin master --tags
130
+ **Publishing**
145
131
 
146
- # GitHub Actions will automatically trigger and publish to npm
147
- ```
132
+ After running `pnpm run bump`, go to **GitHub** **Releases** and create a new release based on the commit generated. This will trigger the `publish.yaml` GitHub Actions workflow, which handles the actual publishing process
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@winchsa/ui",
3
- "version": "0.1.9",
3
+ "version": "0.1.10",
4
4
  "type": "module",
5
5
  "private": false,
6
6
  "publishConfig": {
@@ -64,6 +64,6 @@
64
64
  "build": "unbuild",
65
65
  "lint": "eslint \"**/*.{ts,vue,mjs,json}\"",
66
66
  "lint:fix": "eslint \"**/*.{ts,vue,mjs,json}\" --fix",
67
- "release": "pnpm version patch && pnpm run build && git add . && git commit -m \"chore: release v$(node -p \"require('./package.json').version\")\" && git tag v$(node -p \"require('./package.json').version\") && git push origin master --tags && pnpm publish"
67
+ "bump": "pnpm version patch && pnpm run build && git add . && git commit -m \"chore: release v$(node -p \"require('./package.json').version\")\""
68
68
  }
69
69
  }