Skip to content

chore: migrate to new docker publish workflow#54499

Open
DanielRadlAMR wants to merge 1 commit intofrappe:developfrom
AMR-Mannesmann:chore/migrate-to-new-docker-publish-workflow
Open

chore: migrate to new docker publish workflow#54499
DanielRadlAMR wants to merge 1 commit intofrappe:developfrom
AMR-Mannesmann:chore/migrate-to-new-docker-publish-workflow

Conversation

@DanielRadlAMR
Copy link
Copy Markdown

@github-actions github-actions Bot added the skip-release-notes This PR should not be mentioned in the release notes label Apr 23, 2026
@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented Apr 23, 2026

📝 Walkthrough

Walkthrough

The pull request modifies .github/workflows/docker-release.yml to update the workflow dispatch endpoint triggered during releases. The change replaces the target workflow from build_stable.yml with core-build-stable.yml. The request headers, authentication using CI_PAT, and the payload ({"ref":"main"}) remain unchanged.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Title check ✅ Passed The title accurately describes the main change: migrating the Docker publish workflow endpoint from 'build_stable.yml' to 'core-build-stable.yml'.
Description check ✅ Passed The description references issue #54498, which is minimally related to the changeset and provides context for the change, though it lacks detailed explanation.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link
Copy Markdown
Contributor

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Inline comments:
In @.github/workflows/docker-release.yml:
- Line 18: The curl call used to dispatch the workflow does not validate the
HTTP response so failures can be treated as success; update the curl invocation
(the curl POST that calls dispatches) to detect non-2xx responses and exit
non‑zero on failure by either adding --fail and --show-error or capturing the
HTTP status via -w "%{http_code}" and checking it, and log the response
body/error details to the job output to surface 401/404/422/5xx errors and
prevent silent success.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yml

Review profile: CHILL

Plan: Pro

Run ID: 944a25b1-984f-4a92-b20e-bd528046b6fc

📥 Commits

Reviewing files that changed from the base of the PR and between 0e20e35 and 54deb86.

📒 Files selected for processing (1)
  • .github/workflows/docker-release.yml

Comment thread .github/workflows/docker-release.yml
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

skip-release-notes This PR should not be mentioned in the release notes

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant