Skip to content

fix: re-push image even when only the dockerfile has changed #10248

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Aug 11, 2025

Conversation

emily-shen
Copy link
Contributor

Fixes CC-5563


  • Tests
    • Tests included
    • Tests not necessary because:
  • Public documentation
    • Cloudflare docs PR(s):
    • Documentation not necessary because: bugfix
  • Wrangler V3 Backport
    • Wrangler PR:
    • Not necessary because: new

@emily-shen emily-shen requested review from a team as code owners August 6, 2025 13:55
Copy link

changeset-bot bot commented Aug 6, 2025

🦋 Changeset detected

Latest commit: b84b753

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 3 packages
Name Type
wrangler Patch
@cloudflare/vite-plugin Patch
@cloudflare/vitest-pool-workers Patch

Not sure what this means? Click here to learn what changesets are.

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

Copy link
Contributor

github-actions bot commented Aug 6, 2025

Failed to automatically backport this PR's changes to Wrangler v3. Please manually create a PR targeting the v3-maintenance branch with your changes. Thank you for helping us keep Wrangler v3 supported!

Depending on your changes, running git rebase --onto v3-maintenance main emily/dockerfile-change might be a good starting point.

Notes:

  • your PR branch should be named v3-backport-10248
  • add the skip-v3-pr label to the current PR to stop this workflow from failing

Copy link

pkg-pr-new bot commented Aug 6, 2025

create-cloudflare

npm i https://pkg.pr.new/create-cloudflare@10248

@cloudflare/kv-asset-handler

npm i https://pkg.pr.new/@cloudflare/kv-asset-handler@10248

miniflare

npm i https://pkg.pr.new/miniflare@10248

@cloudflare/pages-shared

npm i https://pkg.pr.new/@cloudflare/pages-shared@10248

@cloudflare/unenv-preset

npm i https://pkg.pr.new/@cloudflare/unenv-preset@10248

@cloudflare/vite-plugin

npm i https://pkg.pr.new/@cloudflare/vite-plugin@10248

@cloudflare/vitest-pool-workers

npm i https://pkg.pr.new/@cloudflare/vitest-pool-workers@10248

@cloudflare/workers-editor-shared

npm i https://pkg.pr.new/@cloudflare/workers-editor-shared@10248

wrangler

npm i https://pkg.pr.new/wrangler@10248

commit: b84b753

@emily-shen emily-shen added the skip-v3-pr Skip validation of presence of a v3 backport PR label Aug 6, 2025
Copy link
Contributor Author

@emily-shen emily-shen Aug 6, 2025

Choose a reason for hiding this comment

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

argh - hoped github might've preserved the changes when i renamed this file. basically this is the same as the original, except i wanted to add some e2e tests for this image re-pushing behaviour since the docker command we use is experimental and could break under us. although i did simplify some of the dev test setup while i was there too.

@emily-shen emily-shen force-pushed the emily/dockerfile-change branch 7 times, most recently from abf5ec2 to d69ecef Compare August 11, 2025 09:12
@emily-shen emily-shen force-pushed the emily/dockerfile-change branch from d69ecef to b84b753 Compare August 11, 2025 09:12
@emily-shen
Copy link
Contributor Author

emily-shen commented Aug 11, 2025

For posterity, I've ended up removing the e2e tests that check this behaviour because I can't get them to work in CI :( (regular unit tests still exist for this feature, the e2e tests worked locally too fwiw...)

I think this is ok because I added the e2e tests because i thought it would be useful to test the actual behaviour of docker manifest inspect since that was experimental, but we don't control the docker version in github CI anyway (e.g. currently the runners are using a version from March still). Also, if the command breaks, it doesn't break anyone's flow, it just means slightly worse DX as there is an unnecessary push.

@github-project-automation github-project-automation bot moved this from Untriaged to Approved in workers-sdk Aug 11, 2025
@petebacondarwin petebacondarwin merged commit 422ae22 into main Aug 11, 2025
40 of 46 checks passed
@petebacondarwin petebacondarwin deleted the emily/dockerfile-change branch August 11, 2025 11:25
@github-project-automation github-project-automation bot moved this from Approved to Done in workers-sdk Aug 11, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
skip-v3-pr Skip validation of presence of a v3 backport PR
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

5 participants