Update develop branch with main

.github/workflows/release.yml

@@ -20,21 +20,21 @@ jobs:
       VERSION: ${{ github.event.inputs.tag }}
     steps:
       - name: Checkout
-        uses: actions/checkout@v3
+        uses: actions/checkout@v4
 
-      - uses: actions/setup-go@v3
+      - uses: actions/setup-go@v4
         with:
           go-version: "1.19.0"
 
       - run: chmod +x ./scripts/build-go-darwin-binaries.sh && ./scripts/build-go-darwin-binaries.sh
 
-      - uses: actions/upload-artifact@master
+      - uses: actions/upload-artifact@v4
         name: Uploading sedge darwin amd64 package
         with:
           name: sedge-${{env.VERSION}}-darwin-amd64
           path: build/sedge-${{env.VERSION}}-darwin-amd64
 
-      - uses: actions/upload-artifact@master
+      - uses: actions/upload-artifact@v4
         name: Uploading sedge darwin arm64 package
         with:
           name: sedge-${{env.VERSION}}-darwin-arm64
@@ -48,15 +48,15 @@ jobs:
     needs: sedge-darwin
     steps:
       - name: Checkout
-        uses: actions/checkout@v3
+        uses: actions/checkout@v4
 
-      - uses: actions/setup-go@v3
+      - uses: actions/setup-go@v4
         with:
           go-version: "1.21.0"
 
       - run: scripts\build-go-windows-binaries.ps1
 
-      - uses: actions/upload-artifact@master
+      - uses: actions/upload-artifact@v4
         name: Uploading sedge windows amd64 package
         with:
           name: sedge-${{env.VERSION}}-windows-amd64.exe
@@ -70,28 +70,28 @@ jobs:
     needs: sedge-windows
     steps:
       - name: Checkout
-        uses: actions/checkout@v3
+        uses: actions/checkout@v4
 
-      - uses: actions/setup-go@v3
+      - uses: actions/setup-go@v4
         with:
           go-version: "1.19.0"
 
       - name: Set up QEMU
-        uses: docker/setup-qemu-action@v2
+        uses: docker/setup-qemu-action@v3
 
       - name: Set up Docker Buildx
         id: buildx
-        uses: docker/setup-buildx-action@v2
+        uses: docker/setup-buildx-action@v3
 
       - run: chmod +x ./scripts/build-go-linux-binaries.sh && ./scripts/build-go-linux-binaries.sh
 
-      - uses: actions/upload-artifact@master
+      - uses: actions/upload-artifact@v4
         name: Uploading sedge linux amd64 package
         with:
           name: sedge-${{env.VERSION}}-linux-amd64
           path: build/sedge-${{env.VERSION}}-linux-amd64
 
-      - uses: actions/upload-artifact@master
+      - uses: actions/upload-artifact@v4
         name: Uploading sedge linux arm64 package
         with:
           name: sedge-${{env.VERSION}}-linux-arm64
@@ -105,12 +105,12 @@ jobs:
     needs: sedge-linux
     steps:
       - name: Download packages
-        uses: actions/download-artifact@v3
+        uses: actions/download-artifact@v4
         with:
           path: /tmp/binaries
 
       - name: Checkout repository
-        uses: actions/checkout@master
+        uses: actions/checkout@v4
         with:
           repository: NethermindEth/homebrew-sedge
           path: homebrew-sedge
@@ -126,7 +126,7 @@ jobs:
           token: ${{ secrets.REPOSITORY_DISPATCH_TOKEN }}
           commit-message: Update Homebrew to latest release
           title: "[Release] Update Homebrew"
-          reviewers: falcoxyz, AntiD2ta, cbermudez97, stdevMac
+          reviewers: AntiD2ta, cbermudez97, stdevMac, adriantpaez
           draft: false
           path: homebrew-sedge
           add-paths: |
@@ -140,10 +140,10 @@ jobs:
     needs: update-homebrew
     steps:
       - name: Checkout
-        uses: actions/checkout@v3
+        uses: actions/checkout@v4
 
       - name: Download packages
-        uses: actions/download-artifact@v3
+        uses: actions/download-artifact@v4
         with:
           path: /tmp/binaries
       - name: Generate Changelog
@@ -184,10 +184,10 @@ jobs:
         run: |
           sudo apt update && sudo apt install golang-go debhelper libdebhelper-perl build-essential devscripts rsync -y
       - name: Checking out Sedge repository
-        uses: actions/checkout@master
+        uses: actions/checkout@v4
         with:
           path: sedge
-      - uses: actions/setup-go@v3
+      - uses: actions/setup-go@v4
         with:
           go-version: "1.19.0"
       - name: Run publish PPA script
