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.