From 0b22275168cbe6d5ce75801e5e57f4c27c56d522 Mon Sep 17 00:00:00 2001 From: Alain Mebsout Date: Thu, 18 Dec 2025 21:11:29 +0100 Subject: [PATCH 1/4] Revert "Merge tezos/tezos!20210: scripts: add auth for sccache on protected branches" This reverts commit 6b78fb294e77ab3296ad3bb462f5a78549260588, reversing changes made to 5596d7a1bd7a30117a795fa9119501444cc94942. --- scripts/ci/sccache-start.sh | 16 ---------------- 1 file changed, 16 deletions(-) diff --git a/scripts/ci/sccache-start.sh b/scripts/ci/sccache-start.sh index 23be1c657ead..103dba7769c4 100755 --- a/scripts/ci/sccache-start.sh +++ b/scripts/ci/sccache-start.sh @@ -34,19 +34,3 @@ if [ "${attempts}" = 0 ]; then echo "Could not start sccache after ${max_attempts}, running without sccache." export RUSTC_WRAPPER="" fi - -# get access to GCS backend to store the cache on protected branches -if [ "$CI_COMMIT_REF_PROTECTED" = "true" ]; then - echo "### Logging into protected repo ..." - echo "${GCP_PROTECTED_SERVICE_ACCOUNT}" | base64 -d > protected_sa.json - gcloud auth activate-service-account --key-file=protected_sa.json - - # - GOOGLE_OAUTH_ACCESS_TOKEN=$(gcloud auth print-access-token) - export GOOGLE_OAUTH_ACCESS_TOKEN -else - echo "### Logging into standard repo ..." - # Nothing to do -fi - -echo "GCS sccache bucket: $GCP_SCCACHE_BUCKET" -- GitLab From c274e09aa2cee73d3dacaab464d214d8c9dcf75f Mon Sep 17 00:00:00 2001 From: Thomas Letan Date: Thu, 18 Dec 2025 18:12:54 +0100 Subject: [PATCH 2/4] EVM Node: Version 0.50 release --- etherlink/CHANGES_NODE.md | 25 ++++++++----------------- 1 file changed, 8 insertions(+), 17 deletions(-) diff --git a/etherlink/CHANGES_NODE.md b/etherlink/CHANGES_NODE.md index faa7bc954427..02f957ffa988 100644 --- a/etherlink/CHANGES_NODE.md +++ b/etherlink/CHANGES_NODE.md @@ -1,14 +1,16 @@ # Changelog -## Unreleased +## Version 0.50 (2025-12-19) -### Breaking changes - -### Configuration changes +This release most notably adds support for [Etherlink 6.1] native execution. In +the event of a successful governance vote, this version will be required to +preserve RPC performances. As a consequence, we strongly advise node operators +to upgrade to this version ahead of the activation of Etherlink 6.1. -### RPCs changes +This release will not apply any migration to the node's store (version +22), meaning it is possible to downgrade to the previous version. -### Monitoring changes +[Etherlink 6.1]: https://medium.com/@etherlink/announcing-etherlink-6-1-a-bugfix-proposal-for-fa-token-deposits-2cc08ffd6fad ### Command-line interface changes @@ -26,17 +28,6 @@ - Supports executing Farfadet-r1 natively. (!20285) -### Storage changes - -### Documentation changes - -### Experimental features changes - -*No guarantees are provided regarding backward compatibility of experimental -features. They can be modified or removed without any deprecation notices. If -you start using them, you probably want to use `octez-evm-node check config ---config-file PATH` to assert your configuration file is still valid.* - ## Version 0.49 (2025-12-04) This release of the EVM node makes it ready for the instant confirmation feature -- GitLab From 96e6cb5382fbb5bc49a807843aa788ca251f780d Mon Sep 17 00:00:00 2001 From: Thomas Letan Date: Thu, 18 Dec 2025 18:13:14 +0100 Subject: [PATCH 3/4] EVM Node: New section in the changelog --- etherlink/CHANGES_NODE.md | 25 +++++++++++++++++++++++++ 1 file changed, 25 insertions(+) diff --git a/etherlink/CHANGES_NODE.md b/etherlink/CHANGES_NODE.md index 02f957ffa988..4a62f8eaabc2 100644 --- a/etherlink/CHANGES_NODE.md +++ b/etherlink/CHANGES_NODE.md @@ -1,5 +1,30 @@ # Changelog +## Unreleased + +### Breaking changes + +### Configuration changes + +### RPCs changes + +### Metrics changes + +### Command-line interface changes + +### Execution changes + +### Storage changes + +### Documentation changes + +### Experimental features changes + +*No guarantees are provided regarding backward compatibility of experimental +features. They can be modified or removed without any deprecation notices. If +you start using them, you probably want to use `octez-evm-node check config +--config-file PATH` to assert your configuration file is still valid.* + ## Version 0.50 (2025-12-19) This release most notably adds support for [Etherlink 6.1] native execution. In -- GitLab From 49c32745c5927e1cae9fd2a8dc8390af46872c10 Mon Sep 17 00:00:00 2001 From: Alain Mebsout Date: Thu, 18 Dec 2025 21:49:42 +0100 Subject: [PATCH 4/4] Reapply "Merge tezos/tezos!20210: scripts: add auth for sccache on protected branches" This reverts commit 0b22275168cbe6d5ce75801e5e57f4c27c56d522. This rollbacks the previous revert to not change master and still allow for the release of the EVM node. --- scripts/ci/sccache-start.sh | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) diff --git a/scripts/ci/sccache-start.sh b/scripts/ci/sccache-start.sh index 103dba7769c4..23be1c657ead 100755 --- a/scripts/ci/sccache-start.sh +++ b/scripts/ci/sccache-start.sh @@ -34,3 +34,19 @@ if [ "${attempts}" = 0 ]; then echo "Could not start sccache after ${max_attempts}, running without sccache." export RUSTC_WRAPPER="" fi + +# get access to GCS backend to store the cache on protected branches +if [ "$CI_COMMIT_REF_PROTECTED" = "true" ]; then + echo "### Logging into protected repo ..." + echo "${GCP_PROTECTED_SERVICE_ACCOUNT}" | base64 -d > protected_sa.json + gcloud auth activate-service-account --key-file=protected_sa.json + + # + GOOGLE_OAUTH_ACCESS_TOKEN=$(gcloud auth print-access-token) + export GOOGLE_OAUTH_ACCESS_TOKEN +else + echo "### Logging into standard repo ..." + # Nothing to do +fi + +echo "GCS sccache bucket: $GCP_SCCACHE_BUCKET" -- GitLab