@@ -200,7 +200,7 @@ jobs:
       - name: Sleep for 1 hour
         run: sleep 3600s
         shell: bash
-      - uses: actions/setup-python@v4
+      - uses: actions/setup-python@v5
       - run: pip install launchpadlib --upgrade
       - name: Run copy binaries PPA script
         env:

CHANGELOG.md

@@ -7,6 +7,17 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [v1.3.1] - 2024-02-14
+
+### Fixed
+
+- Remove the Lodestar `--eth1.providerUrls` flag
+- Replace the Lighthouse `--eth1-endpoints` flag with `--eth1`.
+
+### Changed
+
+- Update client images.
+
 ## [v1.3.0] - 2023-12-11
 
 ### Added

docs/docs/commands/cli.mdx

@@ -42,7 +42,7 @@ This is an example of what you can expect:
 ```
 sedge cli
 2023-03-20 21:54:08 -- [INFO] [Logger Init] Log level: info
-2023-03-20 21:54:08 -- [INFO] You are running the latest version of sedge. Version:  v1.3.0
+2023-03-20 21:54:08 -- [INFO] You are running the latest version of sedge. Version:  v1.3.1
 ? Select network goerli
 ? Select node type full-node
 ? Generation path /root/sedge-data

docs/docs/commands/clients.mdx

@@ -31,7 +31,7 @@ The execution of `sedge clients` will result in an output like this, that will s
 ```
 $ sedge clients
 2023-10-13 14:13:44 -- [INFO] [Logger Init] Log level: info
-2023-10-13 14:13:45 -- [INFO] You are running the latest version of sedge. Version:  v1.3.0
+2023-10-13 14:13:45 -- [INFO] You are running the latest version of sedge. Version:  v1.3.1
 2023-10-13 14:13:45 -- [INFO] Listing supported clients for network chiado
 
  #   Execution Clients   Consensus Clients   Validator Clients

docs/docs/commands/deps.mdx

@@ -75,7 +75,7 @@ The execution of `sedge deps check` will result in an output like this if everyt
 ```
 $ sedge deps check
 2023-03-21 02:56:04 -- [INFO] [Logger Init] Log level: info
-2023-03-21 02:56:05 -- [INFO] You are running the latest version of sedge. Version:  v1.3.0
+2023-03-21 02:56:05 -- [INFO] You are running the latest version of sedge. Version:  v1.3.1
 2023-03-21 02:56:05 -- [INFO] docker is installed
 2023-03-21 02:56:06 -- [INFO] All dependencies are installed and running
 ```

docs/docs/commands/down.mdx

@@ -38,7 +38,7 @@ The execution of `sedge down` will close and remove all the opened containers an
 ```
 $ sedge down
 2022-00-00 00:00:00 -- [INFO] [Logger Init] Log level: info
-2022-00-00 00:00:00 -- [INFO] You are running the latest version of sedge. Version:  v1.3.0
+2022-00-00 00:00:00 -- [INFO] You are running the latest version of sedge. Version:  v1.3.1
 [sudo] password for maceo:
 [+] Running 7/7
  ⠿ Container execution-client                            Removed                                                                 93.8s

docs/docs/commands/importKey.mdx

@@ -78,7 +78,7 @@ To import the validator keys, and start the validator client after the import, r
 ```shell
 $ sedge import-key --from keystore -n sepolia --start-validator prysm
 2023-01-26 11:59:34 -- [INFO] [Logger Init] Log level: info
-2023-01-26 11:59:34 -- [INFO] You are running the latest version of sedge. Version:  v1.3.0
+2023-01-26 11:59:34 -- [INFO] You are running the latest version of sedge. Version:  v1.3.1
 # highlight-next-line
 2023-01-26 11:59:34 -- [WARN] The keys path is not the default one, copying the keys to the default path /root/sedge/example/sedge-data/keystore
 2023-01-26 11:59:34 -- [INFO] Importing validator keys

docs/docs/commands/networks.mdx

