Release and Roadmap
This page summarizes public release and planning information for Cindr3D.
| Step | Output |
|---|---|
| Validate | TypeScript, lint, tests, build, and WASM checks pass |
| Build | Static dist/ output is generated |
| Package | Release ZIP contains index.html and assets/, or dist/index.html and dist/assets/
|
| Publish | GitHub release includes the static asset |
| Verify | Static host or device updater can install and serve the release |
The repository package version is tracked in package.json.
As of the current wiki update:
0.4.3
The v0.3.0 release focused on design workspace depth, workshop integrations, and operational polish.
Design highlights:
- Parametric model library
- Design configurations
- Drawing workspace
- Mesh repair
- Non-destructive boolean history
- Threading library
- Sketch tangent solving
Workshop highlights:
- Generic webhooks
- Discord, Slack, Telegram, and MQTT notification bridges
- Home Assistant bridge
- Slicer profile exchange
- Power-loss recovery
- Enclosure safety
- Stepper driver tuning
Preview highlights:
- Raw G-code dock panel
- Print Preview dashboard card
- PTZ camera improvements
The self-updater installs release assets rather than building from master on the device.
Recommended release asset name:
cindr3d-dist.zip
Accepted archive layouts:
index.html
assets/
or:
dist/index.html
dist/assets/
Use prebuilt assets for Orange Pi or other small-device deployments. This avoids a full Node install and production build on the target machine.
Roadmap details are tracked in the repository file:
TaskLists.txt
Current planning themes include:
- Printer calibration center
- Plugin system
Shipped phases are condensed in TaskLists.txt with summaries. Active or upcoming phases keep more detailed tasks, effort estimates, file hints, and dependency notes.
Before publishing a release:
- Run the main validation commands.
- Build production files.
- Verify WASM artifacts and budget.
- Package the static output into a release asset.
- Confirm the archive layout matches updater expectations.
- Test the release asset on a static host or staging device.
Suggested commands:
npm run typecheck
npm run lint
npm run test:run
npm run build
npm run verify:wasm-build
npm run check:wasm-budget