Skip to content

Conversation

mbg
Copy link
Member

@mbg mbg commented Oct 1, 2025

This workflow is no longer needed now that the update-job-proxy binaries are published as part of CLI releases.

Risk assessment

For internal use only. Please select the risk level of this change:

  • Low risk: Changes are fully under feature flags, or have been fully tested and validated in pre-production environments and are highly observable, or are documentation or test only.

Merge / deployment checklist

  • Confirm this change is backwards compatible with existing workflows.
  • Consider adding a changelog entry for this change.
  • Confirm the readme and docs have been updated if necessary.

@mbg mbg requested a review from a team as a code owner October 1, 2025 14:31
@Copilot Copilot AI review requested due to automatic review settings October 1, 2025 14:31
Copy link
Contributor

@Copilot Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull Request Overview

This PR removes the update-proxy-release workflow that was previously used to update proxy binaries, as this functionality is now handled as part of CLI releases.

  • Removes the entire update-proxy-release.yml workflow file
  • Eliminates the need for manual workflow dispatch to update proxy binaries
  • Streamlines the release process by consolidating proxy binary publishing

@mbg mbg merged commit b496401 into main Oct 2, 2025
313 of 369 checks passed
@mbg mbg deleted the mbg/start-proxy/remove-update-workflow branch October 2, 2025 10:05
@github-actions github-actions bot mentioned this pull request Oct 2, 2025
8 tasks
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.

2 participants