Production Release 2024-07-30

[IanKrieger]

Features

• feat(graphql): replace update creative mutations #1278

Fixes

• fix(graphql): cannot pass image dimenions when updating a creative #1279
• fix: use correct verbiage for new private key #1282

[github-actions]

[puLL-Merge] - brave/ads-ui@1281

Description

This PR updates the Creative management functionality in the Brave Ads UI. It introduces new GraphQL mutations for updating creative state and payload, removes the old update mutation, and modifies the related components to use these new mutations. The PR also includes some minor changes to localization files and the key pair modal.

Changes

Changes

1. src/components/Creatives/CreativeStatusSwitch.tsx:

   • Replaced UpdateCreativeDocument with a new Creative_State_Update mutation
   • Updated the mutation call to use the new structure
   • Removed unnecessary refetch query for campaigns

2. src/components/Creatives/hooks/useSubmitCreative.tsx:

   • Replaced UpdateCreativeDocument with a new Update_Creative_Payload mutation
   • Updated the mutation call to use the new input structure
   • Removed dimensions from the payload when updating

3. src/graphql-client/gql.ts and src/graphql-client/graphql.ts:

   • Added new types and documents for the new mutations
   • Removed the old UpdateCreativeDocument

4. src/graphql/ads-serve.graphql.schema.json:

   • Added new input types for the new mutations
   • Removed userId field from various input types
   • Removed stripePaymentId from UpdateCampaignInput

5. src/graphql/creative.graphql:

   • Removed the UpdateCreative mutation

6. src/locales/*.po:

   • Updated translation for "Your account's new public key will be:" to "Your account's new private key will be:"

7. src/user/settings/NewKeyPairModal.tsx:

   • Changed the text from "public key" to "private key" in the modal

Possible Issues

• The removal of the dimensions field when updating creatives might cause issues if this field is required or used elsewhere in the application.
• The change from "public key" to "private key" in the NewKeyPairModal might be confusing for users if it's not accompanied by appropriate documentation or UI changes.

Security Hotspots

• The change from displaying a public key to a private key in the NewKeyPairModal could potentially expose sensitive information. Ensure that this change is intentional and that proper security measures are in place to protect the private key.