-
Notifications
You must be signed in to change notification settings - Fork 37
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
dependabot updates for September #1796
Comments
If at all possible I'd like to resolve our Tock monitoring issues in #1792 before applying these updates, so that we'll be able to detect errors and other unexpected behavior in production when we apply these library updates. |
I'll proceed with these updates. #1792 has been resolved, we have application monitoring for Tock again, and the batch of minor package updates since June 11 2024 has been deployed. |
I've run into multiple issues trying to apply the library updates piecemeal and discussed next steps with @neilmb :
|
The Python library updates have been applied and released: https://github.com/18F/tock/releases/tag/v20241021.1 I'm still working on resolving issues with the Node library issues in #1819. |
#1819 to resolve the Node package update has been merged and looks healthy in staging so far. The primary change is to the automated testing that runs during our CircleCI build and deploy process and those jobs look healthy too. I'll kick the tires a little more and plan to release the change to production early next week. I'll also capture a follow-up ticket to investigate stabilizing our browser-based integration testing, since the current Jest/Puppeteer based setup has some brittle elements. Once that's captured and the immediate changes are fully deployed, I'll mark this ticket as resolved. |
I've opened #1822 as a follow-up issue. |
This is fully deployed to production with https://github.com/18F/tock/releases/tag/v20241031.1 . |
We have some fairly complicated library updates that need looking into:
certifi
needs to be updated but dependabot can't seem to actually create a PRThe text was updated successfully, but these errors were encountered: