Release 1.19.0

[katspaugh]

🎁 Features

• Push notifications (feat: add push notifications #2369)
  
  
• Human-readable transactions in history and queue (feat: Add human readable transfers to history and queue #2518) (A/B test)
  
  
• Sign/execute pending transactions directly from the Dashboard (Feat: actionable pending txs on the Dashboard #2523)
  
• New connect button + deprecate mobile pairing (Feat: new connect button + deprecate mobile pairing #2544)
  
• Allow safe apps to disable off-chain signing (fix: allow safe apps to disable off-chain signing #2441)

🐞 Bug fixes

• fix: use MultiSendCallOnly 1.3.0 for older Safes (fix: use MultiSendCallOnly 1.3.0 for older Safes #2528)
• fix: Update tx flow form when selecting a replacement nonce (fix: Update tx flow form when selecting a replacement nonce #2520)
• fix: close transaction modal if already on href (fix: close transaction modal if already on href #2527)
• fix: close transaction flow if Safe changes (fix: close transaction flow if Safe changes #2526)
• fix: reset nonce if outdated (fix: reset nonce if outdated #2383)
• Fix: notification center width on mobile
• Fix: [Dashboard] better layout for pending txs (Fix: [Dashboard] better layout for pending txs #2491)
• fix: use current/latest Safe deployments (fix: use current/latest Safe deployments #2467)
• style: welcome screen re-ordering enhancement for mobile view (style: welcome screen re-ordering enhancement for mobile view #2474)
• Fix: reset body scroll after mobile pairing (Fix: reset body scroll after mobile pairing #2489)
• Fix: update default value for Relay Service URL (Update default value for Relay Service URL #2488)
• Fix: Execute batch -> Bulk execute (Fix: Execute batch -> Bulk execute #2464)
• fix: populate address from URL in load Safe flow (fix: populate address from URL in load Safe flow #2451)
• fix: don't track clicks on disabled elements (fix: don't track clicks on disabled elements #2468)
• fix: adjust Ledger signatures for notifications (fix: adjust Ledger signatures for notifications #2550)

🛠️ Miscellaneous

• Attach safe address to GTM (Feat: attach safe address to analytics events #2524)
• Chore: track tx errors on Sentry (Chore: track tx errors on Sentry #2483)
• Fix: update privacy policy (Fix: update privacy policy #2542)
• fix: boolean env vars (fix: boolean env vars #2532)
• Cypress tests refactoring: PO model, safe app tests (Cypress tests refactoring: PO model, safe app tests #2522)
• Refactoring of existing Cypress tests (P2) (Refactoring of existing Cypress tests (P2) #2512)
• Refactor Cypress tests: address book and balance tests (Refactor Cypress tests: address book and balance tests #2502)

[github-actions]

CLA Assistant Lite bot:
Thank you for your submission, we really appreciate it. Like many open-source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution. You can sign the CLA by just posting a Pull Request Comment same as the below format.

---

I have read the CLA Document and I hereby sign the CLA

---

4 out of 5 committers have signed the CLA.
✅ @katspaugh
✅ @udhaykumarbala
✅ @mike10ca
✅ @KaushikKC
❌ @fmrsabino
_{You can retrigger this bot by commenting recheck in this Pull Request}

[github-actions]

Branch preview

✅ Deploy successful!

https://release_1_19_0--walletweb.review-wallet-web.5afe.dev

[github-actions]

ESLint Summary View Full Report

Annotations are provided inline on the Files Changed tab. You can also see all annotations that were generated on the annotations page.

Type	Occurrences	Fixable
Errors	0	0
Warnings	0	0
Ignored	0	N/A

• Result: ✅ success
• Annotations: 0 total

---

^{Report generated by eslint-plus-action}

[francovenica]

@iamacook
Issue notifications:
If you are not in the correct network The "Enable all" button in the top bar notification only makes me switch networks, but doesn't trigger the off-chain signature to actually enable notifications

[francovenica]

Issue:

In the global preferences for notifications, unchecking and saving only one checkbox from one network unchecks the rest of the checkboxes

[francovenica]

I'm leaving a note correcting something I said in the original Notifications EPIC:

The "Confirmation request" DOES work on safes 2/2.
Debugging with Aaron today, I've found out that Firefox is very pesky with notifications. It seems that enabling/disabling notifications constantly can create issues (service workers and the indexDB)
I decied to use chrome as the browser for control, and it seems to be much more consistent with the messages.

Another note that I didn't say in the original EPIC but is worth mentioning:
"Confirmation request" is the only type of notification that looks at the owners who are receiving it. So if an owner signed the enabling of notifications and then is kicked out of the safe, he will no longer receive notificatons about "Confirmation request", but it WILL receive notifications about "tx executions" and "Tokens received". The user can still, as a non owner, unsubscribre from these notifications types.

[iamacook]

I've found out that Firefox is very pesky with notifications. It seems that enabling/disabling notifications constantly can create issues (service workers and the indexDB) I decied to use chrome as the browser for control, and it seems to be much more consistent with the messages.

I can confirm that I get notifications in Firefox and Chrome, even after unregistering the service worker/clearing the IndexedDB. It is concerning that it is so flakey for you but I hope that the user won't have to touch either of these.

Another note that I didn't say in the original EPIC but is worth mentioning: "Confirmation request" is the only type of notification that looks at the owners who are receiving it. So if an owner signed the enabling of notifications and then is kicked out of the safe, he will no longer receive notificatons about "Confirmation request", but it WILL receive notifications about "tx executions" and "Tokens received". The user can still, as a non owner, unsubscribre from these notifications types.

We have mentioned this in the help article that will be linked to as per discussion with @kirkkonen and @TanyaEfremova.

[francovenica]

Issue:

In a brand new safe (or a safe that has never executed a transaction) the nonce field in the tx form shows the skeleton all the time and never shows the Nonce 0 as expected.
After executing that first transaction it works fine, so the issue is if the safe has to execute the nonce 0

[francovenica]

Messages are broken, the text overlaps all together. Maybe is because human-readable

This safe has messages: (turn on Prod CGW)
https://release_1_19_0--walletweb.review-wallet-web.5afe.dev/transactions/messages?safe=gor:0x0EDc6697427E9e9d62A1eE1A2951AfA7bE9e75B7

[usame-algan]

In a brand new safe (or a safe that has never executed a transaction) the nonce field in the tx form shows the skeleton all the time and never shows the Nonce 0 as expected.

Messages are broken, the text overlaps all together. Maybe is because human-readable

Nice finds! I've fixed both in #2562 and merged into this Branch

[francovenica]

The 2 issues reported where fixed

Nonce 0 is shown just fine now
The messages look fine as well

[francovenica]

The rest of the ticket is fine.

I've checked the list in the description and that can be tested in the UI look good

I've done the regression:
Safe creation and adding
Tx creation / execution with Trezor, Ledger, MM extension, MM phone app via WC, Mobile pairing
Send funds, NFT's
Safe app (tx builder)
Execution un bulk
Message signing (using epi 1271 test app)
Owner edition (adding/removin/replacing)
Spending limit creation removal usage
Address book
Import/export
Settings in general
....

[usame-algan]

recheck