Generally speaking, third-party packages require maintenance over time to ensure proper functioning as the host product evolves. This is the responsibility of the package authors.
In the specific case of the Civil 3D Toolkit, it will require an update because there are naming clashes with the new nodes in the core product.
Putting on my non-Autodesk hat now…
I haven’t had time to test anything from Camber yet, but my expectation is that the nodes should continue to work.