Automation tools for KiCAD
This release contains no new features, just bug fixes, and improves compatibility with KiCAD 8.
kicad_dru
file for a board, KiKit crashed. This is fixed (3cb3720106e0b598ccb44a6b684f5dbbf9a76f38)--post 'reconstructarcs: true'
now works correctly (18b590ebe2d6fcaefb510f7782aa06f730ee61e1)footprint_type_mismatch
is not correctly handled (96a964693265d3330ca10c8ce07d10520cde626b)Simply update the Python package. There is no need to update the PCM package.
This release ships mainly with KiCAD 8 support, bug fixes, and a couple of new features. Note that this release drops support for KiCAD v6.
Simply update the Python package. There is no need to update the PCM package. Note that if you are using the official Linux debian packages, you have to use the testing repository at the moment, as the initial release missed scripting support.
I would like to thank all my GitHub Sponsors for their financial support. I would also like to thank all contributors who submitted a PR and everyone who tested KiKit and provided me with steps to reproduce.
VECTOR2I
(ffc6b194c253cd82a1f0755105d221c94ddd5663)Simply update the Python package. There is no need to update the PCM package.
I would like to thank all my GitHub Sponsors and NLnet for their financial support. I would also like to thank all contributors who submitted a PR and everyone who tested KiKit and provided me with steps to reproduce.
If you like KiKit and would like to help it improve, consider supporting me via GitHub Sponsors.
This release brings:
New major release of KiCAD 7 was published. This release brought many incompatibilities, but all should be resolved, and KiKit is compatible with both, KiCAD 6 and KiCAD 7.
The new "In BOM" and"Do not place" options in KiCAD schematics are now supported for the fab
command.
Getting everything right for v7 took a little longer than anticipated, and we didn't manage to meet this release with the release of KiCAD.
We used to keep documentation in Markdown files in the repository. We now provide a documentation build as an interactive webpage available at https://yaqwsx.github.io/KiKit/. This documentation is also available for various released versions, so there should be no confusion between stable release and upstream documentation in the future. New system will also allow us to style the documentation better (e.g., checkout the new Examples section). There's definitely still a lot to improve, but the first step has been made.
dimensions
, to the post
section that will render dimensions objects showing the overall size of the panel.post
option millradiusouter
which simulates the milling only on the outside edges of PCB and leaves any internal features intact.fillet
for tabs that will add natural chamfering without milling simulation. However, the feature is relatively slow and can increase panel building times by 20–50 %. There are plans for speeding this up, but it will require a complete rewrite of the geometrical part of KiKit.boneskip
parameter to skip backbones we now added vbonefirst
and hbonefirst
parameters to specify the offset of skipping (e.g., start at even or odd backbone).fab
command was fixSimply update the Python package. There is no need to update the PCM package.
I would like to thank all my GitHub Sponsors and NLnet for their financial support. I would also like to thank all contributors who submitted a PR and everyone who tested KiKit and provided me with steps to reproduce.
If you like KiKit and you would like to help it improve, consider supporting me via GitHub Sponsors.
This release brings several bug fixes and small improvements in functionality.
Bugfixes:
all
in the layer selectorNew features:
50%
to place the panel in the middle of the page.This release brings several bugfixes:
{time24}
was fixedzip
executable (so all commands now work well on Windows)With these bugfixes the following options were added:
--debug
flag for the fab commandAll users are encouraged to upgrade.
This release fixes packaging problem (see details). There are no new features. If you managed to install KiKit, there is no need to update.
This release brings a large number of new features and several bug fixes. Since the feature list is quite long, we discuss them in depth in a related blog post.
This is also the first version that drops KiCAD 5 support, as most of the new features require KiCAD 6. If you use KiCAD 5 you can continue to use v1.0.5.
Full Changelog: https://github.com/yaqwsx/KiKit/compare/v1.0.5...v1.1.0
There is no need to update the PCM plugin, updating the python package is sufficient.
Having all these new features & bug fixes wouldn’t be possible without the support of my Github Sponsors. Your support allows me to allocate more time to maintain my open-source projects. I really appreciate your trust in me.
I would also like to thank all of you who hired me to fix a bug in KiKit, implement a feature or build a custom workflow for you. When I started KiKit two years ago, I didn’t imagine what could be accomplished using KiKit.
This is only a small release that fixes problems with a broken dialog when no KiKit backend is found in the GUI plugin. This affects only the new users, if you already use KiKit, there is no need to update at the moment.
This release is initiated by the release of the click library v8.1.0 which removes some deprecated API we were using in order to ensure compatibility with both, click v7 and v8, and thus, lower the risk of package incompatibility. When users try to freshly install KiKit v1.0.3, click v8.1 is downloaded and KiKit fails.
This version brings in changes that ensure compatibility with the newest click version (8.1) and also the currently most frequently used one (7.1). Therefore, it fixes problems with the fresh installation of KiKit.
Also, all numerical problems in KiKit were solved so KiKit is now "nanometer-precise". The reason for (what I originally believed to be) numerical imprecision was actually quite silly. More details in the changes of kikit/common.py
in e146259e37c71a0a3a537fa8a8e3986f5cd53355.
In addition, this release brings several fixes:
To update, please update both, the Python package and PCM plugin.