support-fins

blender

plugins: real version numbers, stamped by every build -- 0.7.<n>, n = the position on main of the last commit that changed what that plugin ships (its folder, tests and notes aside, plus every file esbuild bundles into it and the shared Python host), so a plugin gets a new version exactly when it changes and never otherwise (the PrusaSlicer port doesn't move with the engine); plugins/shared/version.py computes it, each build stamps it into the plugin's own manifest (Orca header, Fusion manifest, Cura plugin.json + package, Blender manifest, Rhino package, SolidWorks assembly, Prusa manifest via a new build.py, a FreeCAD VERSION its console line shows) and the command line and MCP server compile it in (support-fins --version); sources hold the unstamped 0.7.0, above every hand-set number before (Fusion 0.6.2) so no host sees a downgrade; CI checks out full history for it and refuses a shallow clone; release labels show the same numbers

2026-10-19 18:13:31 -05:00

cli

CLI resume: --check and --list-plates (added on main since) refuse --resume too, as --list-objects does -- neither generates fins, so a cache would only be opened and left behind

2026-10-21 09:58:50 -05:00

cura

cura: settings dialog declares the i18n catalog Cura.ComboBox reads -- each choice row logged 'Cannot read property i18nc of undefined' (ComboBox.qml:18) on open (#364 ); it sits in the ColumnLayout because UM.Dialog's children take Items only

2026-10-21 11:15:37 -05:00

freecad

plugins: real version numbers, stamped by every build -- 0.7.<n>, n = the position on main of the last commit that changed what that plugin ships (its folder, tests and notes aside, plus every file esbuild bundles into it and the shared Python host), so a plugin gets a new version exactly when it changes and never otherwise (the PrusaSlicer port doesn't move with the engine); plugins/shared/version.py computes it, each build stamps it into the plugin's own manifest (Orca header, Fusion manifest, Cura plugin.json + package, Blender manifest, Rhino package, SolidWorks assembly, Prusa manifest via a new build.py, a FreeCAD VERSION its console line shows) and the command line and MCP server compile it in (support-fins --version); sources hold the unstamped 0.7.0, above every hand-set number before (Fusion 0.6.2) so no host sees a downgrade; CI checks out full history for it and refuses a shallow clone; release labels show the same numbers

2026-10-19 18:13:31 -05:00

fusion

plugins: real version numbers, stamped by every build -- 0.7.<n>, n = the position on main of the last commit that changed what that plugin ships (its folder, tests and notes aside, plus every file esbuild bundles into it and the shared Python host), so a plugin gets a new version exactly when it changes and never otherwise (the PrusaSlicer port doesn't move with the engine); plugins/shared/version.py computes it, each build stamps it into the plugin's own manifest (Orca header, Fusion manifest, Cura plugin.json + package, Blender manifest, Rhino package, SolidWorks assembly, Prusa manifest via a new build.py, a FreeCAD VERSION its console line shows) and the command line and MCP server compile it in (support-fins --version); sources hold the unstamped 0.7.0, above every hand-set number before (Fusion 0.6.2) so no host sees a downgrade; CI checks out full history for it and refuses a shallow clone; release labels show the same numbers

2026-10-19 18:13:31 -05:00

mcp

plugins: real version numbers, stamped by every build -- 0.7.<n>, n = the position on main of the last commit that changed what that plugin ships (its folder, tests and notes aside, plus every file esbuild bundles into it and the shared Python host), so a plugin gets a new version exactly when it changes and never otherwise (the PrusaSlicer port doesn't move with the engine); plugins/shared/version.py computes it, each build stamps it into the plugin's own manifest (Orca header, Fusion manifest, Cura plugin.json + package, Blender manifest, Rhino package, SolidWorks assembly, Prusa manifest via a new build.py, a FreeCAD VERSION its console line shows) and the command line and MCP server compile it in (support-fins --version); sources hold the unstamped 0.7.0, above every hand-set number before (Fusion 0.6.2) so no host sees a downgrade; CI checks out full history for it and refuses a shallow clone; release labels show the same numbers

2026-10-19 18:13:31 -05:00

onshape

plugins: gap review fixes -- Blender's float32 gap at 0.4 is in range, Onshape's gap bounds are the site's 0.1-0.4, Cura README

2026-10-14 07:54:03 -05:00

orca

draw: a mixed run's squat stem sits inside the full wall's stem, not on its faces -- the squat run reaches two stations into each tall neighbour so the two overlap, but over those stations sweepSquat's stem had the full wall's exact section, so their side, tip and bed faces coincided (duplicate faces, edges shared by four triangles). Full coverage builds these walls through draw.js, and a slicer that reads the mesh's topology lost their section on the low layers: the Orca plugin's own slicer dropped up to 6.7 / 10.8 mm2 a layer of real fin on two roof parts (z 0.5-1.9), and the exact-match test's trimesh oracle disagreed with it on lbracket (057). The squat stem is now 0.01 mm narrower each side on the shared stations (sweepSquat's new per-station inset). Auto sweep byte-identical (864 cases); the Orca exact-match test gains a Full case

2026-10-20 08:00:16 -05:00

prusa

plugins: real version numbers, stamped by every build -- 0.7.<n>, n = the position on main of the last commit that changed what that plugin ships (its folder, tests and notes aside, plus every file esbuild bundles into it and the shared Python host), so a plugin gets a new version exactly when it changes and never otherwise (the PrusaSlicer port doesn't move with the engine); plugins/shared/version.py computes it, each build stamps it into the plugin's own manifest (Orca header, Fusion manifest, Cura plugin.json + package, Blender manifest, Rhino package, SolidWorks assembly, Prusa manifest via a new build.py, a FreeCAD VERSION its console line shows) and the command line and MCP server compile it in (support-fins --version); sources hold the unstamped 0.7.0, above every hand-set number before (Fusion 0.6.2) so no host sees a downgrade; CI checks out full history for it and refuses a shallow clone; release labels show the same numbers

2026-10-19 18:13:31 -05:00

rhino

plugins: real version numbers, stamped by every build -- 0.7.<n>, n = the position on main of the last commit that changed what that plugin ships (its folder, tests and notes aside, plus every file esbuild bundles into it and the shared Python host), so a plugin gets a new version exactly when it changes and never otherwise (the PrusaSlicer port doesn't move with the engine); plugins/shared/version.py computes it, each build stamps it into the plugin's own manifest (Orca header, Fusion manifest, Cura plugin.json + package, Blender manifest, Rhino package, SolidWorks assembly, Prusa manifest via a new build.py, a FreeCAD VERSION its console line shows) and the command line and MCP server compile it in (support-fins --version); sources hold the unstamped 0.7.0, above every hand-set number before (Fusion 0.6.2) so no host sees a downgrade; CI checks out full history for it and refuses a shallow clone; release labels show the same numbers

2026-10-19 18:13:31 -05:00

shared

resin: Separate walls (#309 ) -- a Full coverage box that keeps every fill wall apart: none crosses another or joins its flange on the plate (never the flange or joined retries, on either pass, and no shared flange band for rows, ribs or ties), because resin cures joined walls into one block that won't break away; it ticks itself when Direction is set to Vertical (resin) and unticks for Horizontal, then is the user's; off builds exactly as before (sweep 864/864 identical). Costs a little coverage: buster bare 8135 -> 8553 mm2, m4 front 737 -> 825, the guardian lion 0.7 -> 2.8; fused fill walls 6 -> 0, 26 -> 0 (m4's 10 left are Auto's split pieces), 4 -> 0

2026-10-21 09:03:16 -05:00

solidworks

plugins: real version numbers, stamped by every build -- 0.7.<n>, n = the position on main of the last commit that changed what that plugin ships (its folder, tests and notes aside, plus every file esbuild bundles into it and the shared Python host), so a plugin gets a new version exactly when it changes and never otherwise (the PrusaSlicer port doesn't move with the engine); plugins/shared/version.py computes it, each build stamps it into the plugin's own manifest (Orca header, Fusion manifest, Cura plugin.json + package, Blender manifest, Rhino package, SolidWorks assembly, Prusa manifest via a new build.py, a FreeCAD VERSION its console line shows) and the command line and MCP server compile it in (support-fins --version); sources hold the unstamped 0.7.0, above every hand-set number before (Fusion 0.6.2) so no host sees a downgrade; CI checks out full history for it and refuses a shallow clone; release labels show the same numbers

2026-10-19 18:13:31 -05:00