On Saturday, 20 November 2021 at 01:01:05 UTC, rikki cattermole
wrote:
Don't use ~> for branches.
...
Thank you very much. I edited the dub.json, and that fixed the
problem(anyways, there is no longer a "testing" branch, so that
would have also been an issue.)
Don't use ~> for branches.
alpha@DESKTOP-RB97SA4 /tmp/dutils
$ dub build
Invalid SemVer format: stable.0.0
alpha@DESKTOP-RB97SA4 /tmp/dutils
$ nano dub.json
alpha@DESKTOP-RB97SA4 /tmp/dutils
$ dub build
Performing "debug" build using
C:\Tools\D\dmd_2.097.2\windows\bin\dmd.exe for x86_64.
On Friday, 12 November 2021 at 21:22:32 UTC, Ruby The Roobster
wrote:
On Thursday, 11 November 2021 at 01:57:10 UTC, rikki cattermole
wrote:
On 11/11/2021 2:13 PM, Ruby The Roobster wrote:
Branch ~master: Invalid SemVer format: testing.0.0
Branch ~testing: Invalid SemVer format: testing.0.0
Ve
On Thursday, 11 November 2021 at 01:57:10 UTC, rikki cattermole
wrote:
On 11/11/2021 2:13 PM, Ruby The Roobster wrote:
Branch ~master: Invalid SemVer format: testing.0.0
Branch ~testing: Invalid SemVer format: testing.0.0
Version 0.1.2: Invalid SemVer format: testing.0.0
testing is a branch.
On 11/11/2021 2:13 PM, Ruby The Roobster wrote:
Branch ~master: Invalid SemVer format: testing.0.0
Branch ~testing: Invalid SemVer format: testing.0.0
Version 0.1.2: Invalid SemVer format: testing.0.0
testing is a branch.
You are using ~>testing for it.
To use a branch in the SEMVER is ~bra
# Dub says that there is an invalid semVer format, but I don't
see how.
[Relevant Package:](https://code.dlang.org/packages/dutils)
Recently, I added a new tag: v0.1.2 to the github repo, as well
as v0.1.2-rc.1(this was later removed.) Now whenever updating the
package, dub gives me
