Thread overview
How to get Code.dlang.org to update the package?
Feb 12
Dukc
Feb 12
Dukc
February 12
I have pushed a new release tag in Github around two weeks ago, and ordered a manual update at DUB, yet DUB has still not aknowledged the new tag. Is there some requirement for the release tag for it to be recognized?
February 12
On Wednesday, 12 February 2020 at 12:42:32 UTC, Dukc wrote:
> I have pushed a new release tag in Github around two weeks ago, and ordered a manual update at DUB, yet DUB has still not aknowledged the new tag. Is there some requirement for the release tag for it to be recognized?

Hi Dukc,

I'm not sure which dub package you're referring to, but I'm gonna guess that it's this one: http://code.dlang.org/packages/nuklearbrowser, which corresponds to this github repo: https://github.com/dukc/nuklearbrowser. I think the problem is that your latest tag is 0.0.2, instead of v0.0.2 (https://github.com/dukc/nuklearbrowser/tags).

I hope this helps!

Cheers,
Petar
February 12
On Wednesday, 12 February 2020 at 13:05:00 UTC, Petar Kirov [ZombineDev] wrote:
> On Wednesday, 12 February 2020 at 12:42:32 UTC, Dukc wrote:
>> I have pushed a new release tag in Github around two weeks ago, and ordered a manual update at DUB, yet DUB has still not aknowledged the new tag. Is there some requirement for the release tag for it to be recognized?
>
> Hi Dukc,
>
> I'm not sure which dub package you're referring to, but I'm gonna guess that it's this one: http://code.dlang.org/packages/nuklearbrowser, which corresponds to this github repo:
> https://github.com/dukc/nuklearbrowser.

Correct

> I think the problem is that your latest tag is 0.0.2, instead of v0.0.2 (https://github.com/dukc/nuklearbrowser/tags).
>
> I hope this helps!
>
> Cheers,
> Petar

Certainly does, thank you.