Remove legacy tag-triggered release workflow#1402
Merged
Merged
Conversation
Releases for databricks-sdk-py are now driven by the secure public registry releases pipeline in databricks/secure-public-registry-releases-eng, which dispatches tagging.yml in this repository. The old entry points are obsolete: - .github/workflows/release.yml: tag-push-triggered (on: push: tags: 'v*') workflow that built the wheel and published to PyPI / created the GitHub release. Superseded by the secure release pipeline. - .github/workflows/release-test.yml: manual workflow_dispatch helper that published to TestPyPI. Legacy entry point from the old release flow; no longer needed now that the new pipeline owns publishing. Neither file carried any dry-run, push-to-main, merge_group, or PR CI logic to preserve, so both are deleted outright. CI/build verification remains in push.yml (pull_request + merge_group) and the reusable test.yml, which are untouched. Note: if branch protection required status checks referenced "Release" or "Release (TestPyPI)", those entries will need to be removed from branch protection settings.
hectorcast-db
temporarily deployed
to
test-trigger-is
GitHub Actions
Inactive
hectorcast-db
temporarily deployed
to
test-trigger-is
GitHub Actions
Inactive
|
If integration tests don't run automatically, an authorized user can run them manually by following the instructions below: Trigger: Inputs:
Checks will be approved automatically on success. |
mihaimitrea-db
approved these changes
Apr 23, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
NO_CHANGELOG=true
Summary
Releases for
databricks-sdk-pyare now owned by the secure public registry releases pipeline indatabricks/secure-public-registry-releases-eng. That pipeline callstagging.ymlin this repo to create the tag and publish the artifact through the hardened path. The tag-push-triggered workflow and the manual TestPyPI helper in this repo are now obsolete entry points and are removed here.Per-file decisions
.github/workflows/release.ymlpush: tags: 'v*'. Built the wheel, published to PyPI, and created the GitHub release. Superseded by the secure release pipeline..github/workflows/release-test.ymlworkflow_dispatchhelper that published to TestPyPI. Legacy companion to the old release flow; the new pipeline owns publishing, so this is no longer needed..github/workflows/tagging.yml.github/workflows/push.ymlmerge_groupCI. Preserved..github/workflows/test.ymlpush.yml. Preserved..github/workflows/next-changelog.yml,integration-tests.yml,external-message.ymlWhat's preserved
merge_groupCI viapush.yml(tests on Ubuntu + Windows across Python 3.10/3.11/3.12,fmt,check-manifest).test.ymlworkflow.tagging.yml— still the dispatch target for the new secure release pipeline.About the proposed rename
The original plan considered renaming a remaining release workflow to
release-build-check.ymlif it retained dry-run / snapshot /merge_group/ PR-CI triggers. Neither of the two removed files carried any such triggers (release.ymlwas tag-only;release-test.ymlwasworkflow_dispatch-only), so there was nothing to edit-and-rename. Build verification for PRs already lives inpush.yml/test.yml, so a standalonerelease-build-check.ymlwould be a no-op and is intentionally not created.Branch protection
If branch protection required status checks referenced the workflow names
ReleaseorRelease (TestPyPI), those entries will need to be removed from the branch protection settings when this merges — they will no longer report.Test plan
Release/Release (TestPyPI); remove if present.databricks/secure-public-registry-releases-engis the sole entry point for cutting a new release.buildfrompush.yml) passes on this PR.This pull request and its description were prepared by an AI agent on behalf of @hectcastro.