Skip to content

v3.0.1: TailTiny rename completed

Choose a tag to compare

@Asimmimx Asimmimx released this 13 Oct 06:35
· 39 commits to main since this release

Completes the v3.0.0 notes and finishes the rename. No change to how the library works.

Log output changed in v3.0.0 (missing from its notes)

Before After
Log tag microlink tailtiny
MicroLink v2 initialized (max_peers=N) TailTiny initialized (max_peers=N)
Config web page title "MicroLink" "TailTiny"
Example logs: "MicroLink state", "Failed to initialize MicroLink", ... "TailTiny state", "Failed to initialize TailTiny", ...

If you call esp_log_level_set("microlink", ...), or a script or test rig looks for microlink or MicroLink v2 initialized in the serial output, change it to tailtiny / TailTiny initialized.

Examples

All examples now build as tailtiny_<name> (for example build/tailtiny_failover_connect.bin). v3.0.0 had renamed only basic_connect and cellular_connect; cellular_heartbeat, failover_connect and rebind_test follow now.

Code comments

  • The NVS namespace "microlink" now has a comment explaining why it must not be renamed (devices would lose their Tailscale identity).
  • Source references point again to the upstream MicroLink v1 files they came from.

Included from v3.0.0 (not released separately)

MicroLink is now TailTiny. Only the name changed; the code does the same as v2.3.1.

Updating an existing project

Before After
components/microlink/ components/tailtiny/
REQUIRES microlink REQUIRES tailtiny
#include "microlink.h" #include "tailtiny.h"
#include "microlink_internal.h" #include "tailtiny_internal.h"
microlink_* functions and types (microlink_init(), microlink_t, ...) tailtiny_* (tailtiny_init(), tailtiny_t, ...)
menuconfig: "MicroLink V2 Configuration" "TailTiny Configuration"
github.com/Asimmimx/microlink github.com/Asimmimx/tailtiny (the old link redirects)

Unchanged: the CONFIG_ML_* options and ml_* names, so sdkconfig and sdkconfig.credentials files keep working. The keys are still stored in the NVS namespace "microlink", so a device updated from v2.x keeps its Tailscale identity and doesn't need a new auth key.