On 14 Apr 2026, at 2:26, Robert Sawicki wrote:
> I'll chime in here, as I was also a bit confused when exploring the GitHub,
> Heptapod, PyPi and the project's documentation.
>
> It seems that the newest version of the library on PyPi is, as of the time
> of writing this, 3.1.5. The documentation linked in PyPi and Heptapod,
> however, marks "Stable" as 3.1.3 and "Latest" as 3.1.4.
It's pretty clear:
https://foss.heptapod.net/openpyxl/openpyxl/-/commit/13627b03ca25a1a98becf40e533b955615b13429
3.1.5
> I'm a bit more cautious after what happened to Axios, so I gotta' ask - is
> 3.1.5 the current "stable" release? If so, could we also mark that in the
> docs?
You might want to expand on the subject because not everyone is aware of it: Axios was recently compromised and at least one very common library was released with very dangerous code. We can expect to see more and more "supply chain" attacks. I've had at least two myself that nearly succeeded – no-one should think they're immune – but my account cannot be compromised password alone. Openpyxl is considered an important library and a few years Google provided hardware devices for free. Google comes in for criticism but has been pretty good when it come to open source and security in my experience.
This is a problem related to the build process on RTD: they deliberately removed support for Mercurial so we couldn't build the docs there any more. We do build them directly on Heptapod but only for one version at a time. Apparently, there is a way of building the docs using Mercurial for RTD but I haven't had time to look at it in detail.
> Thanks for your time and the great work you've been putting out.
> Have a great one!
I'm hoping to have some more time to work on the project this year.
Charlie
--
Charlie Clark
Managing Director
Clark Consulting & Research
German Office
Sengelsweg 34
Düsseldorf
D- 40489
Tel:
+49-203-3925-0390
Mobile:
+49-178-782-6226