Releases: photon-hq/create-spectrum-project
Release list
create-spectrum-project v0.9.0
New Features
- Spectrum Cloud setup now reads the project’s existing secret into
.envinstead of rotating it, including when using--projectId. This keeps any live integrations working. 🔐
Bug Fixes
- Next-step
cdcommands are now correct for current-directory, nested, sibling, and space-containing paths. - Cloud error hints now use the same package-runner command the scaffolder uses, so
whoamihelp works even without a globalphotoninstall. - The release workflow now has package publish permission, so v0.9.0 can publish correctly.
Improvement
- README and help output now describe
--yes,--no-cloud, and project-secret behavior more clearly.
Version: 0.9.0
create-spectrum-project v0.8.0
New Features
- Added an optional post-scaffold prompt to support Spectrum: if you say yes, it stars
photon-hq/spectrum-tsand follows@photon-hqthrough the GitHub CLI. ⭐ - The prompt only appears when
ghis installed, authenticated, and the session is interactive; it is skipped for-y, CI, logged-out GitHub CLI sessions, or missinggh.
Improvement
- GitHub support actions are best-effort, so a failed star or follow shows a warning but never breaks a successfully created project. README docs now explain when this prompt appears.
Version: 0.8.0
create-spectrum-project v0.7.0
New Features
- Added
--projectId, so you can scaffold against an existing Spectrum Cloud project instead of creating a new one. The CLI can writePROJECT_IDand, when you choose to rotate the secret,PROJECT_SECRETinto.env.
Bug Fixes
- Fixed the existing-project flow so choosing not to rotate the project secret no longer requires Spectrum Cloud auth first.
Improvement
- Updated
--help, README examples, and tests around existing project setup so the new flow is easier to discover and safer to use. ✨
Version: 0.7.0
create-spectrum-project v0.6.0
New Features
-
Spectrum Cloud setup now works for all supported platform providers, not just iMessage. Selected platforms are passed into Cloud provisioning automatically. ✨
-
Added
--platformsas a clearer alias for--providers, so commands like--platforms imessage,telegramnow work.
Bug Fixes
-
Fixed Cloud provisioning for providers like
whatsapp-businessby normalizing platform names correctly before sending them to Spectrum Cloud. -
Fixed Cloud project creation by always including iMessage when provisioning, since Spectrum Cloud requires it.
Improvement
-
Updated CLI help and README examples to use
--platforms, while keeping--providerssupported for compatibility. -
Added focused unit coverage for platform flag parsing and Spectrum Cloud platform provisioning behavior.
Version: 0.6.0
create-spectrum-project v0.5.0
New Features
- The CLI can now set up Spectrum Cloud during project creation for iMessage apps. It logs you in if needed, creates the cloud project, generates credentials, and writes them into
.env. ✨ - Added
--no-cloudso you can skip cloud setup when you want to fill in credentials yourself.
Bug Fixes
- The
.envreminder now still appears when cloud setup fillsPROJECT_IDandPROJECT_SECRETbut provider-specific values, likeTELEGRAM_BOT_TOKEN, are still empty. - Skill installation no longer creates extra agent folders for every registered agent. It now installs the Spectrum skill into the universal agent path only.
Improvement
- New projects now include clearer
AGENTS.mdguidance for managing Spectrum Cloud with thephotonCLI, including login, secret rotation, line listing, and project inspection.
Version: 0.5.0
create-spectrum-project v0.4.0
New Features
- Added Telegram as a supported provider, so new projects can scaffold a Telegram bot alongside terminal, iMessage, and WhatsApp Business. 🎉
- Telegram projects now generate the right
telegram.config({ botToken: process.env.TELEGRAM_BOT_TOKEN! })setup and includeTELEGRAM_BOT_TOKENin the generated environment files.
Improvement
- Updated the generated
.env.exampleand README setup guidance so provider-specific credentials show where they come from, like getting the Telegram bot token from@BotFather. - Added golden and unit test coverage for Telegram-only and all-platform scaffolds, making provider setup easier to validate going forward.
Version: 0.4.0
create-spectrum-project v0.3.1
Bug Fixes
- Projects created with
npm,pnpm, oryarnnow get workingstartanddevscripts usingtsxinstead of Bun-only commands. - Generated TypeScript settings now match the selected package manager, so Node-based projects use Node types while Bun projects keep Bun types.
Improvement
- Added coverage for package-manager-specific scaffolding so future changes are less likely to break generated project scripts. ✨
Version: 0.3.1
create-spectrum-project v0.3.0
New Features
- New projects now include
AGENTS.mdandCLAUDE.md, so AI coding agents get Spectrum-specific project context right away. - The CLI now installs the
spectrumagent skill by default, with a new prompt and--no-skillsflag if you want to skip it. ✨
Bug Fixes
- If skill installation fails, the CLI now gives a clearer retry command and uses the right runner for the environment (
bunxunder Bun,npxotherwise). - Skipping skills no longer shows an “Installing Spectrum skill…” status message.
Improvement
- The README now matches the new flow, including updated
bun create/npm createexamples and the new skill-install option. - Added focused test coverage for skill installation, skip behavior, failure handling, and Claude auto-discovery setup.
Version: 0.3.0
create-spectrum-project v0.2.0
Breaking Changes
-y now defaults to the first platform provider, currently imessage, instead of terminal. Use --providers terminal if you want the local dev TUI behavior.
New Features
Generated platform projects now include a ready-to-fill .env alongside .env.example, so you can add credentials immediately without copying files first.
Bug Fixes
Generated README files now point to the correct Photon dashboard URL: https://app.photon.codes.
Improvement
The CLI now uses “Platforms” instead of “Production” in prompts and messaging, making the setup flow clearer for messaging interfaces. ✨
Version: 0.2.0
create-spectrum-project v0.1.1
Bug Fixes
- Fixed the release workflow for the first npm publish by using
NPM_TOKENinstead of OIDC trusted publishing. This letscreate-spectrum-projectv0.1.1 publish cleanly before trusted publishing is configured on npm. 🚀
Version: 0.1.1