dependency-updates
Skill80 starsChanged 17 days agoMITView on GitHub
Use when checking or applying updates to Enclave's pinned dependencies (Go toolchain and modules, Go linters, container images, GitHub Actions) or the LTS version floors, e.g. when asked what needs updating, to refresh pins, or to apply an update group.
7 other projects use a version of this.
Adopted by
Most recently taken up by
- naomiaro/waveform-playlisttheir own version, first seen Nov 16, 2026
- microsoft/lagetheir own version, first seen Nov 1, 2026
- ImranR98/Obtainiumtheir own version, first seen Oct 17, 2026
- acquia/acquia-skillstheir own version, first seen Oct 9, 2026
- championswimmer/TwoFactheir own version, first seen Oct 9, 2026
- linchpin/skillstheir own version, first seen Oct 2, 2026
Used with
Projects with it also use security-updates.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
acquiaSkillsecurity-updates
Use when user asks about fixing security vulnerabilities, composer audit failures, vulnerable Drupal packages, or CVE advisories in a Drupal codebase.
Also in 3 projects that use this
Other versions7 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 7
- ImranR98/Obtainium★ 21ksame name
- naomiaro/waveform-playlist★ 1.7ksame name
- microsoft/lage★ 817same name
- championswimmer/TwoFac★ 130same name
- acquia/acquia-skills★ 10same name
- acquia/acquia-skills-private★ 1same name
- linchpin/skills★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
The file
We split this skill into the rules it gives an agent
8 rules. 0 are common, 1 is distinctive, and 7 are very specific to this project.
0
Common
Most of the 6 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
7
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 57
Ceilings: if a floor may be raised, say so.
- Very specific: line 86
Check it against the .sha1 file next to it.
- Very specific: line 88
Every Go entry must be approved.
- Very specific: line 91
Never pass -review; requesting a review is the maintainer's decision.
- Very specific: line 94
If Java or Dash is unavailable, report the license check as not done.
- Very specific: line 95
Never edit DEPENDENCIES by hand.
- Distinctive: line 99
Keep these in mind when interpreting results or changing the script.
- Very specific: line 116
New pins: when you add a pinned version anywhere, add its location to KNOWN_PINS in the script and a check for it, or the uncovered-pin …
“Common” is measured: kept by at least 6 in 10 of the 6 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Dependency Updates
scripts/check-versions.sh gathers every fact deterministically. This skill
turns its output into a plan and, on request, applies one group. Do not
replace the script's lookups with your own; if the script is wrong or
incomplete, fix the script.
1. Run the check
make check-versions # or: scripts/check-versions.shIt reads the network and never modifies files. --offline checks only the
lockstep groups and uncovered pins (also part of make lint). Exit status 1
means at least one PROBLEM line.
2. Report
Turn the output into a report, in this order, one line per item with current → target and the files to touch, for example:
yq v4.54.1 → v4.55.0: Dockerfile (YQ_VERSION)The report is complete when every PROBLEM, update, held back, and
not called line of the output appears in exactly one bucket.
- Security:
PROBLEMlines from the Security section and an unsupported Go toolchain. - Inconsistencies: other
PROBLEMlines (lockstep groups, actions on several SHAs or SHAs that do not match their tag, uncovered pins, floors above the ceiling, failed lookups). - Routine:
updatelines for patch and minor versions and digests. - Major:
updatelines markedMAJORormajor change.- GitHub Actions: read the upstream release notes between the two versions and summarize what affects this repository (runner or Node requirements, removed inputs, changed defaults). Check the workflows that use the action.
- A new Debian stable: the
BASE_IMAGEcodename and the matching-<codename>-slimvariant ofAGENT_NODE_IMAGEchange together, because the Node binary is copied into the base image. List the packages that the Dockerfiles and the feature install scripts install that are renamed or missing on the new release. - A new Node LTS:
AGENT_NODE_IMAGEmoves to the new major. Summarize the Node release notes that affect the npm-installed agents.
- Held back:
held backlines andnot calledvulnerabilities with the reason the script gives. If a held-back module has a vulnerability, say that fixing it needs a higher Go floor and that this is the maintainer's decision. - Ceilings: if a floor may be raised, say so; never propose a floor
above the ceiling. For a Docker or buildx ceiling change, check the
Dockerfile instructions in
Dockerfile,Dockerfile.gateway, andinternal/app/dockerfile_gen.goagainst it.
3. Apply (only when asked)
One group per change, on a branch. Use the targets, SHAs, and digests from
the script output. Then rerun the script until the group reports ok, and
run make build, make test, and make lint. Do not commit or push unless
asked.
| Group | Edit |
| Go toolchain | go.mod toolchain; Dockerfile.gateway golang:<version>-alpine<alpine>@<digest>. |
| Go floor | Every location the script lists for "Go floor", including the golang-<minor>-go alternative and /usr/lib/go-<minor>/bin fallback in debian/. Only after the ceiling allows it. |
| Go modules | go get <module>@<version> then go mod tidy; confirm the go directive did not change. |
| Go linters | scripts/install-go-linters.sh, and the same versions in the enclave-dev feature of eclipse-enclave/enclave-extensions (separate PR). New gosec or golangci-lint findings must be fixed or justified with #nosec/nolint and a reason; never weaken the rule set. |
| Container images | The ARG/FROM lines in Dockerfile and Dockerfile.gateway. Alpine also: internal/model/types.go AlpineImage and runtime-assets/microvm/alpine/build-bundle.sh, same digest everywhere; check that the packages installed by the gateway and the QEMU bundle exist on the new branch. |
| GitHub Actions | Every uses: of the action, @<sha> # <tag>. |
| yq | Dockerfile YQ_VERSION; check that yq_linux_amd64 and yq_linux_arm64 are still release assets. |
| Fedora CI | container: in .github/workflows/reusable-rpm-build.yml. |
License check (Go modules)
A changed go.sum must pass Eclipse Dash before the update is done. Run it
on go.sum as the DEPENDENCIES header describes. Dash needs Java 11+ and
the Dash version named there; the jar is at
https://repo.eclipse.org/content/repositories/dash-licenses-releases/org/eclipse/dash/org.eclipse.dash.licenses/<version>/org.eclipse.dash.licenses-<version>.jar.
Check it against the .sha1 file next to it.
- Every Go entry must be
approved. If a new version is not, go back to the newest approved version of that module. Report the newer version as held back pending IP review. - Never pass
-review; requesting a review is the maintainer's decision. - Then regenerate
DEPENDENCIESas its header describes, including the website section and the date. - If Java or Dash is unavailable, report the license check as not done.
Never edit
DEPENDENCIESby hand.
Rules the script encodes
Keep these in mind when interpreting results or changing the script.
- Support set: Debian stable and every Ubuntu LTS release in standard
support (
DEBIAN_SUITES,UBUNTU_SUITES). Release,-updates, and-securitycount;-backportsdoes not. Update the suite lists when a release enters or leaves standard support. - Floors (
godirective and packaging Go version, git, Dockerfile features) may not exceed the ceiling: the lowest version the support set ships. An upstream EOL is not a reason to raise one. - Go toolchain is the latest patch of the oldest supported Go minor:
the release the go command switches to when it builds Go linters that need
a newer Go. A newer project minor breaks
make lint, because analysis tools built with an older Go cannot load a newer standard library. - Go modules may not raise the
godirective. Go linters may not require a Go newer than the toolchain. - Lockstep groups move together. One SHA per action, and it must be the commit of the tag in the comment.
- New pins: when you add a pinned version anywhere, add its location to
KNOWN_PINSin the script and a check for it, or the uncovered-pin check fails.
Not checked
- Deferred: the website (
website/,.github/workflows/website-*.yml). - Deliberately unpinned, installed at their latest version on every build; never pin or bump them: claude and uv (curl installers); codex, pi, opencode and the node-dev global packages (npm); glab and nvm (latest-release lookup); gh and the Debian packages in the images (distribution repositories).
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

