opsmill · ogenstad · Mar 17, 2026 · Jan 9, 2026 · Jan 21, 2026 · Jan 22, 2026
diff --git a/.vale/styles/Infrahub/sentence-case.yml b/.vale/styles/Infrahub/sentence-case.yml
@@ -52,6 +52,7 @@ exceptions:
   - Jinja
   - Jinja2
   - JWT
+  - MDX
   - Namespace
   - NATS
   - Node

diff --git a/.vale/styles/spelling-exceptions.txt b/.vale/styles/spelling-exceptions.txt
@@ -79,6 +79,7 @@ kbps
 Keycloak
 Loopbacks
 markdownlint
+MDX
 max_count
 memgraph
 menu_placement

diff --git a/CHANGELOG.md b/CHANGELOG.md
@@ -10,6 +10,24 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
 This project uses [*towncrier*](https://towncrier.readthedocs.io/) and the changes for the upcoming release can be found in <https://github.com/opsmill/infrahub/tree/develop/infrahub/python_sdk/changelog/>.
 
 <!-- towncrier release notes start -->
+
+## [1.19.0](https://github.com/opsmill/infrahub-sdk-python/tree/v1.19.0) - 2026-03-16
+
+### Added
+
+- Added support for FileObject nodes with file upload and download capabilities. New methods `upload_from_path(path)` and `upload_from_bytes(content, name)` allow setting file content before saving, while `download_file(dest)` enables downloading files to memory or streaming to disk for large files. ([#ihs193](https://github.com/opsmill/infrahub-sdk-python/issues/ihs193))
+- Python SDK API documentation is now generated directly from the docstrings of the classes, functions, and methods contained in the code. ([#201](https://github.com/opsmill/infrahub-sdk-python/issues/201))
+- Added a 'py.typed' file to the project. This is to enable type checking when the Infrahub SDK is imported from other projects. The addition of this file could cause new typing issues in external projects until all typing issues have been resolved. Adding it to the project now to better highlight remaining issues.
+
+### Changed
+
+- Updated branch report command to use node metadata for proposed change creator information instead of the deprecated relationship-based approach. Requires Infrahub 1.7 or above.
+
+### Fixed
+
+- Allow SDK tracking feature to continue after encountering delete errors due to impacted nodes having already been deleted by cascade delete. ([#265](https://github.com/opsmill/infrahub-sdk-python/issues/265))
+- Fixed Python SDK query generation regarding from_pool generated attribute value ([#497](https://github.com/opsmill/infrahub-sdk-python/issues/497))
+
 ## [1.18.1](https://github.com/opsmill/infrahub-sdk-python/tree/v1.18.1) - 2026-01-08
 
 ### Fixed

diff --git a/changelog/151.added.md b/changelog/151.added.md
@@ -0,0 +1 @@
+Add `infrahubctl schema export` command to export schemas from Infrahub.
diff --git a/changelog/201.added.md b/changelog/201.added.md
diff --git a/changelog/265.fixed.md b/changelog/265.fixed.md
diff --git a/changelog/497.fixed.md b/changelog/497.fixed.md
diff --git a/docs/AGENTS.md b/docs/AGENTS.md
@@ -1,4 +1,4 @@
-# docs/AGENTS.md
+# Documentation agents
 
 Docusaurus documentation following Diataxis framework.
 
@@ -34,12 +34,12 @@ Sidebar navigation is dynamic: `sidebars-*.ts` files read the filesystem at buil
 
 No manual sidebar update is needed when adding a new `.mdx` file. However, to control the display order of a new page, add its doc ID to the ordered list in the corresponding `sidebars-*.ts` file.
 
-## Adding Documentation
+## Adding documentation
 
 1. Create MDX file in appropriate directory
 2. Add frontmatter with `title`
 
-## MDX Pattern
+## MDX pattern
 
 Use Tabs for async/sync examples, callouts for notes:
 

diff --git a/docs/docs/infrahubctl/infrahubctl-schema.mdx b/docs/docs/infrahubctl/infrahubctl-schema.mdx
@@ -17,6 +17,7 @@ $ infrahubctl schema [OPTIONS] COMMAND [ARGS]...
 **Commands**:
 
 * `check`: Check if schema files are valid and what...
+* `export`: Export the schema from Infrahub as YAML...
 * `load`: Load one or multiple schema files into...
 
 ## `infrahubctl schema check`
@@ -40,6 +41,25 @@ $ infrahubctl schema check [OPTIONS] SCHEMAS...
 * `--config-file TEXT`: [env var: INFRAHUBCTL_CONFIG; default: infrahubctl.toml]
 * `--help`: Show this message and exit.
 
+## `infrahubctl schema export`
+
+Export the schema from Infrahub as YAML files, one per namespace.
+
+**Usage**:
+
+```console
+$ infrahubctl schema export [OPTIONS]
+```
+
+**Options**:
+
+* `--directory PATH`: Directory path to store schema files  [default: (dynamic)]
+* `--branch TEXT`: Branch from which to export the schema
+* `--namespaces TEXT`: Namespace(s) to export (default: all user-defined)
+* `--debug / --no-debug`: [default: no-debug]
+* `--config-file TEXT`: [env var: INFRAHUBCTL_CONFIG; default: infrahubctl.toml]
+* `--help`: Show this message and exit.
+
 ## `infrahubctl schema load`
 
 Load one or multiple schema files into Infrahub.

diff --git a/docs/docs/python-sdk/guides/client.mdx b/docs/docs/python-sdk/guides/client.mdx
@@ -251,7 +251,7 @@ Your client is now configured to use the specified default branch instead of `ma
 
 ## Hello world example
 
-Let's create a simple "Hello World" example to verify your client configuration works correctly. This example will connect to your Infrahub instance and query the available accounts.
+Let's create a "Hello World" example to verify your client configuration works correctly. This example will connect to your Infrahub instance and query the available accounts.
 
 1. Create a new file called `hello_world.py`:
 

diff --git a/docs/docs/python-sdk/guides/python-typing.mdx b/docs/docs/python-sdk/guides/python-typing.mdx
@@ -131,7 +131,7 @@ infrahubctl graphql generate-return-types queries/get_tags.gql
 
 ### Example workflow
 
-1. **Create your GraphQL queries** in `.gql` files preferably in a directory (e.g., `queries/`):
+1. **Create your GraphQL queries** in `.gql` files preferably in a directory (for example, `queries/`):
 
    ```graphql
    # queries/get_tags.gql

diff --git a/docs/docs/python-sdk/sdk_ref/infrahub_sdk/node/node.mdx b/docs/docs/python-sdk/sdk_ref/infrahub_sdk/node/node.mdx
@@ -37,6 +37,44 @@ artifact_generate(self, name: str) -> None
 artifact_fetch(self, name: str) -> str | dict[str, Any]
 ```
 
+#### `download_file`
+
+```python
+download_file(self, dest: Path | None = None) -> bytes | int
+```
+
+Download the file content from this FileObject node.
+
+This method is only available for nodes that inherit from CoreFileObject.
+The node must have been saved (have an id) before calling this method.
+
+**Args:**
+
+- `dest`: Optional destination path. If provided, the file will be streamed
+  directly to this path (memory-efficient for large files) and the
+  number of bytes written will be returned. If not provided, the
+  file content will be returned as bytes.
+
+**Returns:**
+
+- If ``dest`` is None: The file content as bytes.
+- If ``dest`` is provided: The number of bytes written to the file.
+
+**Raises:**
+
+- `FeatureNotSupportedError`: If this node doesn't inherit from CoreFileObject.
+- `ValueError`: If the node hasn't been saved yet or file not found.
+- `AuthenticationError`: If authentication fails.
+
+**Examples:**
+
+```python
+>>> # Download to memory
+>>> content = await contract.download_file()
+>>> # Stream to file (memory-efficient for large files)
+>>> bytes_written = await contract.download_file(dest=Path("/tmp/contract.pdf"))
+```
+
 #### `delete`
 
 ```python
@@ -180,6 +218,44 @@ artifact_generate(self, name: str) -> None
 artifact_fetch(self, name: str) -> str | dict[str, Any]
 ```
 
+#### `download_file`
+
+```python
+download_file(self, dest: Path | None = None) -> bytes | int
+```
+
+Download the file content from this FileObject node.
+
+This method is only available for nodes that inherit from CoreFileObject.
+The node must have been saved (have an id) before calling this method.
+
+**Args:**
+
+- `dest`: Optional destination path. If provided, the file will be streamed
+  directly to this path (memory-efficient for large files) and the
+  number of bytes written will be returned. If not provided, the
+  file content will be returned as bytes.
+
+**Returns:**
+
+- If ``dest`` is None: The file content as bytes.
+- If ``dest`` is provided: The number of bytes written to the file.
+
+**Raises:**
+
+- `FeatureNotSupportedError`: If this node doesn't inherit from CoreFileObject.
+- `ValueError`: If the node hasn't been saved yet or file not found.
+- `AuthenticationError`: If authentication fails.
+
+**Examples:**
+
+```python
+>>> # Download to memory
+>>> content = contract.download_file()
+>>> # Stream to file (memory-efficient for large files)
+>>> bytes_written = contract.download_file(dest=Path("/tmp/contract.pdf"))
+```
+
 #### `delete`
 
 ```python
@@ -373,6 +449,70 @@ is_ip_address(self) -> bool
 is_resource_pool(self) -> bool
 ```
 
+#### `is_file_object`
+
+```python
+is_file_object(self) -> bool
+```
+
+Check if this node inherits from CoreFileObject and supports file uploads.
+
+#### `upload_from_path`
+
+```python
+upload_from_path(self, path: Path) -> None
+```
+
+Set a file from disk to be uploaded when saving this FileObject node.
+
+The file will be streamed during upload, avoiding loading the entire file into memory.
+
+**Args:**
+
+- `path`: Path to the file on disk.
+
+**Raises:**
+
+- `FeatureNotSupportedError`: If this node doesn't inherit from CoreFileObject.
+
+#### `upload_from_bytes`
+
+```python
+upload_from_bytes(self, content: bytes | BinaryIO, name: str) -> None
+```
+
+Set content to be uploaded when saving this FileObject node.
+
+The content can be provided as bytes or a file-like object.
+Using BinaryIO is recommended for large content to stream during upload.
+
+**Args:**
+
+- `content`: The file content as bytes or a file-like object.
+- `name`: The filename to use for the uploaded file.
+
+**Raises:**
+
+- `FeatureNotSupportedError`: If this node doesn't inherit from CoreFileObject.
+
+**Examples:**
+
+```python
+>>> # Using bytes (for small files)
+>>> node.upload_from_bytes(content=b"file content", name="example.txt")
+>>> # Using file-like object (for large files)
+>>> with open("/path/to/file.bin", "rb") as f:
+...     node.upload_from_bytes(content=f, name="file.bin")
+```
+
+#### `clear_file`
+
+```python
+clear_file(self) -> None
+```
+
+Clear any pending file content.
+
 #### `get_raw_graphql_data`
 
 ```python

diff --git a/docs/docs/python-sdk/topics/object_file.mdx b/docs/docs/python-sdk/topics/object_file.mdx
@@ -68,13 +68,13 @@ spec:
 
 > Multiple documents in a single YAML file are also supported, each document will be loaded separately. Documents are separated by `---`
 
-### Data Processing Parameters
+### Data processing parameters
 
 The `parameters` field controls how the data in the object file is processed before loading into Infrahub:
 
-| Parameter      | Description                                                                                             | Default |
-| -------------- | ------------------------------------------------------------------------------------------------------- | ------- |
-| `expand_range` | When set to `true`, range patterns (e.g., `[1-5]`) in string fields are expanded into multiple objects. | `false` |
+| Parameter      | Description                                                                                                    | Default |
+| -------------- | -------------------------------------------------------------------------------------------------------------- | ------- |
+| `expand_range` | When set to `true`, range patterns (for example, `[1-5]`) in string fields are expanded into multiple objects. | `false` |
 
 When `expand_range` is not specified, it defaults to `false`.
 
@@ -208,9 +208,9 @@ Metadata support is planned for future releases. Currently, the Object file does
 3. Validate object files before loading them into production environments.
 4. Use comments in your YAML files to document complex relationships or dependencies.
 
-## Range Expansion in Object Files
+## Range expansion in object files
 
-The Infrahub Python SDK supports **range expansion** for string fields in object files when the `parameters > expand_range` is set to `true`. This feature allows you to specify a range pattern (e.g., `[1-5]`) in any string value, and the SDK will automatically expand it into multiple objects during validation and processing.
+The Infrahub Python SDK supports **range expansion** for string fields in object files when the `parameters > expand_range` is set to `true`. This feature allows you to specify a range pattern (for example, `[1-5]`) in any string value, and the SDK will automatically expand it into multiple objects during validation and processing.
 
 ```yaml
 ---
@@ -225,15 +225,15 @@ spec:
       type: Country
 ```
 
-### How Range Expansion Works
+### How range expansion works
 
 - Any string field containing a pattern like `[1-5]`, `[10-15]`, or `[1,3,5]` will be expanded into multiple objects.
 - If multiple fields in the same object use range expansion, **all expanded lists must have the same length**. If not, validation will fail.
 - The expansion is performed before validation and processing, so all downstream logic works on the expanded data.
 
 ### Examples
 
-#### Single Field Expansion
+#### Single field expansion
 
 ```yaml
 spec:
@@ -256,7 +256,7 @@ This will expand to:
   type: Country
 ```
 
-#### Multiple Field Expansion (Matching Lengths)
+#### Multiple field expansion (matching lengths)
 
 ```yaml
 spec:
@@ -283,7 +283,7 @@ This will expand to:
   type: Country
 ```
 
-#### Error: Mismatched Range Lengths
+#### Error: mismatched range lengths
 
 If you use ranges of different lengths in multiple fields:
 

diff --git a/docs/docs_generation/content_gen_methods/mdx/mdx_collapsed_overload_code_doc.py b/docs/docs_generation/content_gen_methods/mdx/mdx_collapsed_overload_code_doc.py
@@ -44,7 +44,7 @@ def _collapse_overloads(self, mdx_file: MdxFile) -> MdxFile:
                 h3_parsed = _parse_sections(h2.content, heading_level=3)
                 new_lines = h3_parsed.reassembled(processed_h3)
                 processed_h2.append(
-                    MdxSection(name=h2.name, heading_level=h2.heading_level, _lines=[h2.heading] + new_lines)
+                    MdxSection(name=h2.name, heading_level=h2.heading_level, _lines=[h2.heading, *new_lines])
                 )
 
         new_content = "\n".join(parsed_h2.reassembled(processed_h2))
@@ -67,7 +67,7 @@ def _process_class_sections(self, h2_content: list[str]) -> list[ASection] | Non
                 h4_parsed = _parse_sections(h3.content, heading_level=4)
                 new_lines = h4_parsed.reassembled(collapsed_methods)
                 processed.append(
-                    MdxSection(name=h3.name, heading_level=h3.heading_level, _lines=[h3.heading] + new_lines)
+                    MdxSection(name=h3.name, heading_level=h3.heading_level, _lines=[h3.heading, *new_lines])
                 )
 
         return processed if any_collapsed else None

diff --git a/docs/docs_generation/content_gen_methods/mdx/mdx_section.py b/docs/docs_generation/content_gen_methods/mdx/mdx_section.py
@@ -19,7 +19,7 @@ def content(self) -> list[str]: ...
 
     @property
     def lines(self) -> list[str]:
-        return [self.heading] + self.content
+        return [self.heading, *self.content]
 
 
 @dataclass

@@ -19,6 +19,7 @@ class BranchStatus(str, Enum):
     NEED_REBASE = "NEED_REBASE"
     NEED_UPGRADE_REBASE = "NEED_UPGRADE_REBASE"
     DELETING = "DELETING"
+    MERGED = "MERGED"
 
 
 class BranchData(BaseModel):
-Original file line number
+Diff line change
@@ Expand Up / @@ -52,6 +52,7 @@ exceptions: @@
       - Jinja
       - Jinja2
       - JWT
+      - MDX
       - Namespace
       - NATS
       - Node
@@ Expand Down @@
Original file line number	Diff line number	Diff line change
		@@ -0,0 +1 @@
		Add `infrahubctl schema export` command to export schemas from Infrahub.