Bumps [pyyaml](https://github.com/yaml/pyyaml) from 3.11 to 5.4.
- [Release notes](https://gith...

Bumps [jinja2](https://github.com/pallets/jinja) from 2.8 to 2.11.3.
- [Release notes](https://...

Bumps [pygments](https://github.com/pygments/pygments) from 2.2.0 to 2.7.4.
- [Release notes](h...

Bumps [babel](https://github.com/python-babel/babel) from 2.2.0 to 2.9.1.
- [Release notes](htt...

This changed the formatted output, explaining the test churn.

* Ignore new stack.yaml.lock

* Use mapBuildInfo to extract common build-info fields

* Add prelude.utils.mapBuildInfo.

* dhall format dhall-to-cabal.dhall.

The pinned version is fairly old and there have been some improvements
to the generic builder s...

* Upgrade to Dhall 1.25

* Sort record fields in golden test output.

Dhall 1.25 has got bet...

The Cabal sample is the output for the Dhall sample with comments removed.

* Use Dhall.Lint to simplify --print-type and --print-default.

Unconditionally adding a bindi...

runUnion stops GHC helping us out with case exhaustivity checking.

In the course of making th...

The files are identical, and the decider in favour of doing it this
way around is that SBI was ...

Previously, we'd unconditionally try to substitute in or bind the
variable, but this could go w...

As discussed in #150 (see comments).

Setting an unknown license with cabal spec < 2.0 threw a...

Should've done this as part of #149 - ah well. I did make sure it
worked on the other two build...

Various small improvements from @jneira

Now it's easy to generate a `.cabal` file with the expected name,
instead of having to manually...

On cabal-install-2.4, using cabal-version 2.2 means that a lot of
extra-source-files don't get ...

There are actually no breaking API changes this release that I can see (1.3.0.0...master), so th...

This is mostly just updating the Dhall enumerations for things,
fortunately.

Closes #128.

Issue #124 demonstrates a problem where an alpha-normalized expression
no longer works with dha...

Previously, only the `ModuleRenaming` case was handled. However, there
are two other cases: `De...

Fixes commercialhaskell/stackage#3899.

By necessity this bumps us to Dhall 1.16, as well.

Closes #114

`cabal-to-dhall` has recently learned the default values of
fields. Now `dhall-to-cabal` is abl...

trasforming -> transforming
lanugage -> language

This should have been 2.2 but I must have mis-accepted the tests
during all the rebasing. Oops.

In Cabal 2.2, build-type inference works for 99% of cases and it is
pretty nice. However, if we...

This implements using defaults to omit boring fields for Package,
Executable, Library, Benchmar...

Cabal always reports a `.cabal` file missing the `license` field as
having a license of SPDX.NO...

* Move things that aren't types out of dhall/types

Mostly, these are the functions operating ...

* add mapping over source repos of a project

* add SourceRepo type

* Add constructors for ...

Also expose parseGenericPackageDescriptionThrows, a new convenience function.

This is useful ...

This removes a use of runUnion (#84) and produces much friendlier
output.

Originally part of...

It's a vestige from earlier development, and doesn't work with recent
versions of dhall-to-cabal.

defaults/BuildInfo.dhall already includes an other-modules field.

Also fixes a crash in cabal-to-dhall if OtherOS was used.

Hackage complains:

> Packages using 'cabal-version: 2.0' and the autogenerated module Paths_*...

* print-type: Refer to the Extension union by import.

`Extension` is fairly large and it's no...

The biggest change is the introduction of SPDX licenses, which have to
be reflected in Dhall; a...

Much like #46, this is a field that it is not sensible to do without.

This will grab the current version number from Paths_dhall_to_cabal
and then generate the URL t...

I think that this is a lot clearer about what it is doing, rather than
the previous algorithm, ...

Fixes #50.

* Fix tracking which branches are already true or false in conditionals

Previously, only one ...

I don't have the time to fix them, but we're adding new tests for new features
as we go.