Updating gems to non-yanked versions

[tyler-ball]

Description

Related Issue

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Chore (non-breaking change that does not add functionality or fix an issue)

Checklist:

• I have read the CONTRIBUTING document.
• I have run the pre-merge tests locally and they pass.
• I have updated the documentation accordingly.
• I have added tests to cover my changes.
• All new and existing tests passed.
• All commits have been signed-off for the Developer Certificate of Origin.

[jonsmorrow]

LGTM. DO we need to do dk 3 as well? Also would like to make sure we ad-hoc these before merging.

[tyler-ball]

Ad-hoc builds are running, and as we discussed offline we only need to update DK3 if we want to push out a new release. In the event that we had to do a security fix we would need to update this as well but I vote we wait for that need

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.