Skip to content

chore: use environments for various CI pipelines (#31654) - #31729

Merged
sreya merged 1 commit into
release/2.36from
backport/31654-to-2.36
Nov 4, 2026
Merged

sreya merged 1 commit into
release/2.36from
backport/31654-to-2.36

Conversation

@sreya

@sreya sreya commented Nov 3, 2026

Copy link
Copy Markdown
Collaborator

Backport of #31654 to release/2.36.

Original PR: #31654 (chore: use environments for various CI pipelines)
Merge commit: b0cc77d

Release tags run the release.yaml from their own branch, and pushes to this branch run its own ci.yaml. Without this backport, releases and builds from release/2.36 keep reading the repo-level signing secrets and break once those are deleted.

Changes: cherry-picked with no conflicts. Same as main:

  • release.yaml: release job uses the release environment; publish-homebrew and publish-winget use release-publish.
  • ci.yaml build: uses ci-signing.
  • Those jobs no longer restore the mise or pnpm caches (new use-cache input on pnpm-install).
  • Dry-run SBOM fix: the SBOM is only passed to publish.sh on real releases.
  • Dependabot ecosystem fix (harmless here; Dependabot only reads the default branch).

@sreya for review.


Generated with Coder Agents.

@sreya sreya added the backport/v2.36 Backport PR targeting release/2.36 label Nov 3, 2026
@sreya sreya self-assigned this Nov 3, 2026
@github-actions

github-actions Bot commented Nov 3, 2026

Copy link
Copy Markdown
Contributor

👋 Hey @sreya!

This PR is targeting the release/2.36 release branch, but its title does not start with fix: or fix(scope):.

Only bug fixes should be cherry-picked to release branches. If this is a bug fix, please update the PR title to match the conventional commit format:

fix: description of the bug fix
fix(scope): description of the bug fix

If this is not a bug fix, it likely should not target a release branch.

@sreya
sreya merged commit dc59494 into release/2.36 Nov 4, 2026
57 of 58 checks passed
@sreya
sreya deleted the backport/31654-to-2.36 branch November 4, 2026 02:35
@github-actions github-actions Bot locked and limited conversation to collaborators Nov 4, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

backport/v2.36 Backport PR targeting release/2.36

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants