dcs-sirgit 0.1.0 → 0.1.2

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 (3) hide show
  1. package/README.md +2 -2
  2. package/bin/sirgit +0 -0
  3. package/package.json +1 -1
package/README.md CHANGED
@@ -107,13 +107,13 @@ E2E starts its own server on :8549 automatically (`reuseExistingServer` honored;
107
107
 
108
108
  ### Release
109
109
 
110
- Bump `version` in **both** `server/Cargo.toml` and `package.json` (prepare-bin warns on mismatch), commit, then:
110
+ Bump `version` in `package.json` (the single source — `scripts/prepare-bin.mjs` syncs `server/Cargo.toml` to it at build time), commit, then:
111
111
 
112
112
  ```bash
113
113
  git tag v0.2.0 && git push origin v0.2.0
114
114
  ```
115
115
 
116
- The `release` workflow builds the release binary (web/dist embedded), runs the full suite, publishes to npm, and attaches the binary + tarball to a GitHub Release. One-time setup: add the `NPM_TOKEN` repo secret (an npm *Automation* token, which skips 2FA in CI).
116
+ The `release` workflow (macOS arm64) does the rest: web build → cargo test → `pnpm pack` → `npm publish` → GitHub Release with `bin/sirgit` + the tarball attached. One-time setup: the `NPM_TOKEN` repo secret (an npm *Automation* token, which skips 2FA in CI). *(A release-please bot flow was tried and removed — this org's policy forbids workflow-created PRs.)*
117
117
 
118
118
  ### Performance numbers (M1 acceptance)
119
119
 
package/bin/sirgit CHANGED
Binary file
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "dcs-sirgit",
3
- "version": "0.1.0",
3
+ "version": "0.1.2",
4
4
  "description": "A fast, visual git client — built as a thank-you to ungit. One Rust binary, zero runtime dependencies.",
5
5
  "keywords": [
6
6
  "git",