Releases
Where Bud releases are published, and what changed in each released version.
Full release notes are on each product’s GitHub releases:
How releases are published
Section titled “How releases are published”- Bud is published as a container image at
ghcr.io/mbedlabs/bud. Each released version has an immutable version tag, such as1.2.0. Thestabletag follows tested non-prerelease version tags, independently of GitHub Releases. Pin a full version for production. See Images and versions. - bud-runner and budtestlibrary are published on PyPI: bud-runner and budtestlibrary.
Read the upgrade notes in each release before upgrading. See Upgrade.
Recent versions
Section titled “Recent versions”Bloom imports test cases from TestRail, CSV, XML, and Markdown, and exports test cases and the traceability matrix. Controlled documents go through review and approval, access is given per project through groups of policies, and Jira issues can become Bloom defects.
Bud adds groups and policies, run notifications to Microsoft Teams, Slack, Discord, or any JSON endpoint, and keeps Robot Framework reports with the run. Both apps add an audit log, optional S3-compatible storage, and report requests between Bloom and Bud.
bud-runner reports Robot Framework, pytest, and Behave runs and imports Cucumber JSON; budtestlibrary adds step attachments and async and parameterized steps.
Cloudron packaging and first-run setup, inline artefact tags in documents, campaign and suite topology, Jira alongside GitHub and GitLab, a paginated traceability matrix, and faster screens.
Initial public release of Bud TMP and Bloom PLM: self-hosted container images with a PostgreSQL-backed deployment.