heatwave

update to support newer versions of IPython. (can't we all just get along?)

boringbungalow

this is a boring release, which is actually pretty awesome.

bugfix: rfcat_bootloader had a python3 bug causing issues with verifying that firmware was correctly pushed
specan: pip install rfcat[specan] installs Pyside2 to make it easier.

anyone with ideas for how to make v2.0.0 pop, please drop some issues or hit me with suggestions. :)

trusty

the code is relatively stable.
should release v2.0 soon

nomopysi

removed PySide2 from requirements.txt, as it's not available on all platforms RfCat is desired on.
SpecAn now requires $ pip install PySide2

touchmebabyonemoretime

bugfix for bug introduced in last checkin. thanks @mnhauke !

dead_marshes

added "safemode" to allow RfCat startup (with limitations) for borked dongles using firmware compiled with sdcc>3.5.0 (mostly so we can get into bootloader mode without tapping the magic pin headers, but also for troubleshooting)
bugfixes in vstruct and unittests
bugfixes in rfcat_bootloader (py3 works now! although slow verification :( )

lord_helmet

prepare to release 2.0.0!

killing py3 bugs as we find them.
also, since SDCC v3.5.0 is the last version to correctly build RfCat firmware (working on it @meeas!), inserted a Makefile catch that will keep you from installing dorked firmware with later versions of SDCC.
moved vstruct inside rflib, so as not to conflict with the real thing when people have Vivisect and/or some other Vstruct using tool installed.

same firmware as 1.9.2, look there for precompiled binaries.

more improvements on python3

whackamole, and covering over my plundering PyPi pipeline :) hopefully better this time.

inevitable Python3 support

currently preparing for v2.0.0: completely Python3 compatible.

please test from here on out, issue Pull Requests and bug reports! make v2.0.0 amazing!

also, if you have enhancements for RfCat you wish to share, please make a Pull Request or tag us in your public repo!

@

about time.

my apologies for failing my responsibilities of maintaining real versioning here. i suppose this has only been 9 years in the making
it's been a while since i've managed semantic versioning, and never on github. bear with me and give me feedback. i'm bound to get things wrong.

thanks,
@