An established specification still needs version control
The official page confirms the record date and specification class, rather than announcing a wholly new USB generation. Implementers should inspect the package contents and applicable engineering change notices before deciding what changed for a product.
Maintain a traceable baseline
Drawings, firmware requirements and test plans should identify the exact documents used as their baseline. A stable interface name does not remove the need to track revisions and corrections.
Why the update matters
USB 2.0 remains relevant to many charging and data-enabled products even as newer interfaces develop. Keeping document dates, revisions and engineering changes together prevents a library update from being mistaken for a universal product requirement.