Skip to content

ci: trusted publisher release flow - #1052

Open
ricellis wants to merge 1 commit into
mainfrom
s1384-trusted-publisher
Open

ricellis wants to merge 1 commit into
mainfrom
s1384-trusted-publisher

Conversation

@ricellis

@ricellis ricellis commented Nov 4, 2026

Copy link
Copy Markdown
Member

PR summary

Release workflow using trusted publisher

Fixes: s1384

PR Checklist

Please make sure that your PR fulfills the following requirements:

  • The commit message follows the
    Angular Commit Message Guidelines.
  • Tests for the changes have been added (for bug fixes / features) - ci
  • Docs have been added / updated (for bug fixes / features) - ci

PR Type

  • Bugfix
  • Feature
  • Code style update (formatting, local variables)
  • Refactoring (no functional changes, no api changes)
  • New tests
  • Build/CI related changes
  • Documentation content changes
  • Other (please describe)

What is the current behavior?

Publishing does not use OIDC trusted publisher.

What is the new behavior?

Add publish.yml trusted publisher workflow.

Does this PR introduce a breaking change?

  • Yes
  • No

Other information

@ricellis ricellis self-assigned this Nov 4, 2026

This branch has not been deployed

No deployments
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.

1 participant