steve/databricks-cli
steve
/
databricks-cli
mirror of https://github.com/databricks/cli.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
databricks-cli/.github/workflows/publish-winget.yml

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

29 lines
893 B
YAML
Raw Normal View History

Decouple winget release (#1389) ## Changes We are starting to sign Windows CLI executables, but this has to be done from a machine with a Yubikey storing the signing certificate for the immediate future. As such, we will only trigger Winget publishing once the signed binaries have been uploaded to Github. Additionally, as an extra precaution, we will only release the signed binaries via Winget. ## Tests <!-- How is this tested? -->
2024-04-23 07:17:14 +00:00
name: publish-winget
on:
workflow_dispatch:
Pass tag to release as input to publish-winget workflow (#2107) ## Changes This workflow only worked if it was triggered on the tag to publish itself. This means it is not possible to release a version if the workflow configuration at that tag is broken (as is the case for v0.238.0 because of #2105). This change adds a "tag" input that can be set when manually triggering the workflow. ## Tests * Succesful run with this change: https://github.com/databricks/cli/actions/runs/12689281843 * Pull request that the run created: https://github.com/microsoft/winget-pkgs/pull/209220
2025-01-09 12:07:29 +00:00
inputs:
tag:
description: 'Tag to publish'
default: ''
Decouple winget release (#1389) ## Changes We are starting to sign Windows CLI executables, but this has to be done from a machine with a Yubikey storing the signing certificate for the immediate future. As such, we will only trigger Winget publishing once the signed binaries have been uploaded to Github. Additionally, as an extra precaution, we will only release the signed binaries via Winget. ## Tests <!-- How is this tested? -->
2024-04-23 07:17:14 +00:00
jobs:
publish-to-winget-pkgs:
Update runner for the publish-winget job (#2105) ## Changes This action uses a token to access the release artifacts and, as such, needs to execute on the runner that's on the allowlist. Related PRs: * #2098 * #2077
2025-01-09 11:21:30 +00:00
runs-on:
group: databricks-protected-runner-group
labels: windows-server-latest
Decouple winget release (#1389) ## Changes We are starting to sign Windows CLI executables, but this has to be done from a machine with a Yubikey storing the signing certificate for the immediate future. As such, we will only trigger Winget publishing once the signed binaries have been uploaded to Github. Additionally, as an extra precaution, we will only release the signed binaries via Winget. ## Tests <!-- How is this tested? -->
2024-04-23 07:17:14 +00:00
environment: release
Update runner for the publish-winget job (#2105) ## Changes This action uses a token to access the release artifacts and, as such, needs to execute on the runner that's on the allowlist. Related PRs: * #2098 * #2077
2025-01-09 11:21:30 +00:00
Decouple winget release (#1389) ## Changes We are starting to sign Windows CLI executables, but this has to be done from a machine with a Yubikey storing the signing certificate for the immediate future. As such, we will only trigger Winget publishing once the signed binaries have been uploaded to Github. Additionally, as an extra precaution, we will only release the signed binaries via Winget. ## Tests <!-- How is this tested? -->
2024-04-23 07:17:14 +00:00
steps:
Pin all github actions to commit hash (#2129) ## Changes - Pin all github actions to commit hash. - Modify vedantmgoyal2009/winget-releaser to use tag format that dependabot can understand. Pinning is done by https://github.com/databricks/cli/blob/denik/pin-actions-script/pin_actions.py (100% chatgpt authored). Commits and tags are verified manually. This format should be recognized by dependabot enabled in https://github.com/databricks/cli/pull/2112 ## Tests Existing tests.
2025-01-14 07:39:34 +00:00
- uses: vedantmgoyal2009/winget-releaser@93fd8b606a1672ec3e5c6c3bb19426be68d1a8b0 # v2
Decouple winget release (#1389) ## Changes We are starting to sign Windows CLI executables, but this has to be done from a machine with a Yubikey storing the signing certificate for the immediate future. As such, we will only trigger Winget publishing once the signed binaries have been uploaded to Github. Additionally, as an extra precaution, we will only release the signed binaries via Winget. ## Tests <!-- How is this tested? -->
2024-04-23 07:17:14 +00:00
with:
identifier: Databricks.DatabricksCLI
installers-regex: 'windows_.*-signed\.zip$' # Only signed Windows releases
token: ${{ secrets.ENG_DEV_ECOSYSTEM_BOT_TOKEN }}
fork-user: eng-dev-ecosystem-bot
Pass tag to release as input to publish-winget workflow (#2107) ## Changes This workflow only worked if it was triggered on the tag to publish itself. This means it is not possible to release a version if the workflow configuration at that tag is broken (as is the case for v0.238.0 because of #2105). This change adds a "tag" input that can be set when manually triggering the workflow. ## Tests * Succesful run with this change: https://github.com/databricks/cli/actions/runs/12689281843 * Pull request that the run created: https://github.com/microsoft/winget-pkgs/pull/209220
2025-01-09 12:07:29 +00:00
# Use the tag from the input, or the ref name if the input is not provided.
# The ref name is equal to the tag name when this workflow is triggered by the "sign-cli" command.
release-tag: ${{ inputs.tag || github.ref_name }}