Skip to main content
Version: 0.1.0

Version 0.1.2

Released: September 12, 2026

PADAS 0.1.2 is a focused reliability release that improves Kafka authentication compatibility and makes Motion package builds safer across tagged releases. The release includes two completed issues.

Highlights

  • Kafka authentication compatibility: SASL mechanism values are normalized before they are passed to librdkafka.
  • Safer Motion packaging: sibling components now default to the same workflow ref as the package being built.

Issue summary

IssueTypePriorityStatusSummary
PADAS-864BugMediumDoneKafka connector: normalize sasl.mechanism casing for librdkafka (SCRAM-SHA-512)
PADAS-865TaskMediumDoneMotion package build: default sibling_ref to workflow ref, not sibling main

What changed

Kafka SASL mechanism handling

PADAS-864 fixes Kafka source and sink connector startup failures caused by lowercase or mixed-case sasl.mechanism values. The core Kafka configuration path now normalizes supported aliases before creating the librdkafka client.

Accepted aliasCanonical librdkafka valueUse case
plainPLAINPLAIN authentication
scram-sha-256SCRAM-SHA-256SCRAM-SHA-256 authentication
scram-sha-512SCRAM-SHA-512SCRAM-SHA-512 authentication

This allows configurations such as scram-sha-512 with sasl_ssl to start successfully without requiring operators to override the value manually. Unknown mechanisms continue to fail with a clear configuration error, and unit tests cover alias-to-canonical mapping.

Operational impact: Existing UI and configuration values can remain lowercase. Core performs the compatibility normalization before values reach librdkafka.

Motion package version consistency

PADAS-865 updates the Motion package workflow so an empty sibling_ref defaults to the same Git ref used for the workflow run.

  • Running the workflow from a release tag now checks out sibling components from that same tag.
  • Explicit sibling_ref values still override the default when required.
  • Scheduled builds on main continue to use main siblings.
  • PR behavior in ci.yml remains unchanged.

This prevents version mismatches such as a tagged Motion package containing sibling components from the default branch. Packaging documentation and tests were updated to verify the fallback behavior.

Upgrade notes

  • Upgrade the PADAS components included in the 0.1.2 release.
  • Review Kafka connector authentication settings. Lowercase values such as scram-sha-512, scram-sha-256, and plain are now normalized automatically.
  • When building Motion packages from a tag, leave sibling_ref empty to use the matching tag for sibling components, or provide an explicit ref when intentionally building a mixed-ref package.

Release scope

All issues assigned to fix version 0.1.2 were completed. No unresolved issues remained in the release filter at publication time.

References

  • PADAS-864: Kafka connector — normalize sasl.mechanism casing for librdkafka (SCRAM-SHA-512)
  • PADAS-865: Motion package build — default sibling_ref to workflow ref (not sibling main)

← All releases