@@ -29,7 +29,7 @@ Global Flags:
 ```
 $ sedge networks
 2022-00-00 00:00:00 -- [INFO] [Logger Init] Log level: info
-2022-00-00 00:00:00 -- [INFO] You are running the latest version of sedge. Version:  v1.3.0
+2022-00-00 00:00:00 -- [INFO] You are running the latest version of sedge. Version:  v1.3.1
 2022-00-00 00:00:00 -- [INFO] Listing supported networks
 
  #   Supported Networks

docs/docs/commands/run.mdx

@@ -58,7 +58,7 @@ the following command to start all services in the default generation path
 $ sedge run
 Using config file: /root/.sedge.yaml
 2022-12-29 19:55:55 -- [INFO] [Logger Init] Logging configuration: {Level:debug}
-2022-12-29 19:55:55 -- [INFO] You are running the latest version of sedge. Version:  v1.3.0
+2022-12-29 19:55:55 -- [INFO] You are running the latest version of sedge. Version:  v1.3.1
 2022-12-29 20:40:24 -- [INFO] Checking dependencies: docker
 2022-12-29 20:40:24 -- [INFO] All dependencies are installed on host machine
 2022-12-29 19:55:55 -- [INFO] Setting up containers
@@ -109,7 +109,7 @@ start the validator.
 $ sedge run --services execution,consensus
 Using config file: /root/.sedge.yaml
 2022-12-29 21:03:29 -- [INFO] [Logger Init] Logging configuration: {Level:debug}
-2022-12-29 21:03:29 -- [INFO] You are running the latest version of sedge. Version:  v1.3.0
+2022-12-29 21:03:29 -- [INFO] You are running the latest version of sedge. Version:  v1.3.1
 2022-12-29 21:03:29 -- [INFO] Checking dependencies: docker
 2022-12-29 21:03:29 -- [INFO] All dependencies are installed on host machine
 2022-12-29 21:03:29 -- [INFO] Setting up containers
@@ -154,7 +154,7 @@ Now you can start the validator client like follow:
 $ sedge run --services validator
 Using config file: /root/.sedge.yaml
 2022-12-29 21:24:12 -- [INFO] [Logger Init] Logging configuration: {Level:debug}
-2022-12-29 21:24:12 -- [INFO] You are running the latest version of sedge. Version:  v1.3.0
+2022-12-29 21:24:12 -- [INFO] You are running the latest version of sedge. Version:  v1.3.1
 2022-12-29 21:24:12 -- [INFO] Checking dependencies: docker
 2022-12-29 21:24:12 -- [INFO] All dependencies are installed on host machine
 2022-12-29 21:24:12 -- [INFO] Setting up containers

docs/docs/commands/show.mdx

@@ -29,7 +29,7 @@ Global Flags:
 ```
 $ sedge show
 2023-00-00 00:00:00 -- [INFO] [Logger Init] Log level: info
-2023-00-00 00:00:00 -- [INFO] You are running the latest version of sedge. Version:  v1.3.0
+2023-00-00 00:00:00 -- [INFO] You are running the latest version of sedge. Version:  v1.3.1
 2023-00-00 00:00:00 -- [INFO] Showing existing containers information
 2023-00-00 00:00:00 -- [INFO] containers:
     - name: sedge-execution-client

docs/docs/commands/slashingExport.mdx

@@ -59,7 +59,7 @@ This is an example of exporting slashing protection data from a setup using sepo
 ```shell
 $ sedge slashing-export lighthouse -n sepolia --out slashing-protection.json
 2023-01-06 15:47:56 -- [INFO] [Logger Init] Log level: info
-2023-01-06 15:47:57 -- [INFO] You are running the latest version of sedge. Version:  v1.3.0
+2023-01-06 15:47:57 -- [INFO] You are running the latest version of sedge. Version:  v1.3.1
 2023-01-06 15:47:57 -- [INFO] Exporting slashing data from client lighthouse
 # highlight-next-line
 2023-01-06 15:47:57 -- [INFO] The slashing protection container is starting...
@@ -72,7 +72,7 @@ Notice in this case the validator client remains stopped because it has been sto
 ```shell
 $ sedge slashing-export lighthouse -n sepolia --out slashing-protection.json --start-validator
 2023-01-06 15:51:11 -- [INFO] [Logger Init] Log level: info
-2023-01-06 15:51:11 -- [INFO] You are running the latest version of sedge. Version:  v1.3.0
+2023-01-06 15:51:11 -- [INFO] You are running the latest version of sedge. Version:  v1.3.1
 2023-01-06 15:51:11 -- [INFO] Exporting slashing data from client lighthouse
 2023-01-06 15:51:11 -- [INFO] The slashing protection container is starting...
 2023-01-06 15:51:12 -- [INFO] The slashing container ends successfully.
@@ -87,7 +87,7 @@ Another case may be exporting the slashing data protection when the validator is
 ```shell
 $ sedge slashing-export lighthouse -n sepolia --out slashing-protection.json                  
 2023-01-06 15:51:46 -- [INFO] [Logger Init] Log level: info
-2023-01-06 15:51:46 -- [INFO] You are running the latest version of sedge. Version:  v1.3.0
+2023-01-06 15:51:46 -- [INFO] You are running the latest version of sedge. Version:  v1.3.1
 # highlight-next-line
 2023-01-06 15:51:46 -- [INFO] Stopping validator client
 # highlight-next-line
@@ -108,7 +108,7 @@ In this case, the validator client is stopped before the export and started agai
  ```shell
 $ sedge slashing-export lighthouse -n sepolia --out slashing-protection.json --stop-validator
 2023-01-06 15:52:07 -- [INFO] [Logger Init] Log level: info
