instabox 0.8.141 → 0.8.143

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
- 9388b40e63d6467b3709ea19c5cde1526ea43792671653ee17dff2dd4329774a instabox-darwin-amd64
2
- 453c13a7dea307651cff408cfa47a349336916508f33a232e478f69712ee2b80 instabox-darwin-arm64
3
- db4a6f0e9c94b5d62cb93f0cfa268c5a375dc1372e456636ef750f847d824502 instabox-linux-amd64
4
- 40d9b6c7002f51c5e817b322a711a1e57cd2380b83875aa261a0803d57a5db9e instabox-linux-arm64
5
- 3f90e6e71dbce9fdbe9e4d781c8e8fae77e1d574fd8347275a00da61959ea0da instabox-windows-amd64.exe
6
- bbd41bb7470313a5b7aca27e90893153463d31da215f3e01018a5dbd744bd160 instabox-windows-arm64.exe
1
+ f9c30ce533e8304466e737bfb89a4dbc829e2f63808e44dd07f0adf7dc0c3029 instabox-darwin-amd64
2
+ 7ccb0855571663360d1c73accf7f7b418fa4b05c776aa7b1c8a49c73f539803e instabox-darwin-arm64
3
+ 9a1ee117a8fe0bbeff5a628e3cb907ec8facdd61617657735c1acc2e61704bc9 instabox-linux-amd64
4
+ 6c770897d5d8269fafb493fef1f9df0dc799801610b3a88398e0c514eb01badf instabox-linux-arm64
5
+ e6960959c8b4acfc28e81e3cdd76d8509f70724462bed993c2566c41ce52c5c3 instabox-windows-amd64.exe
6
+ 51aff1b3dbf5acef7793c6ef8f17c20823a0e14756b4a61c102ae40400e72d04 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.141",
3
+ "version": "0.8.143",
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