Disable the legacy auto-crawler for a library without publishing a version?

Registry
1

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:

  1. 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

  2. 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 o

    https://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.

2

Maxbe u can just delete both libaries and disable the autocrawler, so I can release later the right versions.

3

The legacy crawler appears to be publishing these versions automatically. Changing library.properties seems sufficient to trigger publishing.

4

yes, but how to disable the autocrawler? this behavior leads to prereleases being published to platformio

5

CC @ivankravets for library management

6

The autocrawler was disabled for your libraries. Once a new release is ready, please publish them manually using pio pkg publish path/to/library/folder. For more information, see the pio pkg publish — PlatformIO latest documentation