instabox 0.8.142 → 0.8.144

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/cli/SHA256SUMS CHANGED
@@ -1,6 +1,6 @@
1
- 06a8f51276b3b523c8553f19b1379ace1eaa82ed560f60bc162e41be3cee2707 instabox-darwin-amd64
2
- 016753c1ac6344c26a92eb4b19c32e6a7cdcaf5b1be3fdd7d3b4c0543da1791f instabox-darwin-arm64
3
- 5705d3532e98d9a69a3d9f8aac69a4df25539c96be5e2c13fa0222cf85986ce5 instabox-linux-amd64
4
- bc8fbba71e16c886b374bfaa2daa674a95e1520f82bee75804be44ce92d176c7 instabox-linux-arm64
5
- 2a75399d84bed8ad453c7b76b254e171cfaf0b675eb3839b1629e0624b80802c instabox-windows-amd64.exe
6
- 28ae33778fac49465a535d2407f133fc03ca5af426f76a7381fecb6332408808 instabox-windows-arm64.exe
1
+ 613de542788ca1c11f41a11d8c5a983ca7a5f2ec769e38877d434b593c995815 instabox-darwin-amd64
2
+ f76c271b61415055a2705bede12cacc344fff09de1dd24f85557bf93fc8d4739 instabox-darwin-arm64
3
+ d3b0d16978faf7ced814f556b36a0e1e96c083260b6876d4d8770dd48e101bdc instabox-linux-amd64
4
+ 64eaed9f63dadbafcb5a2b75a79d9395411fa5e7802200b5e2c12b165df4c133 instabox-linux-arm64
5
+ 3fc2394f7bee6750c1c5b82ee9cb909454bb986be6fa250061591f861405ccfe instabox-windows-amd64.exe
6
+ b36f93b446bdf41e113e285e892a705723244f34f3f7353327e2bf9de4d26cb6 instabox-windows-arm64.exe
Binary file
Binary file
Binary file
Binary file
Binary file
Binary file
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "instabox",
3
- "version": "0.8.142",
3
+ "version": "0.8.144",
4
4
  "description": "A cloud box for your coding agent, the instabox CLI and its agent skills in one command: npx instabox@latest",
5
5
  "type": "module",
6
6
  "bin": {
@@ -166,7 +166,7 @@ When the user asks to run their CI on instabox, set up `runs-on: instabox-medium
166
166
 
167
167
  1. Get OWNER/REPO: `gh repo view --json owner,name,visibility --jq '.owner.login+"/"+.name+" "+.visibility'`. If it's public, tell the user that pull requests from forks will run on their workspace too, on their plan, and that GitHub's **Require approval for all external contributors** (the repository's **Settings** > **Actions** > **General**) makes each one wait for their approval. Then run `instabox ci` (with `--org ORG` for a workspace): if it says GitHub Actions jobs aren't open on this account yet, use the CLI way below instead.
168
168
  2. Pick the workspace that runs and pays for the jobs: when `instabox workspace ls` lists more than one, ask the user which. Send them the App link with its ID, https://dashboard.instabox.sh/auth/github-app/install?org=ORG_ID (without `?org=` the page asks which workspace when they are in more than one). Linking takes an owner or admin of that workspace. The link has them confirm their GitHub account, then lists the GitHub accounts with the App: ask them to click **Link** next to OWNER (when OWNER is not listed, **Install on another GitHub account**, install it on OWNER and give it access to REPO), and wait until they say it's done. The page it ends on names the workspace it linked. If it says "your personal workspace" and they meant another, see the end of this section. You can't do this step for them.
169
- 3. Change `runs-on:` of the jobs to move to `instabox-medium` (4 vCPU / 8 GiB), or `instabox-small` (2 / 4) or `instabox-large` (8 / 16) where the plan has them (the free plan runs `instabox-medium` only; any other `instabox` label, `instabox` alone included, is refused). Leave the steps alone; the jobs' secrets stay GitHub Actions secrets, as the box gets none of the user's instabox secrets.
169
+ 3. Change `runs-on:` of the jobs to move to `instabox-medium` (4 vCPU / 8 GiB), or `instabox-small` (2 / 4), `instabox-large` (8 / 16), `instabox-xlarge` (16 / 32) or `instabox-2xlarge` (32 / 64) where the plan has them (the free plan runs `instabox-medium` only, `instabox-xlarge` needs Builder or Team and `instabox-2xlarge` Team; any other `instabox` label, `instabox` alone included, is refused). Leave the steps alone; the jobs' secrets stay GitHub Actions secrets, as the box gets none of the user's instabox secrets.
170
170
  4. Show the user the diff and push only with their OK.
171
171
  5. Check the first run: `gh run watch`, and `instabox ci` (with `--org ORG` for a workspace) shows each job's state and why it waits or was refused. When nothing is linked, `instabox ci` says so and prints the App install link to send. A job that stays queued on GitHub with nothing in `instabox ci` means the App has no access to REPO; go back to step 2.
172
172