Development tools and version scope
Development preview. These pages describe the local 1.5.20 development checkout reviewed on 5 November 2026. They do not announce a 1.5.20 release or imply that the testing PCM catalogue contains it. Public GitHub releases were checked: 1.4.1 remains the latest stable release.
Use the stable manual for normal installation and everyday released workflows. Use these pages when testing the corresponding source or an explicitly identified testing build.
Feature and version map
Section titled “Feature and version map”| Capability | Stable 1.4.1 | Reviewed development checkout |
|---|---|---|
| Labels, symbols, title/subtitle and underline | Available | Extended with overline, scoped formatting, multipart labels and placement anchors |
| Header overlays | Single-row 2.54 mm | Renamed Connector Overlay; standard/custom pitch |
| Component callouts and arrays | Available with bundled/custom dimensions | Reusable personal/project component presets |
| Custom SVG symbols and variants | Strict filled SVG profile | Broader geometry import and graphic previews |
| Standalone imported graphics | No dedicated editor | Graphics tool with transforms and PNG tracing |
| Fonts | Bundled typefaces | System-font activation, Google Fonts browsing/install/repair |
| Saved profiles and library backup | Available | Expanded data coverage |
| Native reference designators and cleanup | No Board Tools family | Selection-aware designator styling and scoped cleanup |
| Variable templates | No Variables tab | Personal/project multiline templates and KiCad tokens |
| Project Data | No Project Data workspace | Metadata, reusable fields, revision checkpoints and explicit KiCad synchronization |
Development guides
Section titled “Development guides”- Fonts, SVGs, PNG tracing and graphics
- Designators, cleanup, variables and advanced labels
- Project Data and revision workflows
Connector overlays at another pitch
Section titled “Connector overlays at another pitch”- Open Labels → Connector Overlay.
- Choose a standard pitch or Custom.
- For Custom, enter the physical pitch. The reviewed UI supports 0.50–20.00 mm.
- Check the live maximum text-height indication. Smaller pitch reduces the space available to each pin label.
- Enter count/labels, orientation and pin-1 end, then set the plug opening and clearances.
- Verify first and last positions against the actual electrical footprint before placing the complete rail.
Unit switching preserves pitch physically. Do not enter a millimetre value into a mil-labelled field. Existing 2.54 mm artwork is intended to remain compatible, but check it on a board copy when testing a new build.
Reusable component presets
Section titled “Reusable component presets”Open Settings → Components, choose personal or project scope, and add a preset with the actual component envelope and useful identifying name. Edit/delete through the same manager. Use the preset from Component Callout or Component Array, then review its dimensions in the active tool.
Placed artwork embeds its dimensions, so deleting a preset should not change an already-placed envelope. Preserve the preset library for future new artwork and verify regeneration on a copy during development testing.
Test before depending on a development build
Section titled “Test before depending on a development build”Back up the board and personal library, record the exact commit/package version, and use disposable copies for cleanup and bulk-designator operations. Compare placement, reopen/update, save/reload and undo behaviour.
The source’s manual validation record reports macOS testing, including live IPC placement/update and native save/reload. Windows/Linux visual acceptance, 3D/GerbView orientation acceptance and specific upstream KiCad crash conditions still need release checks. That evidence does not establish release readiness on every platform.
The reviewed source guards transactions on KiCad 10.0.0–10.0.6 when Schematic Editor is open because of an upstream crash condition. If the build asks you to close Schematic Editor or upgrade, follow that instruction before retrying rather than repeatedly applying the action.
Published packages and release status must be checked separately from the version string in a source checkout. The source validation notes and release pipeline provide development context; their branch content may change.