You have commit messages with errors ⧗ input: Publish v3.592.0 ✖ subject may not be empty [subject-empty] ✖ type may not be empty [type-empty] ✖ found 2 problems, 0 warnings ⓘ Get help: https://github.com/conventional-changelog/commitlint/#what-is-commitlint ⧗ input: feat(client-account): This release adds 3 new APIs (AcceptPrimaryEmailUpdate, GetPrimaryEmail, and StartPrimaryEmailUpdate) used to centrally manage the root user email address of member accounts within an AWS organization. ✖ header must not be longer than 100 characters, current length is 223 [header-max-length] ✖ subject must not be sentence-case, start-case, pascal-case, upper-case [subject-case] ✖ subject may not end with full stop [subject-full-stop] ✖ found 3 problems, 0 warnings ⓘ Get help: https://github.com/conventional-changelog/commitlint/#what-is-commitlint ⧗ input: docs(client-sns): Doc-only update for SNS. These changes include customer-reported issues and TXC3 updates. ✖ header must not be longer than 100 characters, current length is 107 [header-max-length] ✖ subject must not be sentence-case, start-case, pascal-case, upper-case [subject-case] ✖ subject may not end with full stop [subject-full-stop] ✖ found 3 problems, 0 warnings ⓘ Get help: https://github.com/conventional-changelog/commitlint/#what-is-commitlint ⧗ input: feat(client-iot-wireless): Adds support for wireless device to be in Conflict FUOTA Device Status due to a FUOTA Task, so it couldn't be attached to a new one. ✖ header must not be longer than 100 characters, current length is 159 [header-max-length] ✖ subject must not be sentence-case, start-case, pascal-case, upper-case [subject-case] ✖ subject may not end with full stop [subject-full-stop] ✖ found 3 problems, 0 warnings ⓘ Get help: https://github.com/conventional-changelog/commitlint/#what-is-commitlint ⧗ input: docs(client-sqs): Doc only updates for SQS. These updates include customer-reported issues and TCX3 modifications. ✖ header must not be longer than 100 characters, current length is 114 [header-max-length] ✖ subject must not be sentence-case, start-case, pascal-case, upper-case [subject-case] ✖ subject may not end with full stop [subject-full-stop] ✖ found 3 problems, 0 warnings ⓘ Get help: https://github.com/conventional-changelog/commitlint/#what-is-commitlint ⧗ input: feat(client-location): Added two new APIs, VerifyDevicePosition and ForecastGeofenceEvents. Added support for putting larger geofences up to 100,000 vertices with Geobuf fields. ✖ header must not be longer than 100 characters, current length is 177 [header-max-length] ✖ subject must not be sentence-case, start-case, pascal-case, upper-case [subject-case] ✖ subject may not end with full stop [subject-full-stop] ✖ found 3 problems, 0 warnings ⓘ Get help: https://github.com/conventional-changelog/commitlint/#what-is-commitlint ⧗ input: feat(client-storage-gateway): Adds SoftwareUpdatePreferences to DescribeMaintenanceStartTime and UpdateMaintenanceStartTime, a structure which contains AutomaticUpdatePolicy. ✖ header must not be longer than 100 characters, current length is 174 [header-max-length] ✖ subject must not be sentence-case, start-case, pascal-case, upper-case [subject-case] ✖ subject may not end with full stop [subject-full-stop] ✖ found 3 problems, 0 warnings ⓘ Get help: https://github.com/conventional-changelog/commitlint/#what-is-commitlint ⧗ input: feat(client-firehose): Adds integration with Secrets Manager for Redshift, Splunk, HttpEndpoint, and Snowflake destinations ✖ header must not be longer than 100 characters, current length is 123 [header-max-length] ✖ subject must not be sentence-case, start-case, pascal-case, upper-case [subject-case] ✖ found 2 problems, 0 warnings ⓘ Get help: https://github.com/conventional-changelog/commitlint/#what-is-commitlint ⧗ input: feat(client-fsx): This release adds support to increase metadata performance on FSx for Lustre file systems beyond the default level provisioned when a file system

Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.