mirror of
https://github.com/affaan-m/ECC.git
synced 2026-10-14 20:25:26 +02:00
Affaan MustafaandGitHub
0348d7b6d7
pi/core and the bundled blueprint skill now refer to the project as ECC only; the generated README no longer expands the name. Profile contents, package name and paths are unchanged (123 skills, 24 commands). The release workflows poll npm for up to five minutes after publish before verifying the artifact. In 2.2.2 the check gave up after about 30 seconds while npm was still processing, failing the run before latest was promoted and the GitHub Release was created. Version metadata synced to 2.2.3 with CHANGELOG, translated release headings and release notes; skill-triggers registryDigest updated for the blueprint text.
1.1 KiB
1.1 KiB
ECC 2.2.3
ECC 2.2.3 is a naming and release-reliability update. The project is called ECC
everywhere it ships, starting with the pi/core profile, and the release
workflow now waits long enough for npm to serve a freshly published version.
Naming
pi/coreno longer expands the project name: its README and the bundledblueprintskill refer to ECC only. The profile contents are otherwise unchanged: 123 curated skills and 24 prompt commands, 35,006 characters of skill description text.- Downstream packagers need no changes. The package is still
ecc-pi-core, the directory is stillpi/core/, and existing install paths keep working.
Release workflow
- After
npm publish, the release workflow polls the registry for up to five minutes before verifying the published artifact. In 2.2.2 it gave up after about 30 seconds while npm was still processing the upload, so the run failed before promotinglatestand creating the GitHub Release, and had to be re-run.
Downstream consumption is unchanged: poll /releases, download
archive/refs/tags/vX.Y.Z.tar.gz, pin its sha256, copy pi/core/, and load it
offline.