microsoft / microsoft/AzureTRE

Prep for Release v0.29.1

Open
#5,084 0 comments 0 reactions 1 assignee View on GitHub

@JayDoubleu is already working on this.

Since Sep 18, 2026.

release
Dominant language
Python
Stars
235
Forks
192
Avg merge
1d 23h
Merged PRs (30d)
13

Description

Prepare AzureTRE v0.29.1 as a maintenance release covering the 18 merged PRs since v0.29.0, reviewed through b57b6af0f4026b337211c0ace029fc27b79d58d5.

The release includes security and dependency patches, Service Bus connection fixes, workspace navigation fixes, DNS allowlist corrections, GitHub automation improvements, and the case-study correction in #5072. The corrected case studies are published under unreleased; the website's latest version still points to v0.29.0.

Release checklist

  • Review the changes since v0.29.0 and propose the v0.29.1 patch version.
  • Prepare the changelog, link all 18 merged PRs, and verify the component inventory.
  • Review and merge the release preparation PR.
  • Validate the selected release commit with builds, unit tests, deployment, upgrade and relevant end-to-end checks.
  • Publish the v0.29.1 pre-release with the release notes.
  • Verify Deploy Documentation succeeds and the corrected case studies appear under latest.
  • Update AzureTRE-Deployment to v0.29.1, align .github and .devcontainer, rebuild and test.
  • Promote v0.29.1 to the latest stable release after validation.

Publication and validation notes

The Deploy Azure TRE workflow is currently manually disabled. The merged PR checks do not replace fresh validation of the selected release commit.

The current documentation workflow listens to release.published. Publishing a pre-release updates the documentation's latest alias immediately. Decide whether to retain this behaviour before publication. Existing archived documentation versions retain their previous content.

No release date is assigned in the preparation PR. Confirm it when the release is published.

References: release procedure, documentation workflow.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.