Skip to content

ci: publish to npm only from release branches - #1219

Open
B4nan wants to merge 1 commit into
masterfrom
ci/publish-release-branch-check
Open

B4nan wants to merge 1 commit into
masterfrom
ci/publish-release-branch-check

Conversation

@B4nan

@B4nan B4nan commented Nov 18, 2026

Copy link
Copy Markdown
Member

The publish workflow took any git ref. It now checks that the commit is on master or 2.x before anything from it gets installed or built, and the job runs in an npm environment.

The environment gets created on the first run with no rules, so its branch policy and the environment binding of the npm trusted publisher still need to be set up by hand.

@B4nan B4nan added adhoc Ad-hoc unplanned task added during the sprint. t-tooling Issues with this label are in the ownership of the tooling team. labels Nov 18, 2026
@B4nan
B4nan requested review from barjin and janbuchar November 18, 2026 09:08

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

adhoc Ad-hoc unplanned task added during the sprint. t-tooling Issues with this label are in the ownership of the tooling team.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant