When upgrading an old project to the current v1.8.0 packages, you might keep the following in mind.
Your project is probably an old-style .vbproj file, and not yet the new 'SDK-style' project file.
That's a big topic, but you need to be aware of the differences.
Old-style project files typically use a separate .packages.config file to specify the NuGet packages.
If you upgrade your packages while staying with the old-style project file and packages.config file, I think the only issue you need to be aware of is the post-build steps that the Excel-DNA package might have added to your project. When building after the upgrade, you might get an error because of this. If you look at the post-build steps, you can delete any that look like they come from Excel-DNA. Sometimes the .vbproj project file itself has some other entries at the bottom with version checks relating to the Excel-DNA packages. You might need to remove these too, if you have problems building after the update.
I would, however, suggest that you upgrade to an SDK-style project file. This is not a requirement for using the current Excel-DNA packages, but seems to be the recommended direction going forward, and has advantages like easier build customization, and easy editing of the project file in Visual Studio. This can be as easy as making a new project in Visual Studio (selecting the "Class Library" template and not "Class Library (.NET Framework)", setting the target runtime back to "net472" or similar to target .NET Framework, then adding the <PackageReference> entries you require. Finally, you can replace your old project file with this new one, and proceed to fix as necessary. One gotcha is that the output directory will change to now include the target framework name. For Excel-DNA, when you move to an SDK-style project file, you can also remove the .dna files that were part of your project and add the customization you had in the .dna files into your project file directly. Regarding your question from another discussion thread, if you move to an SDK-style project file, then dependencies of your packages are automatically references, so you won't need the ExcelDna.Integration package (ExcelDna.Addin brings it in) nor ExcelDna.Registration (ExcelDna.Registration.VisualBasic brings it in).
So overall, I suggest first upgrading using the existing project file, and fixing anything you run into. Then plan to do the more tricky job of updating the project file to prepare for the longer term maintenance of the project.
You're very welcome to ask here if you run into any unexpected problecmt with the update.
-Govert