The pinning rule in prompts/REPO_POLICIES.md now opens with its scope: what we download and install ourselves in scripts and Dockerfiles. Distribution packages come right after, as outside the rule rather than as an exception at the end. Updating and upgrading them is allowed, with apt update && apt upgrade -y && apt install -y build-essential as the example.
Things the diff does not make obvious:
The scope list gains "release archives fetched with curl or wget", and "Python packages" becomes "Python packages from PyPI". The curl | bash paragraph already required this.
The sentence on a package source a Dockerfile adds itself moved up next to the distribution paragraph. It now says those packages are pinned like any other download.
The old example list (apt-get update, apt-get install, apk update, apk add) is replaced by the single example command. The general sentence still covers apk.
Both checklists restate the rule the same way. last_modified is bumped on all three files.
The pinning list, curl | bash ban, untrusted sources, and Node and yarn guidance are otherwise unchanged.
Model: opus-5-5
Closes https://git.eeqj.de/sneak/prompts/issues/154.
The pinning rule in `prompts/REPO_POLICIES.md` now opens with its scope: what we download and install ourselves in scripts and Dockerfiles. Distribution packages come right after, as outside the rule rather than as an exception at the end. Updating and upgrading them is allowed, with `apt update && apt upgrade -y && apt install -y build-essential` as the example.
Things the diff does not make obvious:
- The scope list gains "release archives fetched with `curl` or `wget`", and "Python packages" becomes "Python packages from PyPI". The `curl | bash` paragraph already required this.
- The sentence on a package source a `Dockerfile` adds itself moved up next to the distribution paragraph. It now says those packages are pinned like any other download.
- The old example list (`apt-get update`, `apt-get install`, `apk update`, `apk add`) is replaced by the single example command. The general sentence still covers `apk`.
- Both checklists restate the rule the same way. `last_modified` is bumped on all three files.
The pinning list, `curl | bash` ban, untrusted sources, and Node and yarn guidance are otherwise unchanged.
Model: opus-5-5
The pinning rule now opens with its scope: what we download and install
ourselves in scripts and Dockerfiles. Distribution packages follow right
after as outside the rule, with updating and upgrading allowed. Both
checklists say the same.
Model: opus-5-5
clawbot
self-assigned this 2026-11-06 01:11:57 +01:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Closes #154.
The pinning rule in
prompts/REPO_POLICIES.mdnow opens with its scope: what we download and install ourselves in scripts and Dockerfiles. Distribution packages come right after, as outside the rule rather than as an exception at the end. Updating and upgrading them is allowed, withapt update && apt upgrade -y && apt install -y build-essentialas the example.Things the diff does not make obvious:
curlorwget", and "Python packages" becomes "Python packages from PyPI". Thecurl | bashparagraph already required this.Dockerfileadds itself moved up next to the distribution paragraph. It now says those packages are pinned like any other download.apt-get update,apt-get install,apk update,apk add) is replaced by the single example command. The general sentence still coversapk.last_modifiedis bumped on all three files.The pinning list,
curl | bashban, untrusted sources, and Node and yarn guidance are otherwise unchanged.Model: opus-5-5