-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
Bower Badge Not up to Date #1441
Comments
The bower badge gets its data from the libraries.io api. If you have a look at the relevant page over there https://libraries.io/bower/mark.js it is reporting the version as 8.11.0 so that's what is used on the badge. I'm not sure on how often libraries.io synchronises data from various package managers or what the process is, but there is some delay there which is outside our control. |
@andrew Can you help us clarify the situation? For example, I've manually triggered re-sync yesterday: Last synced: 2018-01-11 23:18:02 UTC Also I've suggested the version update on libraries.io itself. However, it still seems not to fetch the right version? |
@andrew I've just noticed that even the npm version isn't up to date: https://libraries.io/npm/mark.js Maybe a fetching issue of libraries.io? |
LOL: This is what it says on the npm page of mark.js: I've now triggered the resync button and now the npm and also the bower version is correcty determined – even though I've already manually clicked the sync button on the bower page which leaded to no update. This is very confusing. Also it's not clear to me why a manual action is necessary at all. // UPDATE: Maybe it's related, that the hook "https://libraries.io/hooks/github" that existed in mark.js is now responding a 404. Probably worked in the past... |
Would you like to reach out to the folks at libraries.io and ask for some clarification? It would be great to have a definitive answer, for benefit of everyone else in the future... Edit: Ah, I see you did! @andrew it would be great to understand this. |
Sorry for the delay, we had a very backed up queue around the time, which might explain why there were some delays, sorry about that! |
Closing and hoping it won't happen again. |
Yesterday I've released v8.11.1 of mark.js. npm and bower installs are successfully installing the newest version and the npm badge shows the correct version. However, the bower badge shows an old version:
What could be the reason?
The text was updated successfully, but these errors were encountered: