Release v4.2.2

[jemrobinson]

✅ Checklist

• You have given your pull request a meaningful title (e.g. Enable foobar integration rather than 515 foobar).
• You are targeting the appropriate branch. If you're not certain which one this is, it should be develop.
• Your branch is up-to-date with the target branch (it probably was when you started, but it may have changed since then).

🚦 Depends on

n/a

⤴️ Summary

Release candidate for v4.2.2

🌂 Related issues

Closes #1942

🔬 Tests

[jemrobinson]

@JimMadge : I think @craddm is still testing this. I've converted it to a draft so we don't merge prematurely.

[JimMadge]

@craddm Is the code ready to go?

[craddm]

Code is ready, #1993 changes the documentation

[jemrobinson]

Does this also suffer from the DockerHub issue? What's our suggested fix?

[craddm]

Yes, actually, it does, since multiple components rely on docker images running on VMs (e.g. web apps)

[jemrobinson]

One possible fix for this is to add docker login -u $DOCKER_USER -p $DOCKER_PASSWORD lines each time we call docker pull with DOCKER_USER and DOCKER_PASSWORD coming from the config file.

Thoughts?

[JimMadge]

@craddm Are the release notes ready to go?

[JimMadge]

LGTM, just a couple of Markdown suggestions.

[craddm]

@craddm Are the release notes ready to go?

Yes, think this is it. The VPN change only applies to new deployments so existing ones should continue to work without needing to update anything

[JimMadge]

LGTM, just need to update the expected output in tests.