build: upload python wheels for 3.2.*

.agents/skills/prepare-patch-release/SKILL.md

@@ -30,6 +30,8 @@ with a "v" prepended, for example, `v3.1.4.0`.
 - [ ] Review @INSTALL.md for changes.
 - [ ] Review @CREDITS.md for changes.
 - [ ] Review @SECURITY.md for changes.
+- [ ] For a release branch (not main, and not still alpha/beta/rc status),
+      check that wheel.yml's upload_pypi step will publish the branch.
 
 ## Steps to determine the versions of the last and new releases.
 

.github/workflows/wheel.yml

@@ -541,7 +541,7 @@ jobs:
     runs-on: ubuntu-latest
     permissions:
       id-token: write
-    if: github.event_name == 'push' && (startsWith(github.event.ref, 'refs/tags/v3.0.') || startsWith(github.event.ref, 'refs/tags/v3.1.')) && github.event.repository.fork == false
+    if: github.event_name == 'push' && (startsWith(github.event.ref, 'refs/tags/v3.2.') || startsWith(github.event.ref, 'refs/tags/v3.1.')) && github.event.repository.fork == false
     steps:
       - uses: actions/setup-python@5fda3b95a4ea91299a34e894583c3862153e4b97 # v7.0.0
 

CHANGES.md

@@ -69,6 +69,23 @@ Release 3.3 (anticipated Sep/Oct, 2027?) -- compared to 3.2.1.0
 
 
 
+
+Release 3.2.1.3 (Oct 15, 2026) -- compared to 3.2.1.2
+-----------------------------------------------------
+Another no-change release tag to force a Python 3.15 wheel publish.
+Sorry.
+
+
+Release 3.2.1.2 (Oct 14, 2026) -- compared to 3.2.1.1
+-----------------------------------------------------
+No code changes, this is just a new release tag to force a Python 3.15 wheel
+build.
+
+
+Release 3.2.1.1 (Oct 2, 2026) -- compared to 3.2.1.0
+----------------------------------------------------
+  - *fix(ImageInput/Output)*: Honor the data window origin in the `image_span` read/write methods. [#5531](https://github.com/AcademySoftwareFoundation/OpenImageIO/pull/5531)
+  - *fix(docs)*: Fix oiiotool man page generation errors with gawk. [#5528](https://github.com/AcademySoftwareFoundation/OpenImageIO/pull/5528)
 
 
 

docs/dev/RELEASING.md

@@ -43,7 +43,7 @@ years between them.
 
 Minor (API backward-compatible) releases are scheduled annually, targeted at
 late summer (SIGGRAPH time) to be in beta, and early autumn for a full
-release.
+release (aiming for no later than October).
 
 Patch (API and ABI backward-compatible) releases are scheduled monthly,
 usually aiming for the first day of each month.
@@ -131,7 +131,7 @@ project during this soft freeze.
 
 ### Branching for annual major/minor releases
 
-By mid-June (about 1-2 months before the beta of a new annual big release),
+By mid-July (about 1-2 months before the beta of a new annual big release),
 you should branch and mark it as an alpha.
 
 At the tip of "main", create a new branch named `dev-MAJOR.MINOR` that will
@@ -219,6 +219,11 @@ have a heading added at the top for the *next* version.
      developer previews.
    - The `${PROJECT_NAME}_SUPPORTED_RELEASE` variable should be `ON` for any
      release branch, `OFF` for main.
+   - For an annual release's first non-beta, non-rc tag (i.e., when it becomes
+     the new official supported release for the next year), be sure that the
+     wheel.yml workflow's "upload_pypi" job is set up to publish that version.
+     Decide also if there are old release branches that should no longer
+     publish to PyPI and remove those from the publish criteria.
 
 6. In the https://github.com/AcademySoftwareFoundation/OpenImageIO-images project, create a branch
    `dev-x.y` for the major/minor branch, and in the main oiio repo, update