Skip to content

ci: start the Docker image build after the PyPI publish - #1267

Merged
B4nan merged 2 commits into
masterfrom
ci/docker-trigger-version-env
Nov 18, 2026
Merged

B4nan merged 2 commits into
masterfrom
ci/docker-trigger-version-env

Conversation

@vdusek

@vdusek vdusek commented Nov 18, 2026 •

Copy link
Copy Markdown
Contributor

Two changes to the Trigger Docker image build job:

  • It waits for pypi_publish. The Python Docker images take the SDK version from PyPI, so a build that started next to the publish could pick up the previous release.
  • It reads the release version from an environment variable instead of writing it into the gh api command, and sends all payload fields with -f as plain strings.

✍️ Drafted by Claude Code

@vdusek vdusek added adhoc Ad-hoc unplanned task added during the sprint. t-tooling Issues with this label are in the ownership of the tooling team. labels Nov 18, 2026
@vdusek vdusek self-assigned this Nov 18, 2026
@vdusek vdusek added adhoc Ad-hoc unplanned task added during the sprint. t-tooling Issues with this label are in the ownership of the tooling team. labels Nov 18, 2026
@vdusek vdusek changed the title ci: pass the release version to the Docker build trigger as a string ci: pass the release version to the Docker trigger as a string Nov 18, 2026
@codecov

codecov Bot commented Nov 18, 2026 •

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 93.83%. Comparing base (bbebcf2) to head (1283785).

Additional details and impacted files
@@            Coverage Diff             @@
##           master    #1267      +/-   ##
==========================================
- Coverage   93.88%   93.83%   -0.06%     
==========================================
  Files          54       54              
  Lines        3893     3893              
==========================================
- Hits         3655     3653       -2     
- Misses        238      240       +2     
Flag Coverage Δ
e2e 31.08% <ø> (ø)
integration 50.70% <ø> (ø)
unit 91.08% <ø> (-0.06%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@vdusek vdusek changed the title ci: pass the release version to the Docker trigger as a string ci: start the Docker image build after the PyPI publish Nov 18, 2026
@vdusek
vdusek marked this pull request as ready for review November 18, 2026 15:36
@vdusek
vdusek requested review from B4nan and janbuchar and removed request for B4nan November 18, 2026 15:36
@B4nan
B4nan merged commit ed65f5f into master Nov 18, 2026
46 checks passed
@B4nan
B4nan deleted the ci/docker-trigger-version-env branch November 18, 2026 16:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

adhoc Ad-hoc unplanned task added during the sprint. t-tooling Issues with this label are in the ownership of the tooling team.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants