Skip to content
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

Don’t pin to specific version in README #36

Open
bramus opened this issue Nov 5, 2024 · 1 comment
Open

Don’t pin to specific version in README #36

bramus opened this issue Nov 5, 2024 · 1 comment

Comments

@bramus
Copy link

bramus commented Nov 5, 2024

Right now the README includes the library using its full version. At the time or writing that is 1.0.8

<script src="https://cdn.jsdelivr.net/npm/[email protected]/baseline-status.min.js" type="module"></script>

Because of this, authors that copy-paste the code will never receive bugfixes.

Better is to refer to only the major version, as follows:

<script src="https://cdn.jsdelivr.net/npm/baseline-status@1/baseline-status.min.js" type="module"></script>

When following semver, this should be no problem.

@bramus
Copy link
Author

bramus commented Nov 6, 2024

The site developer.chrome.com was affected by this: it was stuck using the wrong Chrome logo because it had pinned [email protected]. I had to manually update that site to load the new version, and immediately opted to load baseline-status@1 from now on so that it always has the latest 1.x version.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant