Az.Cdn 6.1.0-preview: preserve current CDN snapshot

[Ptnan7]

Description

Prepare the current Az.Cdn snapshot as 6.1.0-preview, targeting the independent Az.Cdn-preview release branch.

• Preserve the complete tracked src/Cdn snapshot from 8e41aba41fc (add-migration-cutover-warning), including generated code, custom wrappers, examples, help, tests, recordings, and existing migration endpoint cutover warnings.
• Keep the shipping manifest's numeric ModuleVersion at 6.1.0 and set PrivateData.PSData.Prerelease = 'preview'.
• Rename the existing 6.1.0 changelog heading to 6.1.0-preview; leave the release-note content unchanged.
• Change no files outside src/Cdn. Do not merge unrelated main-branch changes into the preview release line.

The snapshot consumes CDN API 2026-04-01-preview and the existing EdgeAction API configuration. This PR does not regenerate or redesign the module and does not publish a package.

Release Coordination

Public preview releases must not target main or generation, per CONTRIBUTING.md. Az.Cdn-preview is the existing CDN public-preview line used by PR #25759. Main has independently advanced to Az.Cdn 6.2.0; this PR deliberately retains the requested local 6.1.0 snapshot and does not downgrade main.

This PR is draft pending release-owner confirmation of the preview line and packaging validation. The large diff against the older preview branch is the existing CDN snapshot, not newly authored implementation changes. Shared build infrastructure and release-aggregation files are intentionally not changed.

Validation

• Passed: Import-PowerShellDataFile parses the shipping manifest; its numeric version is a valid System.Version; the composed release version is exactly 6.1.0-preview and matches the changelog.
• Passed: Git content comparison verifies every CDN file matches source snapshot 8e41aba41fc, except the two explicitly validated release-metadata changes. The manifest differs only in the prerelease field; the changelog differs only in the version heading.
• Passed: the PR diff contains no files outside src/Cdn.
• Passed: git diff --check for the release-metadata delta. Full snapshot whitespace diagnostics against the older preview branch are identical before and after the metadata changes; existing whitespace and changelog Markdown-format diagnostics are preserved rather than reformatted.
• Not run: AutoRest generation, module build, full StaticAnalysis categories, and scenario playback/live/record tests. No new implementation was authored; these checks were not rerun for this snapshot-only release preparation. Compatibility with the older preview branch's shared build infrastructure remains unverified. Existing tests and recordings are retained unchanged; this is not a claim that the full PR passes CI.

Mandatory Checklist

• Please choose the target release of Azure PowerShell. Target release is a different concept from API readiness.

  • General release
  • Public preview
  • Private preview
  • Engineering build
  • No need for a release

• Check this box to confirm: I have read the Submitting Changes section of CONTRIBUTING.md and reviewed the following information:

• SHOULD update ChangeLog.md file(s) appropriately
  • Update src/{{SERVICE}}/{{SERVICE}}/ChangeLog.md.
    • A snippet outlining the change(s) made in the PR should be written under the ## Upcoming Release header in the past tense.
  • Should not change ChangeLog.md if no new release is required, such as fixing test case only.
• SHOULD regenerate markdown help files if there is cmdlet API change. Instruction
• SHOULD have proper test coverage for changes in pull request.
• SHOULD NOT adjust version of module manually in pull request

The numeric module version is preserved from the requested snapshot; the only new version setting is the explicit preview prerelease marker.

[azure-pipelines]

Azure Pipelines:
There may be pipelines that require an authorized user to comment /azp run to run.

[x-engineering-agent]

Automated sensitive-information remediation ran on this pull request.

• Detected categories: credential
• Replaced with typed [REDACTED:category] placeholders in: no PR metadata fields
• Comment/review owners notified because X Engineering Agent cannot edit another user's text: none

X Engineering Agent does not modify source files. The PR creator must remove or replace each suspected value at the linked line:

• src/Cdn/Cdn.Autorest/docs/New-AzFrontDoorCdnCustomDomain.md:61 — possible credential
• src/Cdn/Cdn.Autorest/docs/New-AzFrontDoorCdnCustomDomainTlsSettingParametersObject.md:28 — possible credential
• src/Cdn/Cdn.Autorest/docs/Update-AzFrontDoorCdnCustomDomain.md:67 — possible credential
• src/Cdn/Cdn.Autorest/docs/Update-AzFrontDoorCdnCustomDomain.md:83 — possible credential

If a credential was exposed, rotate or revoke it immediately. Detected values are never copied into this comment.

✅ Confirm the finding · ❌ Dispute the finding

GitHub only supports a fixed reaction set, so 👍 represents ✅ and 👎 represents ❌. The bot-created reactions are only poll choices.