Computing the next SemVer for dlang packages with dsemver
Sönke Ludwig
sludwig at outerproduct.org
Wed Oct 21 17:58:53 UTC 2020
Am 21.10.2020 um 17:34 schrieb Robert burner Schadek:
> On Wednesday, 21 October 2020 at 15:27:46 UTC, Sönke Ludwig wrote:
>
>> However, I definitely don't see this as a potential feature of the
>> registry in the sense that it automatically creates new versions for
>> all packages.
>
> That is why I said in an ideal world and baby steps.
The thing is just that I don't think it is possible to find a set of
rules that always work. There will always be something that should
"obviously" be flagged as a breaking change and something that is
extremely annoying to be detected as such (forcing a major version
increment).
But as some kind of warning/hint and with some kind of integration into
the version tagging process (maybe forcing a manual version release on
the registry after warnings come up) it could definitely be really nice.
>
> Also, dsemver does not call git yet to create the new tag.
More information about the Digitalmars-d-announce
mailing list