Move supported networks .md folder into safe-smart-accounts

.github/scripts/generateSupportedNetworks.js

@@ -29,10 +29,12 @@ const deduplicate = () => [
   []
 ]
 
+const supportedNetworksPath = './safe-smart-account/supported-networks'
+
 const generateSupportedNetworks = async () => {
   const deploymentRepoUrl = 'https://github.com/safe-global/safe-deployments/'
   shell.exec(`git clone ${deploymentRepoUrl} ./deployments`)
-  shell.rm('-rf', './supported-networks')
+  shell.rm('-rf', supportedNetworksPath)
 
   const fetch = await import('node-fetch')
   const paths = walkPath('deployments/src/assets').map(p =>
@@ -64,7 +66,7 @@ const generateSupportedNetworks = async () => {
     .reduce(...deduplicate())
     .reverse()
 
-  shell.mkdir('./supported-networks')
+  shell.mkdir(supportedNetworksPath)
 
   versions.forEach(version => {
     const _contracts = contracts.flat().filter(c => c.version === version)
@@ -111,7 +113,7 @@ ${_contracts
   .join('\n')}
 
     `
-    fs.writeFileSync(`./supported-networks/${version}.md`, content)
+    fs.writeFileSync(`${supportedNetworksPath}/${version}.md`, content)
   })
 
   shell.rm('-rf', './deployments')

safe-smart-account/supported-networks.md

@@ -1,3 +1,3 @@
 This section lists the addresses of all the Safe contracts deployed grouped by version and chain. The same list can be found on the [GitHub repository](https://github.com/safe-global/safe-deployments), from which these pages are automatically generated.
 
-The most recent version of the Safe contracts is `v1.4.1`, which adds compatibility with the ERC-4337. However, it is not supported yet in the[Safe{Wallet}](app.safe.global) interface and the Safe Transaction Service. For that reason, depending on your use case, it might be recommended to continue using `v1.3.0` until there is better support.
+The most recent version of the Safe contracts is `v1.4.1`, which adds compatibility with the ERC-4337. However, it is not supported yet in the [Safe{Wallet}](app.safe.global) interface and the Safe Transaction Service. For that reason, depending on your use case, it might be recommended to continue using `v1.3.0` until there is better support.