pubm 0.2.1 → 0.2.3

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/README.md CHANGED
@@ -70,6 +70,7 @@ pubm patch --preview
70
70
  | Flag | Purpose |
71
71
  |------|---------|
72
72
  | `-p, --preview` | Dry‑run: show tasks, no side‑effects |
73
+ | `--preflight` | Simulate CI publish locally (token‑based auth + dry‑run) |
73
74
  | `--registry <list>` | Comma‑separated targets, e.g. `npm,jsr,https://registry.example.com` |
74
75
  | `--branch <name>` / `--any-branch` | Release branch guard control |
75
76
  | `--no-pre-check` / `--no-condition-check` | Skip guard stages |
@@ -84,9 +85,25 @@ pubm patch --preview
84
85
  2. **Required condition checks** – registry ping, login & permission, engine versions.
85
86
  3. **Test & build** *(optional)*
86
87
  4. **Version bump & tag** (SemVer)
87
- 5. **Concurrent publish** – npm (OTP/provenance), jsr, plugins.
88
+ 5. **Concurrent publish** – npm (OTP/provenance), jsr, crates.io, plugins.
88
89
  6. **Git push & GitHub release draft**
89
90
 
91
+ ### Preflight Mode
92
+
93
+ Validate that your CI publish pipeline will work **before** pushing:
94
+
95
+ ```bash
96
+ pubm --preflight
97
+ ```
98
+
99
+ Preflight collects registry tokens interactively, then runs the entire pipeline with `promptEnabled=false` (simulating CI). Publish steps are replaced with dry‑run. If a token is invalid, it re‑prompts and retries.
100
+
101
+ After validation, pubm offers to sync tokens to GitHub Secrets via `gh secret set`. You can also sync manually:
102
+
103
+ ```bash
104
+ pubm secrets sync
105
+ ```
106
+
90
107
  ---
91
108
 
92
109
  ## FAQ