Skip to content

Conversation

@Ndpnt
Copy link
Contributor

@Ndpnt Ndpnt commented Jan 12, 2026

No description provided.

Empirical observation: the workflow succeeds with "on: push" but fails with "on: pull_request_target". This suggests npm's OIDC validation may not support the pull_request subject claim format, though this isn't explicitly documented by npm.

This change is safe because `main` is protected and only accepts PR merges (except OTA-Release-bot for automated release commits). The changelog validation logic also prevents accidental releases.
Copy link
Member

@clementbiron clementbiron left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't really understand what you're doing, and I think I would need a lot of context and time to do a proper review. I approve to try to get the release working out as soon as possible.

@Ndpnt Ndpnt merged commit 62e1a24 into main Jan 12, 2026
14 checks passed
@Ndpnt Ndpnt deleted the fix-release branch January 12, 2026 16:22
Copy link
Member

@MattiSG MattiSG left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This change seems very dangerous to me. I understand that now, the release workflow will be called on every push to main, not anymore on merged pull requests only. How will this broadening of release triggers not create loops when the release workflow creates a commit on main to modify the changelog?

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.

4 participants