Skip to content

build: generate an ase swatch file on release - #2

Merged
andrinoff merged 3 commits into
mainfrom
ase-swatches
Nov 12, 2026
Merged

andrinoff merged 3 commits into
mainfrom
ase-swatches

Conversation

@meowgorithm

@meowgorithm meowgorithm commented Nov 11, 2026 •

Copy link
Copy Markdown
Member

Tagged releases now include charmtone-.ase, an Adobe Swatch Exchange file of the CharmTone palette. scripts/ase.py reads the colors and groups from charmtone.go, so the swatch file stays in step with the palette. The build workflow checks that the file parses and contains every key. After goreleaser publishes a tag, a job on the GitHub Ubuntu runner generates the file and uploads it, because the shared releaser does not install Python. Run task ase to generate the swatch file. Untagged builds are named from git describe.

@cursor
cursor Bot force-pushed the ase-swatches branch 2 times, most recently from 64ea68b to 0788cba Compare November 11, 2026 21:33
Read the palette from charmtone.go and attach a versioned charmtone ase
file to each tagged GitHub release. Groups follow the swatch library, and
colors are normal process swatches. The build workflow checks that the file
parses and includes every key. task ase writes the swatch file.
@andrinoff
andrinoff merged commit a19e457 into main Nov 12, 2026
9 checks passed
@andrinoff
andrinoff deleted the ase-swatches branch November 12, 2026 15:10
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.

2 participants