Skip to content

[#134] Release readiness - distribution, versioning, CI, and packaging#136

Open
milkyskies wants to merge 6 commits intomainfrom
feature/#134.release-readiness
Open

[#134] Release readiness - distribution, versioning, CI, and packaging#136
milkyskies wants to merge 6 commits intomainfrom
feature/#134.release-readiness

Conversation

@milkyskies
Copy link
Owner

closes #134

Summary

  • Release workflow: Cross-platform binary builds (macOS arm64/x86, Linux x86/arm64, Windows) triggered on git tags, uploads to GitHub Releases
  • release-please: Automated version bumps, CHANGELOG generation, and Release PRs from conventional commits
  • CI: Added example app build check (compiles .fl files, builds todo app) to catch regressions
  • Package metadata: Added crates.io metadata (description, license, repository) to Cargo.toml, repository info to vite-plugin-floe
  • VS Code extension: Added license, marketplace icon field, renamed icon paths from zs-* to floe-*, created icons directory
  • LICENSE: Added MIT license file
  • CHANGELOG: Seeded with current features
  • Conventional commits: Added rule to workflow.md so agents use feat:/fix:/chore: prefixes
  • Playground: Added WASM build script, updated sample code to new syntax (fn, |x|, .field, ->)
  • Root package.json: Fixed filter names from zenscript-* to floe-*

Still needed (not blocking this PR)

  • Actual VS Code extension icon images (design task)
  • VS Code Marketplace publisher account + VSCE_PAT secret
  • npm publish token for vite-plugin-floe
  • crates.io token for cargo publish
  • Playground hosting (GitHub Pages, Vercel, etc.)

Test plan

  • cargo fmt passes
  • cargo clippy -- -D warnings passes
  • cargo test passes (12/12)
  • Verify release workflow triggers correctly on tag push
  • Verify release-please opens Release PRs on merge to main

milkyskies and others added 6 commits March 14, 2026 15:09
- Add release workflow for cross-platform binary builds (macOS, Linux, Windows)
- Add release-please for automated version bumps and CHANGELOG generation
- Add example app build check to CI pipeline
- Add MIT LICENSE file
- Add crates.io metadata to Cargo.toml (description, license, repository, etc.)
- Add repository metadata to vite-plugin-floe package.json
- Add license and icon fields to VS Code extension package.json
- Fix root package.json filter names (zenscript -> floe)
- Add conventional commits rule to workflow.md
- Rename VS Code extension icon paths from zs-* to floe-*
- Seed CHANGELOG.md with current features

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
…directory

- Add playground/build.sh for wasm-pack WASM builds
- Update playground sample code to use new syntax (fn, |x|, .field, ->)
- Add playground/.gitignore for generated pkg/ directory
- Create VS Code extension icons directory with README

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Explains how conventional commits, release-please, and the release
workflow fit together so the team knows how versioning works.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
macOS and Windows jobs stay on GitHub-hosted runners since
Ubicloud only provides Linux runners.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
…s.io publish

- Rename vite-plugin-floe to @floelang/vite-plugin across all files
- Update VS Code extension publisher to floelang
- Add publishConfig with public access for scoped npm package
- Add publish steps to release workflow: crates.io, npm, Open VSX
- Update all imports (todo app, vite docs, plugin source)
- Update CLAUDE.md with package names table

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
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.

Release readiness - distribution, versioning, CI, and packaging

1 participant