releases

Releases

CCL_Clay3DP follows Semantic Versioning with an -alpha suffix while pre-release. Every release is tagged in git, summarized in CHANGELOG.md, and published as a GitHub Release object with the dist bundle attached.

Download the latest from Releases on GitHub.

📷 GitHub Releases page screenshot showing the latest release with the dist bundle attached.

Released versions

Version	Date	Highlights
1.2.1-alpha	2026-05-03	Panel handler / timer leak fix; ARCHITECTURE.md refresh; code-review cleanup
1.2.0-alpha	2026-05-03	Settings UI redesign (landscape 3-col); Material section expansion (Water %, Shrinkage); build-volume safety; auto-rebuild on settings + geometry change; Skirt + Base in Preview; elliptical-pipe preview; ARCHITECTURE.md added
1.1.1-alpha	2026-04-25	Skirt; Build Volume preview; Print Position marker; auto-translate to origin; Import/Export settings; bundled CCL RoboDK config; PBR clay material per preset; spiral-follows-curve-normal; Outer Wall Bracing ruled-geometry gate
1.1.0-alpha	earlier	Initial polish-branch base — Spiral / Layer modes, printability analyzer, RoboDK Send, original Inner Wall Bracing
1.0.3-alpha	earlier	Earliest tagged version

For full per-release detail (Added / Changed / Fixed / Removed / Migration notes), read CHANGELOG.md. The wiki only summarizes; the changelog is canonical.

Dist bundle convention

Each release ships as CCL_Clay3DP-vX.Y.Z-alpha.zip containing:

CCL_Clay3DP-vX.Y.Z-alpha/
├── CCL_Clay3DP.dll              ← the plugin
├── Newtonsoft.Json.dll          ← dependency
├── PostProcessor/
│   └── KUKA_CNC_2_1_ISG_CCL_3DP_…HSC_WAIT_S_DELAY.py
├── robodk_station/
│   ├── 3DP_v0.4.rdk
│   ├── settings.ini
│   └── layout6.0.1.ini
├── README.md
├── CHANGELOG.md
├── LICENSE
└── NOTICE

The bundle is build-output only — no source. To compile from source, see Install — Path B.

Release workflow checklist

For maintainers cutting a new release:

Pre-tag

• Bump <Version> in CCL_Clay3DP/CCL_Clay3DP.csproj
• Add a CHANGELOG.md entry under ## [X.Y.Z-alpha] — <date> with Added / Changed / Fixed / Removed / Migration sections as relevant
• Bump the version line in README.md (top of file)
• Clean build: dotnet build -c Release
• Run gitleaks on working tree: gitleaks detect
• Verify gitleaks reports zero findings

Tag and push

• git tag vX.Y.Z-alpha (annotated optional)
• git push origin main
• git push origin vX.Y.Z-alpha

Build dist bundle

• dotnet build -c Release → bin/Release/CCL_Clay3DP.dll
• Mirror the prior release's bundle layout under dist/CCL_Clay3DP-vX.Y.Z-alpha/
• Copy DLL, dependency, post-processor, station folder, README, CHANGELOG, LICENSE, NOTICE
• Zip the folder

Create the GitHub Release object

• On GitHub, Releases → Draft a new release (right sidebar of the repo home, or …/releases/new)
• Tag: vX.Y.Z-alpha
• Title: CCL_Clay3DP vX.Y.Z-alpha
• Notes: copy the relevant CHANGELOG section
• Attach the zip as a release asset
• Publish

⚠ The git tag and the GitHub Release object are separate. Pushing a tag does NOT create a Release. The Release object is what users see on the Releases page and what carries the dist bundle download. Skip this step and the release is invisible.

📷 GitHub "New release" form filled out with tag, title, notes, and attached zip.

Post-release

• Bump csproj <Version> to next planned (e.g. 1.2.2-alpha) on a follow-up commit so working state isn't tagged the same as released
• Update Releases page on this wiki with the new entry
• If the release introduced new fields / settings / CLI flags, update Settings reference and Pipeline pages

Past slips worth remembering

The v1.2.0 / 1.2.1 cycle exposed a few easy-to-miss steps:

• Forgot the README version bump in 1.2.0 — caught and patched in 1.2.1.
• Forgot the GitHub Release object initially — git tag was pushed but no Release page existed. The checklist above makes this an explicit item.
• Forgot the post-tag csproj bump initially — committed via ce6c058 after the fact. Now an explicit post-release step.

See also

• CHANGELOG.md — canonical per-release detail
• Install — how to consume a release
• Contributing — how to land changes that go into a release