Auto-memory file deletion now rejects every flag except -f or --force, so fewer commands slip through.
What's wrong with this entry?
The memory-context Bash allowlist for deleting .md files is now deny-by-default on flags instead of blocklisting recursive ones.
- previously it rejected
--recursiveand-r*and allowed other flags; it now rejects every flag except-fand--force --end-of-options is supported- each path is validated by a shared helper that requires a
.mdsuffix under the memory directory - the denial message spells out the rule, and the pre-scan regex for delete-like commands moved to a shared compiled pattern
rm (no flags except -f)
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.239
Clearer rules for force-publishing an artifact
Both mention force