v3 docker image version bump note

[robreinhard]

For future reference,

My engineering team noticed today that the docker versioning bug fix (which came about in v3.5) did a massive version bump for the v3 docker tag.

We noticed this because integration tests suddenly had trouble deserializing from the api/messages endpoint. This is because the last version of v3 did not have pagination.

Seems this bug fix resulted in a 2 year fast-forward for the tag.

We might want this more heavily noted as it breaks integration tests.

[rnwood]

Thanks for the feedback. That's right. The bug in the release process resulted in all those tags not being pushed for a long period of time. There are tags for latest V3, V3.x as well as each individual build. The API wasn't public until recently. So until then, we have not communicated or considered the impact of any changes on other consumers. But now it's public, that should be the case going forward.

…

________________________________ From: Rob Reinhard ***@***.***> Sent: Wednesday, May 8, 2024 10:06:49 PM To: rnwood/smtp4dev ***@***.***> Cc: Subscribed ***@***.***> Subject: [rnwood/smtp4dev] v3 version bump note (Issue #1465) For future reference, My engineering team noticed today that the docker versioning bug fix (which came about in v3.5) did a massive version bump for the v3 docker tag. We noticed this because integration tests suddenly had trouble deserializing from the api/messages endpoint. This is because the last version of v3 did not have pagination. Seems this bug fix resulted in a 2 year fast-forward for the tag. — Reply to this email directly, view it on GitHub<#1465>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AAKEGF6QDW3SIVRA7DB6ZITZBKHWTAVCNFSM6AAAAABHNV6VFOVHI2DSMVQWIX3LMV43ASLTON2WKOZSGI4DMNBXGMYTIMY>. You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>