Skip to content

Conversation

AtofStryker
Copy link
Contributor

@AtofStryker AtofStryker commented Oct 10, 2025

  • Closes

Additional details

Steps to test

How has the user experience changed?

PR Tasks


Note

Adds a publish-binary-branch pipeline parameter and switches binary publish triggering to a new CircleCI command, removing the old Node script.

  • CI/CircleCI:
    • Add pipeline parameter publish-binary-branch and pass it through continuation (.circleci/config.yml, .circleci/src/pipeline/@pipeline.yml).
    • Replace JS-based trigger with new command commands/trigger-publish-binary-pipeline.yml (uses curl/jq, parameter target-repo-branch).
    • Update job create-and-trigger-packaging-artifacts to call trigger-publish-binary-pipeline with target-repo-branch: << pipeline.parameters.publish-binary-branch >>.
    • Remove scripts/binary/trigger-publish-binary-pipeline.js.
  • Docs:
    • Update packages/electron/README.md checklist to use the new parameterized flow and CircleCI UI trigger, adding guidance to set publish-binary-branch and workflow filters.

Written by Cursor Bugbot for commit 284b03d. This will update automatically on new commits. Configure here.

cacieprins and others added 3 commits October 7, 2025 13:52
…ed value for branch

- migrates trigger-publish-binary-pipeline.js to an inlined bash script to speed
  it up and simplify it
- adds a pipeline parameter that can be set via CircleCI UI to determine which
  branch we use in the publish-binary pipeline, to reduce file churn and human
  error
- updates the packages/electron/README.md to include the simplified steps
fi

echo "Pipeline saved to triggered_pipeline.json"
echo "Triggered pipeline: https://app.circleci.com/pipelines/github/cypress-io/cypress-publish-binary/$(jq -r '.number' triggered_pipeline.json)"
Copy link

Choose a reason for hiding this comment

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

Bug: Pipeline URL Error Due to File Path Mismatch

The jq command attempts to read triggered_pipeline.json from the current directory, but curl saves the file to ~/triggered_pipeline.json. This path mismatch prevents jq from finding the file, resulting in a broken pipeline URL in the output.

Fix in Cursor Fix in Web

"binary_version": "$NEXT_VERSION"
}
}
JSON_BODY_EOF
Copy link

Choose a reason for hiding this comment

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

Bug: Pipeline Trigger Fails Due to JSON Interpolation

The JSON body for triggering the pipeline directly interpolates shell variables. This omits necessary JSON escaping for string values and boolean conversion for SHOULD_PERSIST_ARTIFACTS, which can lead to malformed JSON and pipeline trigger failures if variable contents are not strictly valid.

Fix in Cursor Fix in Web

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