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
Copy file name to clipboardExpand all lines: README.md
-13Lines changed: 0 additions & 13 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -292,19 +292,6 @@ npm test # or: pnpm test
292
292
293
293
Both `npm` and `pnpm` are exercised in CI across Node 20 and 22 (see `.github/workflows/ci.yml`).
294
294
295
-
### Release flow
296
-
297
-
1. Bump the version: `npm version patch` (or `minor` / `major`).
298
-
2. Push the tag: `git push --follow-tags`.
299
-
3. Either:
300
-
- Create a GitHub release (the `npm-publish.yml` workflow will publish on the `release: published` event), or
301
-
- Trigger the workflow manually via the Actions tab (`workflow_dispatch`).
302
-
4. Verify both managers can install it:
303
-
```bash
304
-
npm install exprify
305
-
pnpm add exprify
306
-
```
307
-
308
295
### Lockfiles
309
296
310
297
`package-lock.json` (npm) and `pnpm-lock.yaml` (pnpm) are both committed. Neither is shipped in the published tarball (see `.npmignore`); npm/pnpm consumers generate their own lockfiles when installing.
0 commit comments