Repository navigation
build: generate an ase swatch file on release - #2
Merged
Merged
Conversation
cursor
Bot
force-pushed
the
ase-swatches
branch
2 times, most recently
from
November 11, 2026 21:33
64ea68b to
0788cba
Compare
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.
cursor
Bot
force-pushed
the
ase-swatches
branch
from
November 12, 2026 13:19
0788cba to
fd637c7
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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.