@shipstatic/ship 2.0.0-beta.14 → 2.0.0-beta.16

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 (13) hide show
  1. package/README.md +9 -1
  2. package/dist/browser.d.ts +13 -1532
  3. package/dist/browser.js +1 -1
  4. package/dist/browser.js.map +1 -1
  5. package/dist/cli.cjs +56 -57
  6. package/dist/cli.cjs.map +1 -1
  7. package/dist/index.cjs +1 -1
  8. package/dist/index.cjs.map +1 -1
  9. package/dist/index.d.cts +13 -1532
  10. package/dist/index.d.ts +13 -1532
  11. package/dist/index.js +1 -1
  12. package/dist/index.js.map +1 -1
  13. package/package.json +8 -6
package/README.md CHANGED
@@ -320,7 +320,15 @@ The **CLI** (`ship`) resolves its token in this order:
320
320
 
321
321
  1. CLI flag: `--token`
322
322
  2. Environment variable: `SHIP_TOKEN`
323
- 3. Config files: `.shiprc` or `package.json` `"ship"` key (run `ship config` to create one)
323
+ 3. Config file: `~/.shiprc` (run `ship config` to create one)
324
+
325
+ `--config <file>` reads any path you name instead of `~/.shiprc`, which is how per-environment
326
+ configs work (`ship --config dev.shiprc ...`). The file is strict JSON; an empty one means "no
327
+ config".
328
+
329
+ **No repository file is ever read.** A `.shiprc` or `package.json` `"ship"` key in your working
330
+ directory is ignored — cloning a repo can never change which account you deploy to, or which
331
+ host your token is sent to.
324
332
 
325
333
  The **SDK** (`new Ship(...)`) resolves its token in this order:
326
334