agentleFS
Sign inStart free
bherbruckbherbruck/solidcraft/skills/solidcraft-packaging/SKILL.md

solidcraft-packaging

Skill15k starsChanged 18 days agoApache-2.0View on GitHub

Use when preparing or shipping a SolidCraft release, changing installers or packages (AppImage, MSI, dmg, Flatpak, Snap, WinGet, Nix, FreeBSD, web), release asset names, signing or the Pages deployment.

1 other project uses a version of this.

Adopted by

Steady: 0 new projects took it in the last 4 weeks, none the 4 weeks before.thin data

Week of Sep 13: 0 new projectsWeek of Sep 20: 0 new projectsWeek of Sep 27: 0 new projectsWeek of Oct 4: 0 new projectsWeek of Oct 11: 0 new projectsWeek of Oct 18: 0 new projectsWeek of Oct 25: 0 new projectsWeek of Nov 1: 0 new projects
Sep 2026Oct 2026Nov 2026
New projects taking a version of this file each week, over the 8 weeks our latest run read: only 0 in all, so this is a hint, not a trend.

Most recently taken up by

Who's talking about bherbruck/solidcraft

The biggest 5 of 75 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 75

Talked about on GitHub, YouTube, Bluesky and Hacker News (75 times).

On GitHub · 46

41 more on GitHub

On YouTube · 23

18 more on YouTube

On Bluesky · 5

On Hacker News · 1

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 0 are distinctive, and 5 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 5

    Very specific

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

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

    Update [workspace.package] version in Cargo.toml, then cargo update --workspace --offline.

    line 12
  2. Very specific:

    Run cargo xtask ci and the packaging checks in .github/workflows/packaging-lint.yml.

    line 14
  3. Very specific:

    Verify the draft before publishing: the run succeeded for the intended SHA, every platform and architecture is present, sha256sum --check …

    line 18
  4. Very specific:

    Only when shipping is authorised, publish the verified draft with gh release edit, then confirm its tag resolves to the recorded SHA and …

    line 19
  5. Very specific:

    Never overwrite a published version, tag or asset.

    line 20

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

Packaging and releases

Development pushes are not application releases. Pushing to main or pushing a tag does not start a release. The full procedure is docs/releasing.md; follow it when asked to prepare or ship a release.

Preparing

  1. Choose one version for the whole batch from the actual changes (patch, minor, major, -rc.N). Do not infer it from commit prefixes. Moving to 1.0 is the owner's decision.
  2. Update [workspace.package] version in Cargo.toml, then cargo update --workspace --offline; only our own crates' version = lines in Cargo.lock change.
  3. Fold the pending design-format changes with scripts/fold-format-pending.sh (skills/solidcraft-file-formats/SKILL.md).
  4. Run cargo xtask ci and the packaging checks in .github/workflows/packaging-lint.yml. Land the version commit on main through the normal review flow; never use [skip ci].

Building and publishing

  • Advance the release branch with fast-forwards only (git merge --ff-only); never force-push. .github/workflows/release.yml builds every package and creates a draft GitHub Release.
  • Verify the draft before publishing: the run succeeded for the intended SHA, every platform and architecture is present, sha256sum --check SHA256SUMS.txt passes, and the built CLI runs (--version, an example model).
  • Only when shipping is authorised, publish the verified draft with gh release edit, then confirm its tag resolves to the recorded SHA and the downstream deployment ran. A request to prepare a release is not a request to publish.
  • Never overwrite a published version, tag or asset; use a new version. Do not push the version tag yourself. Packages are unsigned unless docs/releasing.md says otherwise; do not claim they are signed.
  • Nightlies are prereleases built by the same workflow; they never become latest or advance release.

Names that must stay stable

  • Assets are solidcraft-<version>-... and are also attached without the version (solidcraft-windows-x64.msi). The README links and the in-app update check (crates/ui-egui/src/update.rs) pick them by name; renaming one breaks both.
  • The old product name survives only in the shims in docs/compatibility.md. Do not rewrite published assets, checksums, tags or historical notes.
  • Documentation, the browser app and the Flatpak repository publish under project Pages /solidcraft/. Add no old-name Pages aliases.

Where things live

  • packaging/ holds the per-platform scripts (packaging/linux, packaging/windows, packaging/macos, packaging/freebsd, packaging/web); packaging/tests checks them.
  • Nix: flake.nix and docs/nix.md. Building: docs/building.md. Downloads: docs/downloads.md.
  • Build with CARGO_TARGET_DIR=<repo>/target. Windows from Linux: cargo xwin build --release --target x86_64-pc-windows-msvc -p solidcraft.

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.

Check your setup, free