versions breaking changes

hackage

6 curated breaking changes across major versions of versions. Use this as a migration checklist before bumping dependencies.

6
changes
Breaking changes by transition
  • v4.0.3 \u2192 v5.0.0breaking

    **Breaking:** Like the above, the `_vMeta` field of `Version` is now `Maybe Text`.

  • v4.0.3 \u2192 v5.0.0breaking

    **Breaking: The `_vRel` and `_vMeta` fields of `Version` have had their order flipped.** Further, the prelease and meta sections are now expected in the same order as `SemVer` when parsing (prerel first, meta second). `Version` is thus now a quite similar to `SemVer`, except allowing letters in more permissive positions.

  • v4.0.3 \u2192 v5.0.0breaking

    **Breaking:** The `meta` traversal has been altered to accomodate the metadata field changes.

  • unknown \u2192 v4.0.0breaking

    **Breaking:** A `Version` now guarantees `NonEmpty` chunks.

  • unknown \u2192 v4.0.0breaking

    **Breaking:** A `Mess` now guarantees `NonEmpty` chunks, and its structure has been significantly changed. Particularly, `Mess` values are now aware of the `Int` values they hold (when they do), as well as "revision" values of the pattern `rXYZ`.

  • unknown \u2192 v4.0.0breaking

    Comparison of `Version` values is more memory efficient.

API access

Get this data programmatically \u2014 free, no authentication.

curl https://depscope.dev/api/breaking/hackage/versions
versions breaking changes — Hackage migration guide | DepScope