-2023-01-06 15:52:07 -- [INFO] You are running the latest version of sedge. Version:  v1.3.0
+2023-01-06 15:52:07 -- [INFO] You are running the latest version of sedge. Version:  v1.3.1
 # highlight-next-line
 2023-01-06 15:52:07 -- [INFO] Stopping validator client
 # highlight-next-line

docs/docs/commands/slashingImport.mdx

@@ -58,7 +58,7 @@ This is an example of importing slashing protection data to a setup using sepoli
 ```shell
 $ sedge slashing-import prysm -f slashing-export.json -n sepolia
 2023-01-06 14:59:11 -- [INFO] [Logger Init] Log level: info
-2023-01-06 14:59:11 -- [INFO] You are running the latest version of sedge. Version:  v1.3.0
+2023-01-06 14:59:11 -- [INFO] You are running the latest version of sedge. Version:  v1.3.1
 # highlight-next-line
 2023-01-06 14:59:11 -- [INFO] Importing slashing data to client prysm from slashing-export.json
 # highlight-next-line
@@ -72,7 +72,7 @@ Notice in this case the validator client remains stopped because it has been sto
 ```shell
 $ sedge slashing-import prysm -f slashing-export.json -n sepolia --start-validator
 2023-01-06 15:08:05 -- [INFO] [Logger Init] Log level: info
-2023-01-06 15:08:06 -- [INFO] You are running the latest version of sedge. Version:  v1.3.0
+2023-01-06 15:08:06 -- [INFO] You are running the latest version of sedge. Version:  v1.3.1
 2023-01-06 15:08:06 -- [INFO] Importing slashing data to client prysm from slashing-export.json
 2023-01-06 15:08:06 -- [INFO] The slashing protection container is starting...
 2023-01-06 15:08:06 -- [INFO] The slashing container ends successfully.
@@ -87,7 +87,7 @@ Another case may be importing the slashing data protection when the validator is
 ```shell
 $ sedge slashing-import prysm -f slashing-export.json -n sepolia 
 2023-01-06 15:10:27 -- [INFO] [Logger Init] Log level: info
-2023-01-06 15:10:27 -- [INFO] You are running the latest version of sedge. Version:  v1.3.0
+2023-01-06 15:10:27 -- [INFO] You are running the latest version of sedge. Version:  v1.3.1
 # highlight-next-line
 2023-01-06 15:10:27 -- [INFO] Stopping validator client...
 # highlight-next-line
@@ -108,7 +108,7 @@ In this case, the validator client is stopped before the import and started agai
  ```shell
 $ sedge slashing-import prysm -f slashing-export.json -n sepolia --stop-validator
 2023-01-06 15:12:22 -- [INFO] [Logger Init] Log level: info
-2023-01-06 15:12:22 -- [INFO] You are running the latest version of sedge. Version:  v1.3.0
+2023-01-06 15:12:22 -- [INFO] You are running the latest version of sedge. Version:  v1.3.1
 # highlight-next-line
 2023-01-06 15:12:22 -- [INFO] Stopping validator client...
 # highlight-next-line

docs/docs/commands/version.mdx

@@ -29,6 +29,6 @@ Global Flags:
 ```
 $ sedge version
 2022-00-00 00:00:00 -- [INFO] [Logger Init] Log level: info
-2022-00-00 00:00:00 -- [INFO] You are running the latest version of sedge. Version:  v1.3.0
+2022-00-00 00:00:00 -- [INFO] You are running the latest version of sedge. Version:  v1.3.1
 sedge v0.5.1
 ```

docs/docs/quickstart/complete-guide.mdx

@@ -41,14 +41,14 @@ want to use another installation method:
   <TabItem value="curl" label="curl">
 
   ```
-  curl -L https://github.com/NethermindEth/sedge/releases/download/v1.3.0/sedge-v1.3.0-linux-amd64 --output sedge
+  curl -L https://github.com/NethermindEth/sedge/releases/download/v1.3.1/sedge-v1.3.1-linux-amd64 --output sedge
   ```
 
   </TabItem>
   <TabItem value="wget" label="wget">
 
   ```
-  wget https://github.com/NethermindEth/sedge/releases/download/v1.3.0/sedge-v1.3.0-linux-amd64 -O sedge
+  wget https://github.com/NethermindEth/sedge/releases/download/v1.3.1/sedge-v1.3.1-linux-amd64 -O sedge
   ```
 
   </TabItem>