chore(release-py): bring hugr-py-v0.14.4 updates to main (#2719)

Modelled on #2708 (for 0.14.3) but this time including
`.release-please-manifest.json`...oooh, should I? Will that confuse
release-please when we do make a (breaking) release actually from `main`
??

---------

Co-authored-by: hugrbot <[email protected]>
Co-authored-by: Seyon Sivarajah <[email protected]>
Co-authored-by: Agustín Borgna <[email protected]>

Author: 4 people

hugr-py/CHANGELOG.md

@@ -1,5 +1,12 @@
 # Changelog
 
+## [0.14.4](https://github.com/CQCL/hugr/compare/hugr-py-v0.14.3...hugr-py-v0.14.4) (2025-11-26)
+
+
+### Bug Fixes
+
+* set hugr field of `PassResult` correctly ([#2715](https://github.com/CQCL/hugr/issues/2715)) ([4abedab](https://github.com/CQCL/hugr/commit/4abedabfd9015e79cfbe84ca2d369ec2175f9492))
+
 ## [0.14.3](https://github.com/CQCL/hugr/compare/hugr-py-v0.14.2...hugr-py-v0.14.3) (2025-11-24)
 
 

hugr-py/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "hugr"
-version = "0.14.3"
+version = "0.14.4"
 requires-python = ">=3.10"
 description = "Quantinuum's common representation for quantum programs"
 license = { file = "LICENCE" }

hugr-py/src/hugr/__init__.py

@@ -18,4 +18,4 @@
 
 # This is updated by our release-please workflow, triggered by this
 # annotation: x-release-please-version
-__version__ = "0.14.3"
+__version__ = "0.14.4"