chore: kickoff release - #4259
Merged
Merged
Conversation
Bumps [body-parser](https://github.com/expressjs/body-parser) from 1.20.5 to 1.20.6. - [Release notes](https://github.com/expressjs/body-parser/releases) - [Changelog](https://github.com/expressjs/body-parser/blob/master/HISTORY.md) - [Commits](expressjs/body-parser@1.20.5...1.20.6) --- updated-dependencies: - dependency-name: body-parser dependency-version: 1.20.6 dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Bumps [json](https://github.com/ruby/json) from 2.19.7 to 2.19.9. - [Release notes](https://github.com/ruby/json/releases) - [Changelog](https://github.com/ruby/json/blob/master/CHANGES.md) - [Commits](ruby/json@v2.19.7...v2.19.9) --- updated-dependencies: - dependency-name: json dependency-version: 2.19.9 dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
* feat: add connect client * add unit tests to ci/cd * fix unit tests * update amplify outputs configuration parsing * address review comments * feat(connect): rework client to Option C API contract Public surface is now identifyUser(userProfile:), registerDevice(token:), and removeDevice(). All routes are SigV4-signed (Bearer token path removed; the backend derives the caller identity from the request signature, so userId is no longer sent). IdentifyUserOptions and OptOut are removed. UserProfile now carries email, name, phone, customAttributes, and location (city, country, postalCode, region). registerDevice resolves deviceId, platform, appVersion, and channelType internally, with platform derived from the target OS. Removes the now-unused AuthToken and AuthTokenProvider protocols from AmplifyFoundation and updates unit and integration tests to the new contract. * chore(connect): declare UserDefaults required-reason API in privacy manifest AmplifyConnectClient persists a device identifier in UserDefaults, so the privacy manifest now declares NSPrivacyAccessedAPICategoryUserDefaults with reason CA92.1, and the target is added to the required-reason API list in the root README. * fix(connect): declare collected data types in privacy manifest The client can transmit email address, name, phone number, coarse location (city, country, postal code, region), and a device identifier (persistent device id and push token). Each is declared as linked to identity, not used for tracking, collected for app functionality. Adds a README note that apps should narrow their app-level privacy declarations to the optional UserProfile fields they actually send. * fix(connect): enforce https endpoints and validate input lengths Endpoint hardening: configuration loading now rejects malformed or non-https endpoint URLs, and the client re-validates before every request so manually constructed configurations are covered. The SigV4 signing target (host, port, protocol) is derived from the endpoint URL instead of hardcoding port 443, so the signature is always computed over the same authority the request is sent to. Input bounds: user profile fields (email, name, phone, location fields), customAttributes keys and values, and the device token are validated against the backend's 255-character attribute limit before any network call, throwing the new ConnectError.validation case that names the offending field. Also removes the device identifier from log messages. * fix(connect): count validation lengths in UTF-16 code units to match backend * address review comments * update files * fix swiftformat issue * fix removeDevice api --------- Co-authored-by: Ekjot <43255916+ekjotmultani@users.noreply.github.com>
thisisabhash
approved these changes
Jul 30, 2026
thisisabhash
temporarily deployed
to
IntegrationTest
July 30, 2026 19:59 — with 
GitHub Actions
Inactive
GitHub Actions
Inactive
thisisabhash
temporarily deployed
to
IntegrationTest
July 30, 2026 20:00 — with
GitHub Actions
Inactive
GitHub Actions
Inactive
thisisabhash
had a problem deploying
to
IntegrationTest
July 30, 2026 20:00 — with
GitHub Actions
Error
GitHub Actions
Error
thisisabhash
temporarily deployed
to
IntegrationTest
July 30, 2026 20:00 — with
GitHub Actions
Inactive
GitHub Actions
Inactive
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
kickoff release