Two of my libraries, sebajost/BlaeckSerial and sebajost/BlaeckTCP, were
registered in 2020 and appear to still be on the legacy auto-crawler. Versions get
published to the registry whenever I change the version field in
library.properties — no tag, no pio pkg publish, and no publishing workflow in
either repository.
Seven versions arrived this way, each on the day its version bump was committed:
BlaeckSerial 5.0.2 2026-03-31
6.0.2 2026-07-01
7.0.0 2026-08-08
BlaeckTCP 5.0.3 2026-03-31
6.0.2 2026-07-14
6.1.0 2026-08-06
7.0.0 2026-08-07
None of them has a git tag. Arduino’s Library Manager, which publishes from tags,
is still on 6.0.1 for both as a result. I had not installed PlatformIO Core at all
until yesterday, so none of these were published by me.
The practical problem is that the version field acts as a publish trigger. I bumped
both to 7.0.0 early in a development cycle and kept working, so the 7.0.0 that users
can install today is a mid-development snapshot rather than a release. I have a few
months of work ahead on both and would like to stop that happening again.
Two questions:
-
maxgerhardt mentioned in an older thread that the crawler versus manual
publishing is "a setting per-libanged for these two
libraries on request, without publishing a version? I would rather not spend a
version number on each purely to -
Is ivankravets’ statement in that publishing one
version manually disables auto-crawling permanently? It is from 2021, so I would
like to confirm before relying ohttps://community.platformio.orgished-with-old-platformio-registry-method/18855/8
Unrelated and minor: the registry links release notes to
https://github.com/sebaJoSt/Blaeckwhich 404s. My tags have no vprefix, so the working URL is…/releases/tag/6.0.1. It looks like the link is built by prepending v`pository’s tags.
The same applies to BlaeckTCP.
Thanks.