deepflow 0.1.41 → 0.1.42
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/bin/install.js +1 -0
- package/package.json +1 -1
- package/src/skills/release/SKILL.md +26 -0
package/bin/install.js
CHANGED
package/package.json
CHANGED
|
@@ -0,0 +1,26 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: release
|
|
3
|
+
description: Commit, bump, push & publish. Use after completing changes that need releasing to npm.
|
|
4
|
+
---
|
|
5
|
+
|
|
6
|
+
# Release
|
|
7
|
+
|
|
8
|
+
Commit current changes with an intelligent message, then run the release script for bump/push/publish.
|
|
9
|
+
|
|
10
|
+
## Steps
|
|
11
|
+
|
|
12
|
+
1. **Check** — Run `git status` and `git diff`. If no changes to commit, skip to step 3 (there may be a version to release).
|
|
13
|
+
2. **Commit** — Stage the changed files (specific files, not `-A`) and commit with a conventional commit message based on the diff. Follow the repo's existing style from `git log --oneline -5`.
|
|
14
|
+
3. **Release** — Run the release script in a single Bash call:
|
|
15
|
+
|
|
16
|
+
```bash
|
|
17
|
+
npm version patch --no-git-tag-version && git add package.json && git commit -m "$(node -p "require('./package.json').version")" && git push && npm publish
|
|
18
|
+
```
|
|
19
|
+
|
|
20
|
+
4. **Report** — Output one line: `✓ published {name}@{version}`
|
|
21
|
+
|
|
22
|
+
## Rules
|
|
23
|
+
|
|
24
|
+
- Only the commit message requires intelligence. Everything else is the script above.
|
|
25
|
+
- If `git diff` is empty and there are no staged/untracked changes, still run step 3 (user may want to bump+publish existing commits).
|
|
26
|
+
- Never modify the release script commands. Run them exactly as written.
|