Skip to content

Pixelbolt v0.8.0

Choose a tag to compare

View all tags
@github-actions github-actions released this 13 Oct 14:47
· 117 commits to main since this release
v0.8.0
9ec9a90
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Early release. This is Pixelbolt's first GitHub release, and its first under this name (it was called PixelForge until 0.8.0). The README describes what it does today.

0.8.0

Renamed from PixelForge to Pixelbolt. The pixelforge command, the pixelforge-* recipe formats and the MCP tool names are unchanged.

The bundle is now pixelbolt.mcpb (checksum pixelbolt.mcpb.sha256), and portable Studio builds are named PixelboltStudio-<version>-<target>. The pixelforge alias stays for at least two releases.

Pixelbolt turns editable JSON recipes into pixel art and sprite animation. pixelbolt.mcpb contains the local Node.js MCP server, its eight tools, schemas and authoring help. The server makes no network requests.

Download pixelbolt.mcpb and open it in Claude Desktop, or use Settings -> Extensions -> install from file. Choose a workspace for recipes and generated artwork, then ask the agent to call pixel_help. The bundle uses the client's Node.js runtime (20 or newer); it does not include Node.js.

Download pixelbolt.mcpb.sha256 beside the bundle to check its SHA-256:

sha256sum --check pixelbolt.mcpb.sha256
gh attestation verify pixelbolt.mcpb --repo skulitom/Pixelbolt --signer-workflow skulitom/Pixelbolt/.github/workflows/release.yml

On PowerShell, (Get-FileHash pixelbolt.mcpb -Algorithm SHA256).Hash should match the hash in the checksum file.

The GitHub release makes the bundle available immediately. MCP Registry publication is a separate, manually dispatched step after testing; see Publishing.

What's Changed

  • [compass] PixelForge Studio: release checks and 0.7.1 fixes for the portable Windows build by @skulitom in #1
  • [compass] Remove dead code: leftover imports and helpers in scripts and showcase tools by @skulitom in #2
  • [compass] Clean up tests: outline counts in craft.test.js by @skulitom in #3
  • [compass] Remove dead code: unused CSS custom properties in the studio and demo by @skulitom in #4
  • [compass] PixelForge's studio walk: wait for the recompile instead of fixed sleeps (a CI flake) by @skulitom in #5
  • [compass] Clean up tests: stop the release check's launchers together by @skulitom in #6
  • [compass] Remove dead code: writeGIF's unused area constant by @skulitom in #7
  • [compass] PixelForge where agents look: the official MCP Registry by @skulitom in #8
  • [compass] PixelForge where agents look: version 0.7.2 and glama.json by @skulitom in #9
  • [compass] PixelForge release workflows: publish leftover drafts, refuse draft registry entries, start manual runs from the tag by @skulitom in #10
  • [compass] GIF export at ffmpeg's size: keep unchanged pixels, clear only where needed (6.7 MB → 1.08 MB on the asset team's scene) by @skulitom in #11
  • [compass] Clean up tests: run the Studio build tests beside the release check (16.2 s → 13.6 s) by @skulitom in #12
  • [compass] PixelForge becomes Pixelbolt, before its first registry entry by @skulitom in #13

New Contributors

Full Changelog: v0.1.0...v0.8.0

Contributors

skulitom
Assets 4
Loading