mirror of
https://github.com/garrytan/gstack.git
synced 2026-10-31 14:06:50 +01:00
* security: isolate every gstack Bun entry point from the audited checkout's .env and bunfig.toml Bun auto-loads .env, .env.local and .env.<NODE_ENV> from its cwd and runs a cwd bunfig.toml preload before the program starts. gstack runs inside the repo it audits, so a committed .env could steer state roots, the claude binary or spend caps, and a bunfig preload ran arbitrary code in every bin and hook. Every bun shebang, shell and skill caller, TypeScript spawn and compiled build now disables both (--no-env-file --config=/dev/null, bunIsolationArgs(), --no-compile-autoload-dotenv/bunfig), with a ratchet and hostile-fixture regressions. Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com> * test: name the directly executed scripts in the isolation ratchet Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com> * test: follow the isolation flags in touchfiles, copy lists, recipe assertions and the harness pin Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com> * fix: keep browse/src/bun-child-config.ts unchanged so the native cookie qualification still binds Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com> * fix(windows): the empty bunfig outlives its process so the timeline hook's detached repair child can read it Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com> * v1.91.159.0 security: gstack's Bun entry points ignore the audited repo's .env and bunfig.toml (S1) Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com> * test: plan-mode render pattern accepts the isolation flags Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com> --------- Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
32 lines
1.2 KiB
TypeScript
32 lines
1.2 KiB
TypeScript
#!/usr/bin/env -S bun --no-env-file --config=/dev/null
|
|
// detect-bump — crude heuristic for picking a bump level from a VERSION pair.
|
|
// Used by CI's version-gate job to re-run the util with the "same" level that
|
|
// /ship used, without needing persisted bump-intent.
|
|
//
|
|
// Input: two VERSION strings via argv: current (base) and target (branch).
|
|
// Output: a single word: major|minor|patch|micro
|
|
//
|
|
// Heuristic: compare slot-by-slot. The first slot that differs IS the level.
|
|
// If nothing differs (shouldn't happen when called by CI gate — the whole point
|
|
// is the branch bumped VERSION), default to "patch".
|
|
|
|
function detect(a: string, b: string): string {
|
|
const pa = a.trim().match(/^(\d+)\.(\d+)\.(\d+)\.(\d+)$/);
|
|
const pb = b.trim().match(/^(\d+)\.(\d+)\.(\d+)\.(\d+)$/);
|
|
if (!pa || !pb) return "patch";
|
|
const [, a1, a2, a3, a4] = pa;
|
|
const [, b1, b2, b3, b4] = pb;
|
|
if (a1 !== b1) return "major";
|
|
if (a2 !== b2) return "minor";
|
|
if (a3 !== b3) return "patch";
|
|
if (a4 !== b4) return "micro";
|
|
return "patch";
|
|
}
|
|
|
|
const [, , base, target] = process.argv;
|
|
if (!base || !target) {
|
|
console.error("Usage: detect-bump <base-version> <branch-version>");
|
|
process.exit(2);
|
|
}
|
|
console.log(detect(base, target));
|