Tags

Tags give the ability to mark specific points in history as being important

  • v0.5.1

    4e0a7d36 · chore: bump version to 0.5.1 ·
    Release: v0.5.1 
    v0.5.1: CI validation release

No code changes since v0.5.0. Purpose is to exercise the tag
pipeline end-to-end with the four .gitlab-ci.yml changes that
landed between v0.5.0 and now: binstall for cargo-audit /
cargo-deb / cargo-generate-rpm, rust:slim base image, and
pull-only cache policy on test/clippy.

Main-branch pipeline validated on 4e0a7d3 (pipeline
release stages for the first time under the new configuration.

  • v0.5.0

    38551e1f · release: bump version 0.4.3 → 0.5.0 for v0.5.0 tag ·
    Release: v0.5.0 
    v0.5.0: rumqttc → rumqttc-v4-next fork (temporary bridge)

Clears five RustSec advisories (RUSTSEC-2026-0099 / 0049 / 0098 /
0104, RUSTSEC-2025-0134) against rumqttc 0.25.1's rustls-webpki /
rustls-pemfile pins. Migration framed explicitly as a temporary
bridge pending upstream rumqttc resumption (bytebeamio/rumqtt#1029);
see docs/decisions.md entry dated 2026-04-24 for the full context.

Opportunistic: enables rustls ring backend via the fork's
use-rustls-ring feature, sheds aws_lc_sys. Stripped release binary
6.52 MiB → 4.56 MiB (-30.1%).

  • v0.4.3

    cfa635a6 · ci: publish GitLab Release on tag push; park native Package Registry work ·
    Release: v0.4.3 
    v0.4.3 — CI publishes GitLab Release with .deb + .rpm attached on
tag push. Native apt/dnf install via Package Registry parked upstream
(Debian Experiment, RPM not GA on gitlab.com). No wire or contract
changes. Patch bumped from 0.4.2 rather than repeated because the
prior 0.4.2 artifact existed only as a locally-built test package,
and install-state on the test host is unverified.