ci: add manual marketplace release workflow#539
Closed
will-yuponce-db wants to merge 1 commit into
Closed
Conversation
Adds a workflow_dispatch 'Release to Marketplace' workflow that wraps the manual steps in CONTRIBUTING.md > Release Process behind one button: - version input field (required) drives src/scripts/bump_version.py - editable release_tag (default v<version>) and marketplace_tag (default marketplace-v<version>) fields - commits the bump to main, tags the commit with both tag families, pushes, and cuts a GitHub Release - optional Databricks deploy step (placeholder pending the exact publish command + secrets) Notes for review: - Runs on the protected runner group (org IP allow list). - Pushing the bump commit to protected main needs RELEASE_TOKEN (an org admin / bypass-actor PAT); tags are not branch-protected. Co-authored-by: Isaac
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
1 participant
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.
What
A manual (
workflow_dispatch) Release to Marketplace workflow that wraps the steps inCONTRIBUTING.md> Release Process behind one Run workflow button, with editable input fields.Input fields
version(required) —X.Y.Z, drivessrc/scripts/bump_version.py.release_tag— defaults tov<version>.marketplace_tag— defaults tomarketplace-v<version>(the tag family the Marketplace listing tracks).create_github_release(default true),deploy(default false).What it does
bump_version.pyto sync the version acrosspyproject.toml,backend/src/__init__.py, and bothpackage.jsons.chore: bump version to <version>, tags with both tag families, pushes the commit + tags.Draft — needs confirmation before merge
RELEASE_TOKENsecret. The bump commit pushes tomain, which is now protected by the merge-queue ruleset. The token must belong to a bypass actor (org admin PAT). Tags aren't branch-protected, so they push fine underGITHUB_TOKEN. Falls back toGITHUB_TOKEN(which will fail the commit push on protected main).databricks bundle deploy/apps deploy. Need the exact publish command and which Databricks secrets exist (DATABRICKS_HOST/DATABRICKS_TOKENor SP OAuth) before enabling it.Open question
The current in-repo version is
0.6.1butmarketplace-v*tags run ahead (latestmarketplace-v0.6.4) — confirm whether the version field should track the marketplace line or thepyproject.tomlline.This pull request and its description were written by Isaac.