https://linen.dev logo
Join Slack
Powered by
Just wanted to confirm - I believe it's already be...
# help
j
Just wanted to confirm - I believe it's already been discussed so please point me to a doc if that answers best - but is Wiremock 2.x supported any more, or will 3.x now be the only supported release?
t
We’ll backport security fixes to 2.x where vulns are discoverd (for a period of time TBD) but other than that it won’t receive any changes.
Have you encountered a tricky upgrade situation?
j
No this was purely educational to know whether I should be flagging usage of 2.x as "deprecated" or "unmaintained" for folks, that's good to know, thank you! Is there anything publicly noting that?
t
I think Oleg put a public GH issue up explaining this
j
That's very helpful thank you 👏🏽
Would you have any immediate concerns of having the supported versions listed in endoflife.date ie https://endoflife.date/keycloak - where 3.x is shown in support and 2.x is - for now - also supported, then when there's a date decided we can update there? I'm happy to keep on top of it, if you'd like, but thought I'd see how you feel about it first 😁
t
@Oleg Nenashev wdyt?
o
I have the policy for the website in the drafts
Coming soon 🙂 For the endoflife.date, indeed I can add it, but I didnf't want to do that since we reserve options for WireMock 2 at the moment. I can still add a stub there with reference to docs
t
👍
No labour required from you by the sound of it @Jamie Tanna [he/him]. Thanks for the offer though!
j
Awesome, appreciate it 👏🏽 thanks both!
o
Yeah, all set for the policy. But anything back on the documentation for WireMock 3 is appreciated, I'm currently preparing it as a main subject for Hacktoberfest
t
Speaking of which, any chance you’d be able to make it down to WireMock HQ in London on 11th of Oct @Jamie Tanna [he/him]? Would be great to say hi in person.
j
Awesome! Once that's done, I can get it wired up so it can show up as an advisory in ie dependency-management-data, a tool I've been building, so folks would get a report like https://dependency-management-data-example.fly.dev/report/advisories?organisation=wiremock that'd say "you're currently / soon using an end of life version" 😁
That sounds nice, would deffo be cool to finally say hi in person! I'll have to see schedule wise and let you know - would this be a day thing or evening?
o
We plan a Hacktoberfest Hackergarten for this day. To be announced today, hopefully
🙌 1
j
@Tom were you still planning something for the 11th? 👀
👍 1
o
@Jamie Tanna [he/him] see the social media announcements, I will put it to the chat too
t
You thinking you might be able to join us @Jamie Tanna [he/him]?
j
I may be able to swing a work visit into this as well, will have a chat with my manager today about it!
t
Excellent! 🤞
j
Sorry not sure I'll be able to make it this time - hopefully next time / soon 🤞🏽
t
Ah shame! Let us know if you manage to contrive a trip to London at any point. We’re usually around mid week.
j
Yeah I'll definitely be taking you up on it - be nice to finally meet 🙂
On the topic of supported versions - happy to create a separate thread if needbe - but did you know we've got several end-of-life/soon to be end-of-life versions of things running in the org? https://dependency-management-data-example.fly.dev/report/advisories?organisation=wiremock lists things in the org, you can ignore the 
<http://github.com/pkg/errors|github.com/pkg/errors>
ones as they're indirect dependencies
2 Views
Open in Slack
PreviousNext
Powered by