2.0.0 (2023-07-28)

The Amazonka team would like to announce the full 2.0.0 release now available on Hackage. There's a lot of work in here, many thanks to all the contributors past and present for getting this over the line. With this release finally out the door we hope to return to a healthy cadence of Hackage releases.

For those still using the 1.6.1 version from Hackage, many things have changed. If you haven't been following along with the release candidate process some suggested reading is the migration guide for an overview and the CHANGELOG for full details.

Please file any feedback under the related GitHub discussion or create a new issue.

2.0.0-rc2 (2023-07-10)

The Amazonka team would like to announce the availability of the final release candidate for the upcoming 2.0.0 release. This release contains many more bug fixes and AWS service updates since rc1, including:

• An overhaul of the authentication-related code.
• A new hooks system for clients to inject custom behavior into the request/response lifecycle.
• Nix Flakes (with cabal) are used for development of the library.
• The cryptonite dependency has been replaced with crypton.

Please read the Amazonka CHANGELOG.md for a high-level overview of all the other changes included in the release candidate.

To test the release, you will need to add a source-repository-package section to your cabal.project file for amazonka itself, and for any service libraries you use (amazonka-sts and amazonka-sso are now dependencies of amazonka because of sts:AssumeRoleWithWebIdentity and SSO support):

-- For amazonka
-- Multiple subdirs in a single `source-repository-package` stanza are supported by cabal-install >= 3.2.0.0.
source-repository-package
    type: git
    location: https://github.com/brendanhay/amazonka
    tag: 31f3d044d84912b99e396a97085a9678e699d91f
    subdir: lib/amazonka lib/amazonka-core lib/services/amazonka-sso lib/services/amazonka-sts lib/services/amazonka-<servicename>

Stack users should use an extra-deps: stanza like this:

extra-deps:
- github: brendanhay/amazonka
  commit: 31f3d044d84912b99e396a97085a9678e699d91f
  subdirs:
  - lib/amazonka
  - lib/amazonka-core
  - lib/services/amazonka-sso
  - lib/services/amazonka-sts
  - lib/services/amazonka-<servicename>

Stack users who also use haskell.nix will need to tell haskell.nix which branch to fetch Amazonka commits from by passing a branchMap parameter like this:

pkgs.haskell-nix.project {
  branchMap = {
    "https://github.com/brendanhay/amazonka.git" = {
      31f3d044d84912b99e396a97085a9678e699d91f = "main";
    };
  };

  # Whatever else you normally have here
  src = ...
}

Please file any feedback from testing under the related discussion so the team can finalize the 2.0.0 release.

2.0.0-rc1 (2021-11-28)

The Amazonka team is happy to announce the availability of the first release candidate for the upcoming 2.0.0 release. This release collects the past few years' worth of bug fixes and AWS service updates, and also includes some fairly major changes to repository organisation and conventions. Some of the highlighted changes include:

• Sum types for enumerations have been replaced with pattern synonyms over Text, this makes all sum types trivially extensible - no more deserialisation errors when EC2 adds new instance types, regions, etc.
• The core Network.AWS namespace has been renamed to Amazonka to match the package.
• Record field names now match the documentation (where possible) and are no longer prefixed - it is now recommended to use generic-lens or optics packages to modify fields, but generated lenses are still provided for compatibility in each respective Amazonka.<Service>.Lens.
• The main branch is now the singular source of truth. master + develop will continue to exist in their current state(s), but no further commits will occur on these branches.
• Work has been done to reduce the amount of memory used when compiling large service libraries such as amazonka-ec2.

Please read the Amazonka CHANGELOG.md for a high-level overview of all the other changes included in the release.

Because of the magnitude of the accumulated changes, we are now entering a stabilisation period before we release to Hackage. During this period, we'd greatly appreciate people testing amazonka against their projects, and reporting issues against the 2.0 milestone. We are aiming for a four-week stabilisation period, but may shorten or lengthen this depending on the volume of issues raised.

The large number of changes and improvements is thanks to all of the individuals who contributed to this release. Big thanks to everyone involved and in particular @endgame for their work driving everything forward.

You can view the latest Haddock documentation which is built against the main branch and published at https://amazonka.brendanhay.nz/ .

To test the release, you will need to add a source-repository-package section to your cabal.project file for amazonka itself, and for any service libraries you use (amazonka-sts is now a dependency of amazonka because of AssumeRoleWithWebIdentity support):

-- For amazonka
-- Multiple subdirs in a single `source-repository-package` stanza are supported by cabal-install >= 3.2.0.0.
source-repository-package
    type: git
    location: https://github.com/brendanhay/amazonka
    tag: 0ccede621e56fb6f240e4850e205cde82d0e4a4b
    subdir: lib/amazonka lib/amazonka-core lib/services/amazonka-sts lib/services/amazonka-<servicename>

Stack users should use an extra-deps: stanza like this:

extra-deps:
- github: brendanhay/amazonka
  commit: 0ccede621e56fb6f240e4850e205cde82d0e4a4b
  subdirs:
  - lib/amazonka
  - lib/amazonka-core
  - lib/services/amazonka-sts
  - lib/services/amazonka-<servicename>