Pointing to a specific version prevents to introduce breaking changes of major releases. Users should switch to a new major release carefully, reading release notes and looking at the final result on their published documents.
For example, replace https://unpkg.com/@nextbitlabs/rapido@latest/rapido.css with https://unpkg.com/@nextbitlabs/rapido@3.1.0/rapido.css. Using semver range, we could also point to https://unpkg.com/@nextbitlabs/rapido@^3/rapido.css for targeting versions >=3.0.0 <4.0.0.
Pointing to a specific version prevents to introduce breaking changes of major releases. Users should switch to a new major release carefully, reading release notes and looking at the final result on their published documents.
For example, replace
https://unpkg.com/@nextbitlabs/rapido@latest/rapido.csswithhttps://unpkg.com/@nextbitlabs/rapido@3.1.0/rapido.css. Using semver range, we could also point tohttps://unpkg.com/@nextbitlabs/rapido@^3/rapido.cssfor targeting versions >=3.0.0 <4.0.0.That line should be updated at each new release.