Why isn't the repository version updated in Package Control?

[punkochel]

Pawn Kit repository

Pawn Kit is at https://packagecontrol.io/channel_v3.json version 1.0.7, but it was updated to version 1.1.0 three weeks ago. I couldn't find any information on how to fix this.

[Haiquan-27]

I noticed that other packages also have similar issues. Is there a problem with obtaining the version tag?

[punkochel]

I didn't quite get you. I made the tag version as in previous releases. Then everything worked without problems.
Although this time I changed the minor version, before that I only changed the patch number in the semantic version.

[haroon26]

I noticed the same issue when I updated Rails Migration Boy last week. Later I found this: https://forum.sublimetext.com/t/package-control-not-showing-our-latest-release/75589/2

[GottemHams]

The last post in that thread says updates work again, but I still see https://github.com/sublimelsp/LSP-intelephense listed at 1.2.4 instead of 1.3.2. There are a couple of releases from as recent as 2025-03-27 though, which is even another LSP plugin: https://github.com/sublimelsp/LSP-basedpyright. The only real difference I see at a quick glance is that working repos do not use the v prefix for tags, while all of the problematic plugins mentioned in this issue do use it. Dunno if it even makes a difference, but it's at least peculiar.

[haroon26]

@GottemHams it is true that not all packages have got updated including mine as well, but the issue might be something different from this version convention. Like take example of this reported issue, Pawn Kit repository is now showing the latest version in sublime package control list while it's version starts with 'v'

[FichteFoll]

There is a known issue currently with the crawler not being able to catch up. The exact cause is not yet known but only @wbond can look into it atm and he is quite busy with non-computer stuff. A handover to @sublimehq is in the works but also not yet completed.

[GottemHams]

@haroon26 Too bad, I was kinda hoping it could be a way for anyone but Will to fix this from their own ends in the meantime. ;_;

[haroon26]

@FichteFoll I have updated OS support of my plugin and PR's been merged around 3 weeks ago but it is not reflecting in channel. Is this due to the same issue or should I report a separate one?

[FichteFoll]

Likely. I suggest to wait until this issue is resolved and open a new one if that is not resolved as well.

[michaelblyons]

Fixed, no?