From 152afa95a26f8a15fb5ad1a69b61cd63ebce6ed4 Mon Sep 17 00:00:00 2001 From: Jiani Wang Date: Wed, 20 Aug 2025 10:57:14 -0700 Subject: [PATCH 1/2] bump version --- assets/version.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/assets/version.txt b/assets/version.txt index 6e8bf73aa..17e51c385 100644 --- a/assets/version.txt +++ b/assets/version.txt @@ -1 +1 @@ -0.1.0 +0.1.1 From 373cddb754fa16d1e390573ba60a4a139ef6217c Mon Sep 17 00:00:00 2001 From: Jiani Wang Date: Wed, 20 Aug 2025 17:44:40 -0700 Subject: [PATCH 2/2] add docs --- docs/release.md | 1 + 1 file changed, 1 insertion(+) diff --git a/docs/release.md b/docs/release.md index 598734960..88d594f39 100644 --- a/docs/release.md +++ b/docs/release.md @@ -5,6 +5,7 @@ Currently we follow a lightweight release process. - if major features are added, increment `y` - if minor fixes are added, increment `z` - Create a new release at https://github.com/pytorch/torchtitan/releases/new + - In the tag section, add a new tag for the release. The tag should use the version number, with a `v` prefix (for example, `v0.1.0`). Make sure to select the `main` branch as the target. - In the release notes - include proper nightly versions for `torch` and `torchao`, which can be found in [latest CI](https://github.com/pytorch/torchtitan/actions/workflows/integration_test_8gpu.yaml) test log "Run script in container" section. E.g. - "Successfully installed ... `torch-2.8.0.dev20250605+cu126`"