Skip to content

aeson 1.5 tracking issue #167859

@sternenseemann

Description

@sternenseemann

We are still building some packages with aeson 1.5 which is a slight annoyance, so let's make a list and migrate them to 2.0 one by one!

Packages still using aeson 1.5:

  • niv
  • nix-linter
  • vaultenv
  • stack
  • descriptive
  • mattermost-api, matterhorn
  • elmPackages
  • spago, bower-json
  • ghcjs

Packages that are failing because they don't support aeson 2.0 (but also haven't been overridden to use 1.5):

cc @NixOS/haskell

Metadata

Metadata

Assignees

No one assigned

    Labels

    0.kind: enhancementAdd something new or improve an existing system.3.skill: sprintableA larger issue which is split into distinct actionable tasks5.scope: trackingLong-lived issue tracking long-term fixes or multiple sub-problems6.topic: haskellGeneral-purpose, statically typed, purely functional programming language

    Projects

    Status

    Done

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions