jaypost 0.6.0 → 0.7.0

package/CHANGELOG.md

@@ -1,5 +1,15 @@
 # jaypost
 
+## 0.7.0
+
+### Minor Changes
+
+- 333dedb: One-line install for the standalone binary: `curl -fsSL https://unpkg.com/jaypost/install.sh | sh` picks the binary for your OS and CPU, checks it against `SHA256SUMS`, puts it in `~/.local/bin` and runs `jaypost init`. The website serves the same script at `https://bithyte.github.io/jaypost/install.sh`.
+
+### Patch Changes
+
+- b299efa: Fixed the standalone binary failing every Telegram call, so `jaypost init` rejected any bot token. Also silenced the `url.parse()` deprecation warning (DEP0169) it printed on the first Telegram request.
+
 ## 0.6.0
 
 ### Minor Changes

package/README.md

@@ -429,7 +429,7 @@ Attachments need a service at least as new as this release; an older one ignores
 
 ### OpenAPI spec
 
-The API is described in OpenAPI 3.1: [`docs/openapi.yaml`](docs/openapi.yaml) (port 8787, Telegram's text limit), `GET /openapi.yaml` on a running service, or `jaypost openapi [FILE]`. The last two use the install's port and its provider's text limit. Regenerate the docs copy with `npm run openapi`.
+The API is described in OpenAPI 3.1: [`docs/openapi.yaml`](docs/openapi.yaml) (port 8787, Telegram's text limit), `GET /openapi.yaml` on a running service, or `jaypost openapi [FILE]`. The last two use the install's port and its provider's text limit. Regenerate the docs copy with `vp run openapi`.
 
 ## Install options
 
@@ -446,21 +446,29 @@ Node 24+ is needed for `npx` and the systemd and launchd targets unless you use
 
 ### Standalone binary
 
-Each GitHub Release has a single-file binary for Linux and macOS, so you can skip Node:
+Each GitHub Release has a single-file binary for Linux and macOS (x64 and arm64), so you can skip Node:
 
 ```
-curl -L https://github.com/bithyte/jaypost/releases/latest/download/jaypost-linux-x64.gz | gunzip > jaypost && chmod +x jaypost && ./jaypost init systemd
+curl -fsSL https://unpkg.com/jaypost/install.sh | sh
 ```
 
-On macOS (Apple silicon):
+The same script is on the website too:
 
 ```
-curl -L https://github.com/bithyte/jaypost/releases/latest/download/jaypost-darwin-arm64.gz | gunzip > jaypost && chmod +x jaypost && ./jaypost init launchd
+curl -fsSL https://bithyte.github.io/jaypost/install.sh | sh
+```
+
+It picks the binary for your OS and CPU, checks it against the release's `SHA256SUMS`, puts it in `~/.local/bin/jaypost` and runs `jaypost init`. Right after a release the binaries can take a few minutes to upload; the script says so if it gets there first.
+
+To do it by hand, download `jaypost-<linux|darwin>-<x64|arm64>.gz` from the [latest release](https://github.com/bithyte/jaypost/releases/latest), then:
+
+```
+gunzip jaypost-linux-x64.gz && mv jaypost-linux-x64 jaypost && chmod +x jaypost && ./jaypost init
 ```
 
 If you downloaded the binary with a browser instead of curl, macOS may block it; run `xattr -d com.apple.quarantine jaypost` first.
 
-`init` copies the binary to `~/.local/bin/jaypost` and runs the service from there. `SHA256SUMS` on the release lists the checksums.
+`init` copies the binary to `~/.local/bin/jaypost` and runs the service from there.
 
 The API token file `~/.config/jaypost/token` is written for every target; the service's own copy goes in the target's `.env` or in `config.json` as listed below. All targets keep their files under `~/.config/jaypost/` (or `$XDG_CONFIG_HOME/jaypost/`). `install.json` there records which target is installed, its port and version. It's what `status`, `reset-owner` and `uninstall` read.
 
@@ -677,10 +685,10 @@ The [question log](#question-log) keeps question text and answers on disk (mode
 
 ## Releasing
 
-When a change matters to users, run `npm run changeset` on its branch, pick patch, minor or major, write a line or two for the changelog, and commit the generated `.changeset/*.md` file with the change. Internal changes (refactors, tests, docs) don't need one.
+When a change matters to users, run `vp run changeset` on its branch, pick patch, minor or major, write a line or two for the changelog, and commit the generated `.changeset/*.md` file with the change. Internal changes (refactors, tests, docs) don't need one.
 
 After a PR with a changeset is merged into `main`, the `publish` workflow opens or updates a `chore: release` PR that bumps the version, writes `CHANGELOG.md` and regenerates `docs/openapi.yaml`. Merging that PR is the release: the workflow runs the checks and tests, publishes to npm, pushes the `vX.Y.Z` tag and creates the GitHub Release. Nothing needs to be run locally.
 
 The same workflow builds the standalone binaries: Linux on Ubuntu, macOS on a macOS runner (ad-hoc codesigned). One last job gzips them and attaches the four `.gz` files and a `SHA256SUMS` to the GitHub Release.
 
-The website in `site/` deploys to `https://bithyte.github.io/jaypost/` after each release, as the last job of `publish`. To deploy by hand (the first time, or for a site-only fix), run the `site` workflow from the Actions tab; it builds whichever ref you pick. For local work, run `npm --prefix site ci` once, then `npm run web:dev`. One-time setup: Settings, Pages, Source: GitHub Actions. To run it from a release tag, add a `v*` tag rule to the `github-pages` environment, which only allows `main` by default.
+The website in `site/` deploys to `https://bithyte.github.io/jaypost/` after each release, as the last job of `publish`. To deploy by hand (the first time, or for a site-only fix), run the `site` workflow from the Actions tab; it builds whichever ref you pick. For local work, `vp install` at the root installs the site too, then run `vp run web:dev`. One-time setup: Settings, Pages, Source: GitHub Actions. To run it from a release tag, add a `v*` tag rule to the `github-pages` environment, which only allows `main` by default.

package/dist/cli.js

@@ -209,7 +209,7 @@ function toEntry(asked, settled, now) {
 //#endregion
 //#region src/config/constants.ts
 /** Package version, read from package.json when the module loads. */
-const VERSION = "0.6.0";
+const VERSION = "0.7.0";
 /** Port used when neither the env nor the config file sets one. */
 const DEFAULT_PORT = 8787;
 /** Appended to config errors so the user knows how to fix them. */

package/install.sh

@@ -0,0 +1,69 @@
+#!/bin/sh
+# Installs the jaypost standalone binary to ~/.local/bin, then runs `jaypost init`.
+# Usage: curl -fsSL https://unpkg.com/jaypost/install.sh | sh
+# JAYPOST_RELEASE_URL overrides where the binaries come from (tests use it).
+set -eu
+
+release_url="${JAYPOST_RELEASE_URL:-https://github.com/bithyte/jaypost/releases/latest/download}"
+bin_dir="$HOME/.local/bin"
+
+fail() {
+  echo "jaypost install: $1" >&2
+  exit 1
+}
+
+case "$(uname -s)" in
+  Linux) os=linux ;;
+  Darwin) os=darwin ;;
+  *) fail "no binary for $(uname -s); use npx jaypost init instead (needs Node 24+)" ;;
+esac
+
+case "$(uname -m)" in
+  x86_64 | amd64) arch=x64 ;;
+  aarch64 | arm64) arch=arm64 ;;
+  *) fail "no binary for $(uname -m); use npx jaypost init instead (needs Node 24+)" ;;
+esac
+
+# A shell running under Rosetta reports x86_64 on Apple silicon; the native binary is better
+if [ "$os" = darwin ] && [ "$arch" = x64 ] && [ "$(sysctl -n hw.optional.arm64 2>/dev/null)" = 1 ]; then
+  arch=arm64
+fi
+
+if command -v sha256sum >/dev/null 2>&1; then
+  hash_file() { sha256sum "$1" | cut -d' ' -f1; }
+elif command -v shasum >/dev/null 2>&1; then
+  hash_file() { shasum -a 256 "$1" | cut -d' ' -f1; }
+else
+  fail "needs sha256sum or shasum to check the download"
+fi
+
+asset="jaypost-$os-$arch.gz"
+temp_dir=$(mktemp -d)
+trap 'rm -rf "$temp_dir" "$bin_dir/jaypost.$$.tmp"' EXIT
+
+echo "Downloading $asset"
+for file in "$asset" SHA256SUMS; do
+  if ! curl -fsSL -o "$temp_dir/$file" "$release_url/$file"; then
+    fail "couldn't download $release_url/$file; if a release just came out, its binaries may still be uploading, so try again in a few minutes"
+  fi
+done
+
+expected=$(awk -v name="$asset" '$2 == name { print $1 }' "$temp_dir/SHA256SUMS")
+actual=$(hash_file "$temp_dir/$asset")
+if [ -z "$expected" ] || [ "$expected" != "$actual" ]; then
+  fail "checksum of $asset doesn't match SHA256SUMS"
+fi
+
+# Unpack next to the target and rename, so a running copy is never half-written
+mkdir -p "$bin_dir"
+gunzip -c "$temp_dir/$asset" >"$bin_dir/jaypost.$$.tmp"
+chmod +x "$bin_dir/jaypost.$$.tmp"
+mv -f "$bin_dir/jaypost.$$.tmp" "$bin_dir/jaypost"
+echo "Installed $bin_dir/jaypost"
+
+# stdin is this script when piped from curl, so init's prompts need the terminal
+if ! (: </dev/tty) 2>/dev/null; then
+  echo "No terminal to set it up from; run $bin_dir/jaypost init"
+  exit 0
+fi
+"$bin_dir/jaypost" init </dev/tty

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "jaypost",
-  "version": "0.6.0",
+  "version": "0.7.0",
   "description": "Local HTTP API that asks you a question on Telegram or Discord with buttons and returns your answer",
   "keywords": [
     "approval",
@@ -20,7 +20,8 @@
   },
   "files": [
     "dist",
-    "CHANGELOG.md"
+    "CHANGELOG.md",
+    "install.sh"
   ],
   "type": "module",
   "exports": {
@@ -36,21 +37,6 @@
     },
     "./package.json": "./package.json"
   },
-  "scripts": {
-    "start": "node src/cli.ts start",
-    "cli": "node src/cli.ts",
-    "test": "vp test",
-    "check": "vp check",
-    "build": "tsc -p tsconfig.build.json && vp pack",
-    "build:exe": "node scripts/build-exe.ts",
-    "openapi": "node scripts/openapi.ts",
-    "changeset": "changeset",
-    "version-packages": "changeset version && npm install --package-lock-only && npm run openapi",
-    "prepack": "npm run build",
-    "web:dev": "npm --prefix site run dev",
-    "web:build": "npm --prefix site run build",
-    "web:preview": "npm --prefix site run preview"
-  },
   "dependencies": {
     "@clack/prompts": "^1.8.1",
     "@discordjs/core": "^2.6.0",
@@ -72,5 +58,19 @@
   },
   "engines": {
     "node": ">=24.2"
+  },
+  "scripts": {
+    "start": "node src/cli.ts start",
+    "cli": "node src/cli.ts",
+    "test": "vp test",
+    "check": "vp check",
+    "build": "tsc -p tsconfig.build.json && vp pack",
+    "build:exe": "node scripts/build-exe.ts",
+    "openapi": "node scripts/openapi.ts",
+    "changeset": "changeset",
+    "version-packages": "changeset version && vp install --lockfile-only && vp run openapi",
+    "web:dev": "vp run --filter jaypost-site dev",
+    "web:build": "vp run --filter jaypost-site build",
+    "web:preview": "vp run --filter jaypost-site preview"
   }
-}
+}