You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
a read-only config is refused by name, never replaced
A config the user made read-only is no longer replaced by a write: the run names the file, writes nothing and exits 1.
Fixed
A config made read-only is refused by name, never replaced. On POSIX a rename replaces a read-only file, so configure.mjs, install.mjs --reset and the config and ranking writers replaced a file the user had protected, without a word. Each writer now checks the target first: a file with no write bit is refused with read-only; nothing was written, its bytes and mode stay as they were, and the run exits 1. The migration's <legacy>.bak path is checked before anything is written, and a backup made read-only after that check is refused before its rename. — test: scripts/lib/configure-readonly.test.mjs
Changed
The plugin icon sits at the plugin root: .claude-plugin/plugin.json names ./icon.png (it named ./.claude-plugin/icon.png in 1.8.12). The manifest folder holds the manifest alone.
Exit code, from 1.8.12:configure.mjs exits 1 when a legacy file this run did not read cannot be moved aside, where it exited 0 before, and on every failure of the seeded legacy file's move. A script that runs configure.mjs may see a new non-zero exit.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
a read-only config is refused by name, never replaced
A config the user made read-only is no longer replaced by a write: the run names the file, writes nothing and exits 1.
Fixed
configure.mjs,install.mjs --resetand the config and ranking writers replaced a file the user had protected, without a word. Each writer now checks the target first: a file with no write bit is refused withread-only; nothing was written, its bytes and mode stay as they were, and the run exits 1. The migration's<legacy>.bakpath is checked before anything is written, and a backup made read-only after that check is refused before its rename. — test:scripts/lib/configure-readonly.test.mjsChanged
.claude-plugin/plugin.jsonnames./icon.png(it named./.claude-plugin/icon.pngin 1.8.12). The manifest folder holds the manifest alone.configure.mjsexits 1 when a legacy file this run did not read cannot be moved aside, where it exited 0 before, and on every failure of the seeded legacy file's move. A script that runsconfigure.mjsmay see a new non-zero exit.Release page · CoalTipple
All reactions