Blob Blame History Raw
<revisionlist>
  <revision rev="1" vrev="1">
    <srcmd5>f22bf9783ce58f5387e917625277cb16</srcmd5>
    <version>1.19.0</version>
    <time>1706119515</time>
    <user>anag+factory</user>
    <comment></comment>
    <requestid>1141053</requestid>
  </revision>
  <revision rev="2" vrev="1">
    <srcmd5>e92b2654e57b1ca4029ac3282ad28613</srcmd5>
    <version>1.19.2</version>
    <time>1708284275</time>
    <user>anag+factory</user>
    <comment></comment>
    <requestid>1147255</requestid>
  </revision>
  <revision rev="3" vrev="1">
    <srcmd5>3390857fa9396a708fb8aaf3504a3be6</srcmd5>
    <version>1.20.0</version>
    <time>1713724057</time>
    <user>anag+factory</user>
    <comment>- update to 1.20.0:
  * Updated `Version.bump()` to add a `smart` argument,
    which only bumps when `distance != 0`.</comment>
    <requestid>1169374</requestid>
  </revision>
  <revision rev="4" vrev="1">
    <srcmd5>018f4eeb8533b975d8dc0d9b26f032fb</srcmd5>
    <version>1.21.0</version>
    <time>1714758367</time>
    <user>anag+factory</user>
    <comment>- update to 1.21.0:
  * Generally, when Dunamai can detect the VCS in use, but
    there's no version set yet, then Dunamai uses 0.0.0 as a
    fallback, unless strict mode is enabled.
    However, if there were some tags and none matched the version
    pattern, then Dunamai would yield an error.
  * Added `--ignore-untracked` option to control checking whether
    the repository is dirty.</comment>
    <requestid>1171535</requestid>
  </revision>
</revisionlist>