Trusted Signing GA SDK Release #28679
Draft
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
added 7 commits
October 7, 2025 12:37
| Thanks for your contribution! The pull request validation has started. Please revisit this comment for updated status. |
There was a problem hiding this comment.
Pull Request Overview
This PR represents the general availability (GA) release of the Azure Trusted Signing PowerShell module, transitioning from preview to stable status. The changes update API versions, module metadata, and build configurations to reflect the production-ready state.
Key changes include:
- Updated API version from preview (
2024-09-30-preview) to GA (2025-10-13) - Incremented module version from
0.1.0to1.0.0 - Added WhatIf/Confirm support to the CI Policy signing cmdlet
Reviewed Changes
Copilot reviewed 12 out of 19 changed files in this pull request and generated no comments.
Show a summary per file
| File | Description |
|---|---|
Invoke-AzTrustedSigningCIPolicySigning.md |
Added WhatIf and Confirm parameter documentation for the CI Policy signing cmdlet |
Az.TrustedSigning.psd1 |
Updated module manifest with new generation date, Az.Accounts dependency version, and formatting improvements |
TrustedSigning.sln |
Restructured solution file with updated project references and build configurations |
env.json |
Reordered test environment configuration properties |
Test-AzTrustedSigningAccountNameAvailability.Recording.json |
Updated test recording with new GA API version and request identifiers |
generate-info.json |
Updated generation ID for the AutoRest build |
Az.TrustedSigning.md |
Updated module GUID in documentation |
codeSigningAccounts*.json |
Updated API version references in UX configuration files |
README.md |
Updated commit reference and module version for AutoRest generation |
AssemblyInfo.cs |
Added copyright header and updated assembly version information |
.gitignore |
Added exclusion for custom PowerShell module files |
|
/azp run |
|
Azure Pipelines successfully started running 3 pipeline(s). |
isra-fel
reviewed
Oct 13, 2025
|
|
||
| # For new RP, the version is 0.1.0 | ||
| module-version: 0.1.0 | ||
| module-version: 1.0.0 |
There was a problem hiding this comment.
Please reach out to us internally if you wish to GA the module
|
Thanks for the review, @janielMartell lets talk about this internally as well. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Mandatory Checklist
Please choose the target release of Azure PowerShell. (⚠️ Target release is a different concept from API readiness. Please click below links for details.)
Check this box to confirm: I have read the Submitting Changes section of
CONTRIBUTING.mdand reviewed the following information:ChangeLog.mdfile(s) appropriatelysrc/{{SERVICE}}/{{SERVICE}}/ChangeLog.md.## Upcoming Releaseheader in the past tense.ChangeLog.mdif no new release is required, such as fixing test case only.