Skip to content

add release vscode workflow; fix changelog#10719

Open
hlshen wants to merge 9 commits into
mainfrom
hlshen/release-workflow
Open

add release vscode workflow; fix changelog#10719
hlshen wants to merge 9 commits into
mainfrom
hlshen/release-workflow

Conversation

@hlshen

@hlshen hlshen commented Jun 25, 2026

Copy link
Copy Markdown
Contributor

Create a release-vscode-ext workflow, used to trigger the Kokoro build, sign, and publish pipeline.

@hlshen hlshen requested review from fredzqm and joehan June 25, 2026 17:37
@wiz-9635d3485b

wiz-9635d3485b Bot commented Jun 25, 2026

Copy link
Copy Markdown

Wiz Scan Summary

Scanner Findings
Vulnerability Finding Vulnerabilities -
Data Finding Sensitive Data -
Secret Finding Secrets -
IaC Misconfiguration IaC Misconfigurations 1 High
SAST Finding SAST Findings -
Software Management Finding Software Management Findings -
Total 1 High

View scan details in Wiz

To detect these findings earlier in the dev lifecycle, try using Wiz Code VS Code Extension.

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Code Review

This pull request updates the CHANGELOG.md file by adding a '## NEXT' header to prepare for future release notes. There are no review comments to address.

@hlshen hlshen enabled auto-merge (squash) June 25, 2026 17:46
Comment thread .github/workflows/release-vscode-ext.yaml Fixed
Comment thread .github/workflows/release-vscode-ext.yaml Fixed
Comment thread .github/workflows/release-vscode-ext.yaml Fixed
Comment thread .github/workflows/release-vscode-ext.yaml Fixed
Comment thread .github/workflows/release-vscode-ext.yaml Fixed

@joehan joehan left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Seems fine once we change the branch name

Comment thread .github/workflows/release-vscode-ext.yaml Outdated
Comment thread .github/workflows/release-vscode-ext.yaml
Comment thread .github/workflows/release-vscode-ext.yaml
@hlshen hlshen requested a review from morganchen12 June 26, 2026 18:09
Comment thread .github/workflows/release-vscode-ext.yaml
Comment thread .github/workflows/release-vscode-ext.yaml Outdated
Comment thread .github/workflows/release-vscode-ext.yaml
@hlshen hlshen requested review from joehan and morganchen12 June 26, 2026 21:08
Comment on lines +32 to +34
TARGET_BRANCH="vscode-release-trigger-build-only"
else
TARGET_BRANCH="vscode-release-trigger"

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Given these are going to be origins for release artifacts, you should work with Joe to set up branch protections for these branches.

github.event.issue.pull_request &&
startsWith(github.event.comment.body, '/run-release') &&
(github.event.comment.author_association == 'OWNER' ||
github.event.comment.author_association == 'MEMBER' ||

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Lets also assert that the pr aiuthor is an owner or maintainer as well. I don't think we'd ever run this on a contributor branch, but we should encode that into the rule

jobs:
release:
if: |
github.event.issue.pull_request &&

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Please also add an author check here.

(github.event.issue.author_association == 'OWNER' ||
github.event.issue.author_association == 'MEMBER')

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.

6 participants