All 7 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.
chris48s
on 12 Jan 2018
@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?
julmot
on 12 Jan 2018
@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?
julmot
on 13 Jan 2018
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...
julmot
on 14 Jan 2018
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.
paulmelnikow
on 14 Jan 2018
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!
andrew
on 22 Jan 2018
Closing and hoping it won't happen again.
julmot
on 22 Jan 2018
Related issues
Fazendaaa
·
3Comments
irgolic
·
3Comments
paulmelnikow
·
3Comments
calebcartwright
·
3Comments
chadwhitacre
·
4Comments
Most helpful comment
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.