agentleFS
eclipse-enclaveeclipse-enclave/enclave/.agents/skills/dependency-updates/SKILL.md

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

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.
  • acquiaSkill

    security-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

    1. ImranR98/Obtainium★ 21ksame name
    2. naomiaro/waveform-playlist★ 1.7ksame name
    3. microsoft/lage★ 817same name
    4. championswimmer/TwoFac★ 130same name
    5. acquia/acquia-skills★ 10same name
    6. acquia/acquia-skills-private★ 1same name
    7. 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.

  • In this repository2 other files it gives its agents.

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
  1. Very specific:

    Ceilings: if a floor may be raised, say so.

    line 57
  2. Very specific:

    Check it against the .sha1 file next to it.

    line 86
  3. Very specific:

    Every Go entry must be approved.

    line 88
  4. Very specific:

    Never pass -review; requesting a review is the maintainer's decision.

    line 91
  5. Very specific:

    If Java or Dash is unavailable, report the license check as not done.

    line 94
  6. Very specific:

    Never edit DEPENDENCIES by hand.

    line 95
  7. Distinctive:

    Keep these in mind when interpreting results or changing the script.

    line 99
  8. Very specific:

    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 …

    line 116

“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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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.sh

It 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.

  1. Security: PROBLEM lines from the Security section and an unsupported Go toolchain.
  2. Inconsistencies: other PROBLEM lines (lockstep groups, actions on several SHAs or SHAs that do not match their tag, uncovered pins, floors above the ceiling, failed lookups).
  3. Routine: update lines for patch and minor versions and digests.
  4. Major: update lines marked MAJOR or major 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_IMAGE codename and the matching -<codename>-slim variant of AGENT_NODE_IMAGE change 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_IMAGE moves to the new major. Summarize the Node release notes that affect the npm-installed agents.
  5. Held back: held back lines and not called vulnerabilities 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.
  6. 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, and internal/app/dockerfile_gen.go against 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.

GroupEdit
Go toolchaingo.mod toolchain; Dockerfile.gateway golang:<version>-alpine<alpine>@<digest>.
Go floorEvery 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 modulesgo get <module>@<version> then go mod tidy; confirm the go directive did not change.
Go lintersscripts/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 imagesThe 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 ActionsEvery uses: of the action, @<sha> # <tag>.
yqDockerfile YQ_VERSION; check that yq_linux_amd64 and yq_linux_arm64 are still release assets.
Fedora CIcontainer: 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 DEPENDENCIES as 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 DEPENDENCIES by 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 -security count; -backports does not. Update the suite lists when a release enters or leaves standard support.
  • Floors (go directive 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 go directive. 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_PINS in 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).

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.