@ashlr/stack 0.2.2 → 0.3.0
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 +31 -1
- package/dist/index.js +12385 -9104
- package/package.json +2 -2
package/README.md
CHANGED
|
@@ -95,7 +95,7 @@ A cheat sheet for the current source interface:
|
|
|
95
95
|
| `stack projects list|register|remove|where` | Cross-project registry; `projects list --json` prints `ashlr.stack.projects/v1` |
|
|
96
96
|
| `stack ci init` | Inspect unavailable CI health workflow generation; exits nonzero without writing a workflow |
|
|
97
97
|
| `stack completion <bash\|zsh\|fish>` | Emit a shell-completion script |
|
|
98
|
-
| `stack upgrade` | Check npm for a newer
|
|
98
|
+
| `stack upgrade` | Check npm for a newer release; `--apply` upgrades an npm global CLI with rollback |
|
|
99
99
|
| `stack login <provider>` | Refresh credentials for that provider; existing stored credentials are separate from setup staging |
|
|
100
100
|
| `stack sync --platform <name>` | Push through Phantom to a configured Vercel, Railway or Fly target |
|
|
101
101
|
| `stack onboard [--apply] [--undo]` | Detect Codex, Claude Code, Cursor and Gemini CLI and register the Phantom gateway (`ashlr-hub`) in each; plan only without `--apply`, existing config files backed up before writing; `--undo` restores them |
|
|
@@ -128,3 +128,33 @@ Full schema: [stack.ashlr.ai/docs/config](https://stack.ashlr.ai/docs/config).
|
|
|
128
128
|
## License
|
|
129
129
|
|
|
130
130
|
MIT. See the repository [LICENSE](../../LICENSE).
|
|
131
|
+
|
|
132
|
+
### Safe CLI upgrades
|
|
133
|
+
|
|
134
|
+
`stack upgrade` checks for a newer stable release without installing it. For an
|
|
135
|
+
existing npm global installation on macOS or Linux, run `stack upgrade --apply`.
|
|
136
|
+
Use `--apply --dry-run` to preview, or add `--json` for machine-readable output.
|
|
137
|
+
Bun, linked development installs, Windows, and other ecosystem components are
|
|
138
|
+
outside this first upgrade slice; use the manual installation hint for those.
|
|
139
|
+
|
|
140
|
+
The command checks the current package identity and CLI health, installs the exact
|
|
141
|
+
new version into a temporary prefix with lifecycle scripts disabled, and checks
|
|
142
|
+
its version and help output. It then replaces the package directory while keeping
|
|
143
|
+
the existing launcher. If either active health check fails, it restores the original
|
|
144
|
+
directory locally and verifies it, without downloading the previous version.
|
|
145
|
+
Failures exit nonzero, including a successfully rolled back upgrade. Successful
|
|
146
|
+
`--apply --json` reports have status `upgraded`; read-only reports retain the
|
|
147
|
+
existing `ashlr.stack.upgrade/v1` shape.
|
|
148
|
+
|
|
149
|
+
An exclusive lock prevents overlapping Stack upgrades. Do not run another package
|
|
150
|
+
manager against the same installation during an upgrade. Each npm operation has
|
|
151
|
+
a two-minute timeout and each CLI health check has a fifteen-second timeout.
|
|
152
|
+
These checks cover CLI startup, version, and command registration, not remote
|
|
153
|
+
service health. No provider resources or credentials are changed.
|
|
154
|
+
|
|
155
|
+
A process kill or power loss between directory renames requires manual recovery.
|
|
156
|
+
Recovery files live beside the installed package under `.stack-upgrade-*`, with
|
|
157
|
+
the original package in `previous`. Keep those files until the installation is
|
|
158
|
+
verified. If automatic recovery fails, the error identifies the retained directory.
|
|
159
|
+
Only remove a stale `.stack-upgrade-lock` after confirming no upgrade is running
|
|
160
|
+
and restoring/verifying the installation.
|