:loudspeaker: We will be officially releasing Wire...
# announcements
o
šŸ“¢ We will be officially releasing WireMock 3.0.0 in the next few days. The artifacts are already there in Maven central, and we are updating the documentation, Docker images, Helm charts and other artifacts to use WireMock 3 before the announcements The WireMock 3.0.0 documentation is live, as well as the
2.x
archive. It would be great if the team, especially the engineer folks, could glance through the documentation and report any gaps and obsolete information you notice before the announcements (tomorrow?). We know about some undocumented features, some mis-merges into the 2.x documentation for early 3 beta, and likely there are many more issues due to harcoded versions and obsolete information. Any reports on GitHub issues would be appreciated! https://wiremock.org/docs/ If you maintainer WireMock integrations or interested in contributing, there's also a lot of opportunities to contribute integration tests and patches for new features and WireMock 3 compatibility. For any contributions, or if you need a hint on what to work on, join the #help-contributing channel! ā€¢ Documentation: https://wiremock.org/docs/ ā€¢ Changelog: https://github.com/wiremock/wiremock/releases/tag/3.0.0 ā€¢ Extension compatibility: https://github.com/wiremock/wiremock/issues/2323 ā€¢ Open tickets for WireMock 3: https://github.com/orgs/wiremock/projects/5
šŸŽ‰ 6
b
@Oleg Nenashev I see the updates you posted above and I see on Docker Hub there were updates around the same time (8 hours ago things say as I write this). wiremock/wiremock - Docker Image | Docker Hub But Iā€™m confused why the Docker Hub page says the latest is v2.32.0 from Dec 2021 and none of the later 2.3x.x updates (and of course 3.0.0). Though I do see in Docker Desktop when I search for WireMock the newer list. And if I click on tags. I think it just reads better to show on the main Docker Hub page the latest version.
o
This is an issue with updating the readme page on DockerHub
šŸ‘šŸ» 1
The tags themselves are uploaded. I will fix the page
šŸ‘šŸ» 1
b
OK, since I grabbed the container and brought it into my local Docker Desktop, I clicked on the image and Docker Scout (Early Access) popped up with some potentially scary vulverabilities. Please see the attached screen shot. I see runc is at version 1.1.9.
o
It is very much possible. Eclipse Temurin Docker images have no objective to be CVE-clean
So yeah, we could do another image focused on CVE cleaning ness, e.g. based on Wolfi or ROCKs