Skip to content

feat: rebrand trusted signing to artifact signing#982

Merged
dtivel merged 8 commits intodotnet:mainfrom
Jaxelr:feat/artifact-signing
Feb 26, 2026
Merged

feat: rebrand trusted signing to artifact signing#982
dtivel merged 8 commits intodotnet:mainfrom
Jaxelr:feat/artifact-signing

Conversation

@Jaxelr
Copy link
Member

@Jaxelr Jaxelr commented Feb 11, 2026

Resolves #971

This PR performs the following changes:

  • Creates a new artifact signing command along with its corresponding options and bootstraps it as a new subcommand of the sign command.
  • Shows a new message of obsoletion for the current trusted signing command.
  • Renames the existing trusted signing provider to artifact signing while using 1 provider for both the existing and new command.
  • Renames the corresponding unit tests and adds test for obsolete command
  • Updates and renames existing trusted signing integration doc to artifact signing integration.

@Jaxelr Jaxelr requested a review from a team as a code owner February 11, 2026 02:45
@dtivel
Copy link
Collaborator

dtivel commented Feb 25, 2026

@Jaxelr, looks great! Thanks for the PR. Can you please rebase to latest main, and I'll merge?

@Jaxelr
Copy link
Member Author

Jaxelr commented Feb 25, 2026

Artifact signing test:

image

Trusted signing test:

image

These are using the verbosity of information for simplicity.

@Jaxelr Jaxelr force-pushed the feat/artifact-signing branch from 74c710e to 0f40d8a Compare February 25, 2026 20:43
@Jaxelr Jaxelr force-pushed the feat/artifact-signing branch from 0f40d8a to 63c5fb0 Compare February 25, 2026 20:46
@Jaxelr
Copy link
Member Author

Jaxelr commented Feb 25, 2026

Ok, rebased against the latests.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Trusted Signing rebranded to Artifact Signing

3 participants