agentleFS
LouLouLibsLouLouLibs/claude-skills/skills/julia-release/SKILL.md

julia-release

Skill1 starsChanged 59 days agoMITView on GitHub

Use when tagging a Julia package version, updating the loulouJL registry, or computing artifact hashes for Artifacts.toml. Triggers on "tag version", "release", "register", "update registry", "artifact hashes".

  • Commits and pushes

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Update Artifacts.toml with computed hashes, commit, push.

    line 65
  2. Distinctive:

    Commit and push the registry:

    line 92

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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

Julia Package Release & Registry Update

Tag a version, compute artifact hashes, and register in loulouJL.

Registry Location

/Users/loulou/Dropbox/projects_code/julia_packages/loulouJL/

Each package has: Versions.toml, Deps.toml, Compat.toml, Package.toml

Quick Reference

StepCommand
Get tree SHAgit rev-parse vX.Y.Z^{tree}
Download release artifactcurl -sL -o file.tar.gz "URL"
SHA256 of tarballshasum -a 256 file.tar.gz
Tree hash of extracted artifactjulia -e 'using Pkg; println(bytes2hex(Pkg.GitTools.tree_hash(".")))'

Release Checklist

1. Version bump (PR required if main is protected)

# Project.toml
version = "X.Y.Z"

2. Tag AFTER all changes are merged

NEVER re-tag a release that has artifacts. Re-tagging causes GitHub to regenerate tarballs with different SHA256 checksums, breaking all artifact downloads.

git tag -a vX.Y.Z -m "vX.Y.Z: description"
git push origin vX.Y.Z

3. Wait for CI + artifact builds

gh run list --limit 5                    # check status
gh run watch <run-id> --exit-status      # wait for completion

4. Compute artifact hashes (if package has Artifacts.toml)

# Download each artifact from the release
curl -sL -o artifact.tar.gz "https://github.com/ORG/REPO/releases/download/vX.Y.Z/artifact-PLATFORM.tar.gz"

# SHA256 (goes in Artifacts.toml [[name.download]] sha256)
shasum -a 256 artifact.tar.gz

# Tree hash (goes in Artifacts.toml [[name]] git-tree-sha1)
mkdir extracted && cd extracted
tar -xzf ../artifact.tar.gz
julia -e 'using Pkg; println(bytes2hex(Pkg.GitTools.tree_hash(".")))'

Update Artifacts.toml with computed hashes, commit, push. Do this BEFORE tagging if possible to avoid the re-tag problem.

5. Update loulouJL registry

TREE=$(git rev-parse vX.Y.Z^{tree})

Versions.toml — always update:

["X.Y.Z"]
git-tree-sha1 = "TREE_SHA"

Deps.toml — update only if dependencies changed. Use version ranges:

["X.Y-0"]
SomeDep = "uuid-here"

Ranges must not overlap. "0.6-0" means 0.6 to end of 0.x.

Compat.toml — update only if compat bounds changed:

["0"]
julia = "1.6-*"

Commit and push the registry:

cd /Users/loulou/Dropbox/projects_code/julia_packages/loulouJL
git add LETTER/PackageName/
git commit -m "Register PackageName vX.Y.Z"
git push

6. Verify

using Pkg
Pkg.Registry.update()
Pkg.add("PackageName")  # or Pkg.update("PackageName")

Artifacts.toml Format

[[artifact_name]]
arch = "aarch64"          # or "x86_64"
git-tree-sha1 = "HASH"
os = "macos"              # or "linux"
lazy = true

    [[artifact_name.download]]
    url = "https://github.com/ORG/REPO/releases/download/vX.Y.Z/file.tar.gz"
    sha256 = "HASH"

Common Mistakes

MistakeConsequencePrevention
Re-tag a release with artifactsSHA256 changes, downloads breakTag once, after all changes merged
Tag before artifact hashes committedNeed re-tag (see above)Compute hashes first, commit, then tag
Overlapping Deps.toml rangesRegistry resolution errors"0.5-0.5" then "0.6-0", never "0.5-0" overlapping "0.6-0"
Forget Pkg.Registry.update()Old version installedAlways update registry before testing
Forget Libdl/stdlib in Deps.tomlPackage fails to loadStdlibs with UUIDs still need Deps.toml entries

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.