Skip to content

Add ECA.#1

Merged
zarthross merged 8 commits into
mainfrom
eca-update
Jun 2, 2026
Merged

Add ECA.#1
zarthross merged 8 commits into
mainfrom
eca-update

Conversation

@zarthross

Copy link
Copy Markdown
Owner

No description provided.

zarthross added 8 commits June 2, 2026 16:08
- Abandon nix-update approach (cannot handle multi-platform packages)
- Port update scripts from old-update-method branch
- Convert all packages to use lib.importJSON instead of builtins.fromJSON
- Create shared ci/lib/github-release-update.sh for common update logic
- Add multi-platform support for eca-bin (4 platforms with different hashes)
- Switch eca-bin from fetchzip to fetchurl to use published .sha256 files
- Update ci/update.sh to run all package update scripts
- Reduce update script size by 46% (24 lines -> 13 lines for simple packages)

All packages now have:
- sources.json with version, url, and hash
- update.sh script that generates sources.json
- default.nix that reads from sources.json

Benefits:
- Works from any platform (no cross-evaluation issues)
- Multi-platform packages supported (eca-bin has 4 different hashes)
- Flake-friendly (uses pure lib.importJSON)
- Consistent and maintainable
- Easy to add new packages
- Change from macos-latest to ubuntu-latest (update script downloads all platforms)
- Simplify from multi-job multi-platform workflow to single job
- Fix commit to add sources.json instead of default.nix
- Remove unused commitAndForcePush and commitAndPush functions
- CI workflow unchanged (still runs flake check on both Linux and macOS)
- Document sources.json pattern
- Add instructions for adding new packages
- Add instructions for updating packages
- Fix typo: github actions -> GitHub Actions
@zarthross zarthross merged commit 5d3129c into main Jun 2, 2026
2 checks passed
@zarthross zarthross deleted the eca-update branch June 2, 2026 14:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant