Skip to main content

October 2026 maintenance release

The Power Platform Developer Suite (PPDS) maintenance release was published on October 30, 2026. The versions below were verified from their public distribution channels. See installation.

ProductPublished version
PPDS.Auth1.1.2
PPDS.Dataverse1.3.2
PPDS.Migration1.2.2
PPDS.Query1.0.2
PPDS.Plugins3.0.1
PPDS.Cli1.4.2
PPDS.Mcp1.2.2
PPDS Extension1.6.2
PPDS Skills0.1.2
PPDS.Tools1.1.0 stable, unchanged; 1.2.0-alpha3 prerelease
PPDS ALM1.0.1, also selected by v1

Each product retains its own version line. All eight core product tags point to 60dbd696d28c79447fe6490924a462c91f9b2d35; Skills, Tools, and ALM have their own reviewed repository commits. The Extension row refers to the maintained extension in the main PPDS repository. The retired standalone extension and Demo are outside this release.

Reference pages were regenerated by docs run 41159212988 from docs repair commit fc5c0e80edf2e8eec79cc36fc64167c8eaaed76e. That commit changes docs tooling, tests, and the docs specification, with no product runtime source change. The earlier run omitted CLI pages because its reflector used an incompatible runtime; the repair selects the compatible runtime and rejects incomplete generation. Generation provenance records this source-build evidence separately from the skills' public-package capture. Published product tags were not moved.

Metadata editing​

View and app correctness fixes already merged after the previous release are included: visible view columns and FetchXML projections stay aligned, related columns retain qualified identities, writes verify intended draft XML, app selections validate before mutation, and sitemap editing preserves localized labels.

The Timeline correction accepts UClientActivitiesConfigurationJSON without relaxing known parameter types or form structure. It does not promise arbitrary unknown control support. See the metadata editing guide.

Plugin packages and extraction​

Package identity validation checks the primary assembly, runtime plugin types, official attribute identities, and extraction evidence before upload. This includes concrete IPlugin types without PPDS registration attributes and does not synthesize steps for them. Post-upload failures provide inspection/retry guidance.

CLI 1.4.2 accepts lib/net48 plugin packages and qualifies the supported framework/signing requirements for loose DLLs. It repairs incomplete reference caches and protects new caches within the OS account's local application data. Legacy shared-temp caches are left untouched. See the plugin package guide.

Dependency servicing​

Auth and Dataverse pin PKCS 10.0.13 and XML cryptography 8.0.5. The RPC update resolves MessagePack 2.5.307. These fixes flow into downstream libraries, CLI, MCP, and the bundled Extension daemon. Already merged identity, Dataverse SDK, Microsoft.Extensions, and SourceLink updates are also included. Plugins 3.0.1 refreshes build/package inputs and its packed README; it adds no attributes and retains its strong-name identity and net462 target.

The Extension includes patched DOMPurify in notebook rendering, updates vscode-jsonrpc, and targets bundled CLI 1.4.2. Node modernization is deferred. See the cryptography servicing PR and RPC update.

PowerShell and ALM compatibility​

PPDS.Tools​

Tools #16 supplies 1.2.0-alpha3, repairing all 12 cmdlets in the prerelease CLI-wrapper API. Stable 1.1.0 retains its native implementation and is unchanged. The fixes redact supplied credentials in diagnostics, parse complete JSON and plugin envelopes, read migration progress from stderr, and propagate failures. They also preserve arguments, relative paths and interactive prompts, and terminate the owned CLI process when PowerShell cancels a call.

The original CLI 1.4.1 baseline passed 143 Pester tests. The actual published Gallery package was then downloaded, its 22 source files matched to release commit 8714e80148ae29b926c18a0a8531185e10c06944, and all 12 exports imported successfully. Three offline wrapper checks pass with installed public CLI 1.4.2: schema object/JSON output, plugin extraction without an output file, and relative output-file handling. Authentication, deployment and migration retain mocked boundaries; no live-service success is claimed. See the compatibility details. The CLI-wrapper API remains prerelease.

PPDS ALM​

ALM #35 supplies the 1.0.1 fixes. Plugin builds select the evaluated MSBuild TargetPath using the selected solution's context. Ambiguous builds require plugin-project or plugin-target-framework. Plugin workflows use current extraction, authentication, diff and deployment contracts; failed or invalid drift results stop deployment, while a valid drift exit code 1 remains successful. Cleanup removes only the temporary named profile.

The workflows keep the consumer checkout separate from their composite actions, fetched from job.workflow_repository at job.workflow_sha. These identity fields require GitHub.com; this patch does not support GitHub Enterprise Server. Real MSBuild selection, synthetic net462 extraction, and mocked workflow execution provide separate offline coverage.

Validation follow-up #36 corrects the authentication, diff and deploy evidence: both tested CLI versions return successful --help output even for nonexistent options. Tests now inspect actual advertised option declarations, value requirements and enum choices, with negative controls. This establishes advertised syntax, not runtime parsing or live behavior. The original 22 hosted tests passed with CLI 1.4.1. After publication, all 22 tests passed from the actual public ALM 1.0.1 archive with installed public CLI 1.4.2; all 57 tracked archive files matched release commit 5769e59b7833d85474ca8f4b410784360a7656dc. See the test scope.

The new v1.0.1 tag and supported v1 alias select this release. The existing v1.0.0 tag is preserved. Consumer projects pinned to older immutable tags or commits are not automatically retargeted.

Release verification​

Documentation and skills​

The AI agent installation guide covers Claude Code and GitHub Copilot CLI. Skills 0.1.2 was recaptured using the full manual capture flow from independently verified public CLI 1.4.2 and MCP 1.2.2 packages: 271 CLI command nodes and 41 MCP tool names and descriptions. Package source commits, signatures and hashes matched; only the raw source-commit version string changed from the reviewed simulation. Full MCP input schemas were checked separately from the capture script.

Public capture provenance is included in the core skill, so copying all seven skill folders retains it. Static validation rejects relative links outside that installed tree. Both required hosted static checks and the free harness self-test pass. The Linux workflows use Ubuntu 24.04 for Python 3.8 support; paid/live evaluations remain opt-in and were not run for this release.

Product artifacts​

Release workflows and independent downloads verified all seven public NuGet packages, five native CLI assets and checksums, and four Marketplace VSIX targets with bundled CLI 1.4.2. NuGet repository signatures, source commits, stable internal dependencies, assembly identities and SourceLink were checked. Plugins 3.0.1 retains its strong-name identity. Clean public installs/restores passed. Windows native and bundled CLIs each passed four offline extraction checks; a public native CLI also extracted a synthetic net48 package. The public Windows VSIX activated in isolated VS Code with 66 commands and no Dataverse operations. Local reference-cache checks used an existing cache; fresh-cache creation is covered by the release workflow.

Validation limits​

Core product NuGet and production npm audit checks had zero findings. The accepted limits remain: 23 development-tooling advisories are deferred; GitHub tracks 12 alerts covering 11 GHSAs and three test-only CodeQL notices. Unavailable companion GitHub scanning remains unknown rather than being treated as clean.

A separate audit of this documentation site's unchanged dependency lockfile reports 65 affected-package entries: eight low, 15 moderate, 24 high, and 18 critical. These documentation dependency findings are outside the core product audit counts and remain unresolved in this publication.

The earlier live net48 smoke used runtime 49f09af8; all six resources were cleaned up. It is separate from the new public-artifact offline checks. A live Timeline round-trip remains untested. The API rollover was a no-op because tracked Unshipped entries were empty; the surface summary has only the existing Auth baseline and is not a complete cross-library API proof. See the release runbook.