chore(release): 5.1.0 [skip ci]

# [5.1.0](v5.0.0...v5.1.0) (2025-08-06)

### Bug Fixes

* **api:** respond with x-amz-json content type ([8ecaf40](8ecaf40)), closes [#404](#404)

### Features

* support AttributesRequireVerificationBeforeUpdate ([a0d30eb](a0d30eb)), closes [#410](#410) [#411](#411)

chore(release): 5.0.0 [skip ci]

# [5.0.0](v4.1.0...v5.0.0) (2025-03-05)

### Bug Fixes

* sub as username when using emails ([045f507](045f507))

### BREAKING CHANGES

* It's possible that users may have been stored with
their email address as their Username in the cognito-local database;
this was incorrect and shouldn't have happened. You may need to recreate
any users who were incorrectly saved with their email address as their
username.

chore(release): 4.1.0 [skip ci]

# [4.1.0](v4.0.0...v4.1.0) (2025-02-16)

### Features

* **api:** support https ([c23eefe](c23eefe))

chore(release): 4.0.0 [skip ci]

# [4.0.0](v3.23.3...v4.0.0) (2025-02-11)

* fix!: user pool creation race conditions ([69ee1e1](69ee1e1))

### BREAKING CHANGES

* You must create a User Pool before using it (by calling
createUserPool). Previously, User Pools would be created on-demand.

User Pools (and their associated databases) used to be created lazily
when first accessed, this was intended to to allow low-touch setup of
cognito-local by creating user pools with default options if they don't
exist, but it has been a source of obscure corruption issues for a
while. It's been possible to create race conditions by making requests
to cognito-local in parallel before a User Pool was created, and those
parallel requests would stomp on each other by creating multiple
databases.

This change removes the laziness: Any existing User Pools will be parsed
when cognito-local first starts, and new User Pools are created when
createUserPool is called. Any attempts to access User Pools which don't
exist will fail with a ResourceNotFound error.

chore(release): 3.23.3 [skip ci]

## [3.23.3](v3.23.2...v3.23.3) (2024-03-21)

### Bug Fixes

* add openid-configuration endpoint ([14a6507](14a6507))

chore(release): 3.23.2 [skip ci]

## [3.23.2](v3.23.1...v3.23.2) (2023-05-28)

### Bug Fixes

* **InitiateAuth:** handle UNCONFIRMED user login attempt ([93a452b](93a452b))

chore(release): 3.23.1 [skip ci]

## [3.23.1](v3.23.0...v3.23.1) (2023-03-11)

### Bug Fixes

* **api:** confirm user apis return errors for invalid states ([e2975f0](e2975f0))

chore(release): 3.23.0 [skip ci]

# [3.23.0](v3.22.0...v3.23.0) (2023-03-11)

### Bug Fixes

* **lambda:** unhandled errors in lambda return correct error message ([c9821d1](c9821d1))

### Features

* **api:** listUsers support for Filter ([5ebcf24](5ebcf24)), closes [#313](#313)

chore(release): 3.22.0 [skip ci]

# [3.22.0](v3.21.2...v3.22.0) (2023-03-10)

### Features

* **confirmationCodes:** add CODE environment variable to pre-define the confirmation codes ([2c823f0](2c823f0))
* **confirmationCodes:** update README file ([9143469](9143469))

chore(release): 3.21.2 [skip ci]

## [3.21.2](v3.21.1...v3.21.2) (2023-03-10)

### Bug Fixes

* **errorFormat:** make exception format more consistent with real Cognito exceptions ([e67576b](e67576b))
* **tests:** newer node versions were starting express in ipv6 ([efc08a7](efc08a7))