Repository navigation
v1.0.1
A patch release with three fixes. A failed transcript call in init --transcripts no longer throws away the chats already drafted, and a configuration error stops it at once. init's next-step commands run as printed for any folder name. The Claude Code plugin installs sandtable into the working folder's own project, never a parent's. There are no breaking changes.
Fixed
init --transcripts: a transcript whose call fails after the client's retries no longer throws away the transcripts drafted before it.initwrites what was drafted, names each failed transcript with its error, prints theinit --transcriptscommand that drafts only the transcripts left, and still exits 2. It goes on past an error that concerns one transcript alone (an HTTP status of 400, 413, 429 or 5xx, such as a Bedrock 503 on a long chat). It stops at one that every later call would hit too (401, 403, 404, or no HTTP status, such as missing credentials), names it once and lists the transcripts it didn't send (#402).initandvalidate: the next-step commands they print quote a folder whose name has a space or another character the shell would split or expand, such asnpx sandtable-ai review 'dom three', so they run as printed (#409).- Plugin: the drafting and results skills install
sandtable-aiand its optional packages into the working folder's own npm project. In a folder with nopackage.json, they runnpm init -yfirst, since npm otherwise installs into the nearest project above it, even the engineer's home folder. Afterwards they say whichpackage.jsonthey changed (#401).
What's Changed
Other changes
- fix(init): init --transcripts keeps the chats it drafted when one fails, and names the failed ones by @Uliseis in #406
- fix(init): init's next-step commands quote paths, so they run as printed by @Uliseis in #410
- fix(plugin): the skills install sandtable into the working folder, never into a parent project by @Uliseis in #404
- chore(release): v1.0.1 by @Uliseis in #411
Full Changelog: v1.0.0...v1.0.1