Skip to content

v1.1.3

Choose a tag to compare

@github-actions github-actions released this 27 Oct 16:59
· 24 commits to main since this release
a30cece

A patch release with fixes to the Claude Code plugin's two hooks. The plan hook also catches init run through npm exec or npm run. It no longer shows a dry run's plan for a paid run in another folder or region. The install hook covers pnpm and yarn as well as npm. It suggests npm init -y with each of them, and a command that installs into the folder it checked. There are no breaking changes.

Fixed

  • Plugin: the hook that shows a model-backed init's plan now also catches npm exec sandtable-ai -- init, npm run sandtable -- init and npx sandtable-ai -- init, which ran with no dry run and no message before. It compares the environment variables that pick the provider and region too, so a paid run under another AWS_REGION= than its dry run says the plan isn't known, instead of showing the other region's plan (#415).
  • Plugin: the hook that keeps sandtable in the working folder's own project now covers pnpm add, pnpm install <package> and yarn add, which also install into the nearest project above a folder with no package.json. It tells Claude to run npm init -y first with those too, because pnpm init adds a devEngines field that makes npx sandtable-ai refuse to run. It also checks the folder that yarn's --cwd names (#415, #432).
  • Plugin: when the install hook stops an install that runs in another folder, after a cd or with yarn's --cwd, the command it suggests now starts with a cd to that folder. Before, it left the cd out, so the suggestion, run as written, installed into the project above (#432).
  • Plugin: the plan hook no longer shows a dry run's plan for a paid init whose relative paths name other files. It resolves each command's paths from the folder it ran in, following any cd in the command, so cd eng && npx sandtable-ai init --sop sop.md after a dry run of --sop sop.md in the folder above now says the plan isn't known. A folder change it can't follow, such as cd $DIR or a subshell, makes the plan unknown too. A bare AWS_REGION=…; before the command, which reaches init only when the variable is exported already, now matches only a dry run with the same assignment (#427).

What's Changed

Other changes

  • fix(plugin): the hooks cover init after --, the region from the environment, and pnpm and yarn installs by @Uliseis in #426
  • fix(plugin): the plan hook compares paths by the folder each init ran in by @Uliseis in #429
  • fix(plugin): the install hook says npm init -y with pnpm and yarn too by @Uliseis in #434
  • chore(release): v1.1.3 by @Uliseis in #435

Full Changelog: v1.1.2...v1.1.3