Skip to content

Conversation

@ajalon1
Copy link
Contributor

@ajalon1 ajalon1 commented Jan 14, 2026

RATIONALE

We don't want brew install dr-cli to update users to release candidates and other pre-releases.

Our goreleaser configuration only works to skip rc tags, but @yuriyhrytsyuk and I are using beta atm.

Reference: https://goreleaser.com/customization/homebrew_casks/

    # Setting this will prevent goreleaser to actually try to commit the updated
    # cask - instead, the cask file will be stored on the dist directory
    # only, leaving the responsibility of publishing it to the user.
    # If set to auto, the release will not be uploaded to the homebrew tap
    # in case there is an indicator for prerelease in the tag e.g. v1.0.0-rc1
    #
    # Templates: allowed.
    skip_upload: true

CHANGES

Configure goreleaser to not publish to datarobot-oss/homebrew-taps if a non stable tag has been created.

PR Automation

Comment-Commands: Trigger CI by commenting on the PR:

  • /trigger-smoke-test or /trigger-test-smoke - Run smoke tests
  • /trigger-install-test or /trigger-test-install - Run installation tests

Labels: Apply labels to trigger workflows:

  • run-smoke-tests or go - Run smoke tests on demand (only works for non-forked PRs)

Important

For Forked PRs: If you're an external contributor, the run-smoke-tests label won't work. Only maintainers can trigger smoke tests on forked PRs by applying the approved-for-smoke-tests label after security review. Please comment requesting maintainer review if you need smoke tests to run.

@ajalon1 ajalon1 requested a review from a team January 14, 2026 15:40
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.

1 participant