Merge main into feature/querybuilder-clean

Resolve README.md conflict: combine context manager row with
QueryBuilder namespace description.

Author: tpellissier

.claude/skills/dataverse-sdk-use/SKILL.md

@@ -53,7 +53,13 @@ credential = AzureCliCredential()
 credential = ClientSecretCredential(tenant_id, client_id, client_secret)
 credential = CertificateCredential(tenant_id, client_id, cert_path)
 
-# Create client (no trailing slash on URL!)
+# Create client with context manager (recommended -- enables HTTP connection pooling)
+# No trailing slash on URL!
+with DataverseClient("https://yourorg.crm.dynamics.com", credential) as client:
+    ...  # all operations here
+# Session closed, caches cleared automatically
+
+# Or without context manager:
 client = DataverseClient("https://yourorg.crm.dynamics.com", credential)
 ```
 
@@ -232,7 +238,7 @@ client.tables.delete("new_Product")
 
 #### Create One-to-Many Relationship
 ```python
-from PowerPlatform.Dataverse.models.metadata import (
+from PowerPlatform.Dataverse.models.relationship import (
     LookupAttributeMetadata,
     OneToManyRelationshipMetadata,
     Label,
@@ -264,7 +270,7 @@ print(f"Created lookup field: {result['lookup_schema_name']}")
 
 #### Create Many-to-Many Relationship
 ```python
-from PowerPlatform.Dataverse.models.metadata import ManyToManyRelationshipMetadata
+from PowerPlatform.Dataverse.models.relationship import ManyToManyRelationshipMetadata
 
 relationship = ManyToManyRelationshipMetadata(
     schema_name="new_employee_project",

.github/workflows/ado-pipeline-yaml-pr-warning.yml

@@ -0,0 +1,55 @@
+name: Warn when ADO pipeline YAML file changes
+
+on:
+  pull_request:
+    paths:
+      - ".azdo/ci-pr.yaml"
+
+permissions:
+  contents: read
+  pull-requests: write
+
+jobs:
+  warn:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Emit warning in logs
+        run: |
+          echo "::warning file=.azdo/ci-pr.yaml::This PR changes .azdo/ci-pr.yaml. After merge, Azure DevOps may disable/require approval for the PR pipeline YAML until it is re-enabled/approved."
+
+          echo "ADO pipeline: DV-Python-SDK-PullRequest (definitionId=29922)"
+          echo "https://dev.azure.com/dynamicscrm/OneCRM/_build?definitionId=29922"
+
+      - name: Add workflow summary
+        run: |
+          {
+            echo "## ADO PR pipeline YAML change detected"
+            echo ""
+            echo "**File changed:** \`.azdo/ci-pr.yaml\`"
+            echo ""
+            echo "**Why this matters:** After this is merged, Azure DevOps may disable/require approval for the PR pipeline YAML."
+            echo ""
+            echo "**Action required (post-merge):** Re-enable / approve the updated YAML for:"
+            echo "- **DV-Python-SDK-PullRequest** (definitionId=29922)"
+            echo "- https://dev.azure.com/dynamicscrm/OneCRM/_build?definitionId=29922"
+            echo ""
+            echo "Then trigger a run to confirm PR validation works."
+          } >> "$GITHUB_STEP_SUMMARY"
+
+      - name: Post resolvable PR review comment
+        env:
+          GH_TOKEN: ${{ github.token }}
+        run: |
+          jq -n \
+            --arg sha "${{ github.event.pull_request.head.sha }}" \
+            '{
+              path: ".azdo/ci-pr.yaml",
+              subject_type: "file",
+              commit_id: $sha,
+              body: "> [!WARNING]\n> **ADO PR pipeline YAML change detected**\n>\n> This PR modifies `.azdo/ci-pr.yaml`. After merge, Azure DevOps may disable or require approval for the PR validation pipeline.\n>\n> **Action required (post-merge):** Re-enable / approve the updated YAML for:\n> - **DV-Python-SDK-PullRequest** (definitionId=29922)\n> - https://dev.azure.com/dynamicscrm/OneCRM/_build?definitionId=29922\n>\n> Please resolve this comment after completing the post-merge steps."
+            }' | \
+          gh api \
+            --method POST \
+            -H "Accept: application/vnd.github+json" \
+            /repos/${{ github.repository }}/pulls/${{ github.event.pull_request.number }}/comments \
+            --input -

CHANGELOG.md

@@ -5,6 +5,57 @@ All notable changes to this project will be documented in this file.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [0.1.0b5] - 2026-02-27
+
+### Fixed
+- UpsertMultiple: exclude alternate key fields from request body (#127). The create path of UpsertMultiple failed with `400 Bad Request` when alternate key column values appeared in both the body and `@odata.id`.
+
+## [0.1.0b4] - 2026-02-25
+
+### Added
+- Operation namespaces: `client.records`, `client.query`, `client.tables`, `client.files` (#102)
+- Relationship management: `create_one_to_many_relationship`, `create_many_to_many_relationship`, `get_relationship`, `delete_relationship`, `create_lookup_field` with typed `RelationshipInfo` return model (#105, #114)
+- `client.records.upsert()` for upsert operations with alternate key support (#106)
+- `client.files.upload()` for file upload operations (#111)
+- `client.tables.list(filter=, select=)` parameters for filtering and projecting table metadata (#112)
+- Cascade behavior constants (`CASCADE_BEHAVIOR_CASCADE`, `CASCADE_BEHAVIOR_REMOVE_LINK`, etc.) and input models (`CascadeConfiguration`, `LookupAttributeMetadata`, `Label`, `LocalizedLabel`)
+
+### Deprecated
+- All flat methods on `DataverseClient` (`create`, `update`, `delete`, `get`, `query_sql`, `upload_file`, etc.) now emit `DeprecationWarning` and delegate to the corresponding namespaced operations
+
+## [0.1.0b3] - 2025-12-19
+
+### Added
+- Client-side correlation ID and client request ID for request tracing (#70)
+- Unit tests for `DataverseClient` (#71)
+
+### Changed
+- Standardized package versioning (#84)
+- Updated package link (#69)
+
+### Fixed
+- Retry logic for examples (#72)
+- Removed double space formatting issue (#82)
+- Updated CI trigger to include main branch (#81)
+
+## [0.1.0b2] - 2025-11-17
+
+### Added
+- Enforce Black formatting across the codebase (#61, #62)
+- Python 3.14 support added to `pyproject.toml` (#55)
+
+### Changed
+- Removed `pandas` dependency (#57)
+- Refactored SDK architecture and quality improvements (#55)
+- Prefixed table names with schema name for consistency (#51)
+- Updated docstrings across core modules (#54, #63)
+
+### Fixed
+- Fixed `get` for single-select option set columns (#52)
+- Fixed example filename references and documentation URLs (#60)
+- Fixed API documentation link in examples (#64)
+- Fixed CI pipeline to use modern `pyproject.toml` dev dependencies (#56, #59)
+
 ## [0.1.0b1] - 2025-11-14
 
 ### Added
@@ -19,6 +70,8 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 - Comprehensive error handling with specific exception types (`DataverseError`, `AuthenticationError`, etc.) (#22, #24)
 - HTTP retry logic with exponential backoff for resilient operations (#72)
 
+[0.1.0b5]: https://github.com/microsoft/PowerPlatform-DataverseClient-Python/compare/v0.1.0b4...v0.1.0b5
+[0.1.0b4]: https://github.com/microsoft/PowerPlatform-DataverseClient-Python/compare/v0.1.0b3...v0.1.0b4
 [0.1.0b3]: https://github.com/microsoft/PowerPlatform-DataverseClient-Python/compare/v0.1.0b2...v0.1.0b3
 [0.1.0b2]: https://github.com/microsoft/PowerPlatform-DataverseClient-Python/compare/v0.1.0b1...v0.1.0b2
 [0.1.0b1]: https://github.com/microsoft/PowerPlatform-DataverseClient-Python/releases/tag/v0.1.0b1

CONTRIBUTING.md

@@ -109,4 +109,16 @@ Brief summary of the release
 ### Fixed
 - Bug fix 1 (#125)
 - Bug fix 2 (#126)
+```
+
+**Post-Release Version Bump:**
+
+After tagging and publishing a release, immediately bump the version on `main` to the next
+development target. This ensures builds from source are clearly distinguished from the
+published release:
+
+```bash
+# After publishing v0.1.0b4, bump to v0.1.0b5 on main
+# Update version in pyproject.toml
+# Commit directly to main: "Bump version to 0.1.0b5 for next development cycle"
 ```

README.md

@@ -114,6 +114,7 @@ The SDK provides a simple, pythonic interface for Dataverse operations:
 | Concept | Description |
 |---------|-------------|
 | **DataverseClient** | Main entry point; provides `records`, `query`, `tables`, and `files` namespaces |
+| **Context Manager** | Use `with DataverseClient(...) as client:` for automatic cleanup and HTTP connection pooling |
 | **Namespaces** | Operations are organized into `client.records` (CRUD), `client.query` (QueryBuilder & SQL), `client.tables` (metadata), and `client.files` (file uploads) |
 | **Records** | Dataverse records represented as Python dictionaries with column schema names |
 | **Schema names** | Use table schema names (`"account"`, `"new_MyTestTable"`) and column schema names (`"name"`, `"new_MyTestColumn"`). See: [Table definitions in Microsoft Dataverse](https://learn.microsoft.com/en-us/power-apps/developer/data-platform/entity-metadata) |
@@ -132,17 +133,18 @@ from PowerPlatform.Dataverse.client import DataverseClient
 
 # Connect to Dataverse
 credential = InteractiveBrowserCredential()
-client = DataverseClient("https://yourorg.crm.dynamics.com", credential)
 
-# Create a contact
-contact_id = client.records.create("contact", {"firstname": "John", "lastname": "Doe"})
+with DataverseClient("https://yourorg.crm.dynamics.com", credential) as client:
+    # Create a contact
+    contact_id = client.records.create("contact", {"firstname": "John", "lastname": "Doe"})
 
-# Read the contact back
-contact = client.records.get("contact", contact_id, select=["firstname", "lastname"])
-print(f"Created: {contact['firstname']} {contact['lastname']}")
+    # Read the contact back
+    contact = client.records.get("contact", contact_id, select=["firstname", "lastname"])
+    print(f"Created: {contact['firstname']} {contact['lastname']}")
 
-# Clean up
-client.records.delete("contact", contact_id)
+    # Clean up
+    client.records.delete("contact", contact_id)
+# Session closed, caches cleared automatically
 ```
 
 ### Basic CRUD operations
@@ -359,13 +361,12 @@ client.tables.delete("new_Product")
 Create relationships between tables using the relationship API. For a complete working example, see [examples/advanced/relationships.py](https://github.com/microsoft/PowerPlatform-DataverseClient-Python/blob/main/examples/advanced/relationships.py).
 
 ```python
-from PowerPlatform.Dataverse.models.metadata import (
+from PowerPlatform.Dataverse.models.relationship import (
     LookupAttributeMetadata,
     OneToManyRelationshipMetadata,
     ManyToManyRelationshipMetadata,
-    Label,
-    LocalizedLabel,
 )
+from PowerPlatform.Dataverse.models.labels import Label, LocalizedLabel
 
 # Create a one-to-many relationship: Department (1) -> Employee (N)
 # This adds a "Department" lookup field to the Employee table