Skip to content

Conversation

thaJeztah
Copy link
Member

@thaJeztah thaJeztah commented Oct 6, 2025

full diff: moby/moby@4ca8aed...cfefa33

- What I did

- How I did it

- How to verify it

- Human readable description for the release notes

- A picture of a cute animal (not mandatory but encouraged)

@thaJeztah thaJeztah force-pushed the bump_engine branch 5 times, most recently from 2427ef3 to 2351a29 Compare October 6, 2025 20:51
@austinvazquez austinvazquez force-pushed the bump_engine branch 2 times, most recently from 25e53b0 to 7bf32ab Compare October 7, 2025 05:08
@thaJeztah
Copy link
Member Author

Looks like you updated / squashed things, and possibly reverted some changes we may still need; I likely won't have time to work on this Today, but in case you need the state from before you modified, I just pushed my branch as a "backup" branch in case useful;

@austinvazquez
Copy link
Contributor

Sorry about that. Yeah the cut-over to the new network types is challenging because its in quite a few spots but also type disparity from go-connections for functions (ParsePortSpecs) we haven't updated yet. I touched up docker/go-connections#148 but not sure if it was worth the investment. Still seems to be parts that are not lining up.

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