carson 4.3.3 → 4.3.4
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.
- checksums.yaml +4 -4
- data/RELEASE.md +11 -1
- data/VERSION +1 -1
- metadata +1 -1
checksums.yaml
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
---
|
|
2
2
|
SHA256:
|
|
3
|
-
metadata.gz:
|
|
4
|
-
data.tar.gz:
|
|
3
|
+
metadata.gz: 9a188fed6453dc86ca1da87766cf9e594e3eb8a92fccdc091fa6d9daeca57fcf
|
|
4
|
+
data.tar.gz: a817693746cbd73a690c16de3f75e5e6b0ec6312d42a94f1cec0b02ed418ff89
|
|
5
5
|
SHA512:
|
|
6
|
-
metadata.gz:
|
|
7
|
-
data.tar.gz:
|
|
6
|
+
metadata.gz: cd7ce61eadfac8406738d2eb8bfaa15c18ec64fca01912e2e01866e91c362bec82b62708863fd6cffd8f7f1d7e3d55efd8240f911a141f29ec792af8e1d5341b
|
|
7
|
+
data.tar.gz: 83c23c3de5d30229a718c393201a9f0af70c8a3336266baacc0ac891b771fd8f27a6d924baa84a098363e2cb121cbebdfed24cbfac758eb10236e265b959e1d9
|
data/RELEASE.md
CHANGED
|
@@ -15,7 +15,7 @@ Release-note scope rule:
|
|
|
15
15
|
|
|
16
16
|
Audit was a remote-centred pre-commit gate — it blocked commits based on delivery-time concerns (PR checks, CI baseline) that don't belong at commit time. In local-centred mode it was purely dead weight. Rather than relocate it to bureau, we verified that none of its unique checks had proven value at any gate, and dissolved the whole thing. Scars, not speculation.
|
|
17
17
|
|
|
18
|
-
## 4.3.
|
|
18
|
+
## 4.3.4
|
|
19
19
|
|
|
20
20
|
### Fixed
|
|
21
21
|
|
|
@@ -25,6 +25,16 @@ Audit was a remote-centred pre-commit gate — it blocked commits based on deliv
|
|
|
25
25
|
|
|
26
26
|
Local-centred mode means local main is the source of truth. Fetching from GitHub on every checkin was a remote-centred assumption baked into the command. The two sequential network round-trips accounted for 90% of the wall time.
|
|
27
27
|
|
|
28
|
+
## 4.3.3
|
|
29
|
+
|
|
30
|
+
### New
|
|
31
|
+
|
|
32
|
+
- **Empty parcel guard.** `carson deliver` refuses to deliver a branch with zero commits ahead of main. Previously, delivering an empty branch was a silent no-op — `git merge --ff-only` succeeded, Carson reported "merged into main", the courier synced to remote, and the workbench was destroyed. All edits that existed only in the working directory were lost. Now `Warehouse#prepare!` stamps each parcel with its origin (via `git merge-base`) and `Parcel#empty?` compares head to origin. An empty parcel blocks with: "Nothing to deliver — no commits ahead of main."
|
|
33
|
+
|
|
34
|
+
### Why
|
|
35
|
+
|
|
36
|
+
An agent edited four files in a worktree, ran `carson deliver` without committing, and lost all work. Carson merged a branch with zero commits ahead of main — a valid fast-forward, technically a no-op. The edits existed only in the working directory and were destroyed on workbench cleanup. The agent then wrote a confident delivery summary describing changes that did not exist on main.
|
|
37
|
+
|
|
28
38
|
## 4.3.2
|
|
29
39
|
|
|
30
40
|
### Fixed
|
data/VERSION
CHANGED
|
@@ -1 +1 @@
|
|
|
1
|
-
4.3.
|
|
1
|
+
4.3.4
|