Skip to content

Commit af9603d

Browse files
committed
chore: update CI workflow by removing redundant PNPM installation step and enhance deployment instructions in README
1 parent ef3d5be commit af9603d

File tree

2 files changed

+24
-5
lines changed

2 files changed

+24
-5
lines changed

.github/workflows/ci.yaml

+5-5
Original file line numberDiff line numberDiff line change
@@ -53,6 +53,11 @@ jobs:
5353
- name: Checkout repository
5454
uses: actions/checkout@v3
5555

56+
- name: Install pnpm
57+
uses: pnpm/action-setup@v2
58+
with:
59+
version: 8
60+
5661
- name: Setup Node.js and cache PNPM dependencies
5762
uses: actions/setup-node@v3
5863
with:
@@ -61,11 +66,6 @@ jobs:
6166
scope: "@programmer_network"
6267
cache: pnpm
6368

64-
- name: Install PNPM
65-
uses: pnpm/action-setup@v2
66-
with:
67-
version: 8
68-
6969
- name: Install Dependencies
7070
run: pnpm install
7171
env:

README.md

+19
Original file line numberDiff line numberDiff line change
@@ -315,4 +315,23 @@ Then update your `package.json` scripts:
315315
"scripts": {
316316
"dev:with-local-ajv": "cross-env USE_LOCAL_AJV=true vite"
317317
}
318+
```
319+
320+
Here's a slightly improved version of your deployment instructions, which clarifies the steps and ensures consistency:
321+
322+
---
323+
324+
## Deployment Instructions
325+
326+
To deploy a new version and publish it to npm, follow these steps:
327+
328+
1. Check the current version in `package.json`.
329+
330+
2. Create a new tag that is one version higher than the version specified in `package.json`, following semantic versioning (e.g., `v1.0.1``v1.0.2`).
331+
332+
3. Push the new tag to the remote Git repository.
333+
334+
```bash
335+
git tag vX.X.X
336+
git push origin vX.X.X
318337
```

0 commit comments

Comments
 (0)