vibeview 0.17.0 → 0.17.1

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 (2) hide show
  1. package/README.md +43 -2
  2. package/package.json +1 -1
package/README.md CHANGED
@@ -34,6 +34,43 @@ vibeview dev
34
34
 
35
35
  [Live Development docs →](https://vibeview.io/docs/live-development)
36
36
 
37
+ ## Cloud Builds (beta)
38
+
39
+ Build your React Native app on VibeView's build fleet — no Mac, no CI
40
+ pipeline, no local toolchain:
41
+
42
+ ```bash
43
+ vibeview build --cloud # simulator/emulator build
44
+ vibeview build --cloud --production # signed release build (.ipa / .aab)
45
+ ```
46
+
47
+ A regular cloud build lands in your app's Build History, ready to run on a
48
+ cloud device. Add `--production` for a **signed release build** on iOS,
49
+ tvOS, Android, or Android TV, using signing credentials you store once:
50
+
51
+ ```bash
52
+ # Apple: your distribution certificate + provisioning profile
53
+ vibeview credentials add --platform ios --file cert.p12 --profile app.mobileprovision
54
+
55
+ # Android: upload a keystore — or have VibeView generate one (no Java needed)
56
+ vibeview credentials generate --platform android --name release
57
+ ```
58
+
59
+ Credentials are stored encrypted and never readable back. Build-time
60
+ secrets work the same way:
61
+
62
+ ```bash
63
+ vibeview env set NPM_TOKEN "..." # secret by default, injected into builds
64
+ vibeview webhooks add --url https://ci.example.com/hooks/vibeview
65
+ ```
66
+
67
+ Webhooks POST a signed payload to your endpoint whenever a build finishes.
68
+ Manage running builds with `vibeview builds list | logs | download | cancel`.
69
+
70
+ [Cloud Builds docs →](https://vibeview.io/docs/cloud-builds) ·
71
+ [App Signing →](https://vibeview.io/docs/app-signing) ·
72
+ [Build Webhooks →](https://vibeview.io/docs/build-webhooks)
73
+
37
74
  ## Let your AI agent drive the device
38
75
 
39
76
  The same session can be driven by a coding agent, so it can verify its own
@@ -88,9 +125,13 @@ Output formats: `human`, `json`, and `junit` for any CI system. The exit code re
88
125
 
89
126
  | Command | Purpose |
90
127
  | --- | --- |
91
- | `vibeview login` | Authenticate via browser |
128
+ | `vibeview login` / `logout` / `whoami` | Authenticate via browser, sign out, show who you are |
92
129
  | `vibeview dev` | Live development on a cloud device |
93
- | `vibeview build` | Build your app and upload it |
130
+ | `vibeview build` | Build your app — locally, or on the build fleet with `--cloud` (add `--production` for a signed release) |
131
+ | `vibeview builds list/logs/download/cancel/delete-artifact` | Manage cloud builds and their artifacts |
132
+ | `vibeview credentials add/generate/list/rm` | App-signing credentials for production builds |
133
+ | `vibeview env list/set/rm/pull` | Build variables and secrets injected into cloud builds |
134
+ | `vibeview webhooks add/list/rm/test` | Notify your systems when builds finish (signed payloads) |
94
135
  | `vibeview dev-status` / `dev-stop` | Check on, or stop, a backgrounded dev session |
95
136
  | `vibeview agent-setup` | Make VibeView discoverable to your coding agent (skill + MCP) |
96
137
  | `vibeview mcp` | Run the MCP server so an agent can drive the device |
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "vibeview",
3
- "version": "0.17.0",
3
+ "version": "0.17.1",
4
4
  "description": "VibeView CLI -- run mobile tests from CI/CD pipelines",
5
5
  "type": "module",
6
6
  "bin": {