Skip to content

[HDX-4235] ci: remove cancel-in-progress from push.yml#2281

Draft
wrn14897 wants to merge 1 commit into
mainfrom
warren/HDX-4235-remove-cancel-in-progress-push-yml
Draft

[HDX-4235] ci: remove cancel-in-progress from push.yml#2281
wrn14897 wants to merge 1 commit into
mainfrom
warren/HDX-4235-remove-cancel-in-progress-push-yml

Conversation

@wrn14897
Copy link
Copy Markdown
Member

Summary

The Push Downstream workflow (.github/workflows/push.yml) uses
createWorkflowDispatch to fan a downstream EE port out for every push to
main. Each run is a single short API call, so there is no benefit to
cancelling in-flight runs.

The previous concurrency.cancel-in-progress: true setting created a race
where a queued run could be cancelled (and silently skipped entirely)
instead of running after the active one finished. This dropped the EE port
for at least one merge commit:

This PR removes the concurrency block entirely so every push to main
spawns its own downstream dispatch, even when pushes land close together.
A YAML comment is added in its place explaining the intent so the setting
isn't reintroduced.

This implements remediation option #3 from HDX-4235.

Screenshots or video

N/A — non-UI change.

How to test on Vercel preview

N/A — non-UI change.

References

… ports (HDX-4235)

The Push Downstream workflow uses createWorkflowDispatch to mirror each
push to main as a downstream EE port. Each run is a single short API
call, so there is no benefit to cancelling in-flight runs.

The previous `cancel-in-progress: true` setting created a race where a
queued run could be cancelled (and silently skipped entirely) instead of
running after the active one finished. This dropped the EE port for at
least one merge commit:

  - f6a1d02 (PR #2250,
    feat(mcp): add event_patterns display type to query tool)
    which had to be ported manually as hyperdxio/hyperdx-ee#2073.

Removing the concurrency block ensures every push to main spawns its own
downstream dispatch, even when pushes land close together.
@changeset-bot
Copy link
Copy Markdown

changeset-bot Bot commented May 15, 2026

⚠️ No Changeset found

Latest commit: 53b22d7

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@vercel
Copy link
Copy Markdown

vercel Bot commented May 15, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment
Project Deployment Actions Updated (UTC)
hyperdx-oss Ignored Ignored May 15, 2026 6:45am

Request Review

@wrn14897 wrn14897 added the ai-generated AI-generated content; review carefully before merging. label May 15, 2026
@github-actions
Copy link
Copy Markdown
Contributor

E2E Test Results

All tests passed • 178 passed • 3 skipped • 1265s

Status Count
✅ Passed 178
❌ Failed 0
⚠️ Flaky 3
⏭️ Skipped 3

Tests ran across 4 shards in parallel.

View full report →

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ai-generated AI-generated content; review carefully before merging.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant