fix: Create contract artifacts and add them to releases (matter-labs#1630)

Author: mm-zk

.github/workflows/build-release.yaml

@@ -1,17 +1,16 @@
-name: Build and release(manual)
+name: Build and release(manual & tags)
 
 on:
   workflow_dispatch:
     inputs:
-      commit:
+      tag:
         type: string
-        description: SHA commit for build
-        required: false
-      prefix:
-        type: string
-        description: Prefix for release name
-        required: false
-        default: manual
+        description: tag to build from
+        required: true
+  create:
+    tags:
+      - "v*" # for main releases
+      - "zkos*" # for zk releases
 
 permissions:
   contents: write
@@ -21,10 +20,21 @@ jobs:
     runs-on: ubuntu-latest
 
     steps:
+      - name: Resolve tag
+        id: vars
+        run: |
+          if [ "${{ github.event_name }}" = "workflow_dispatch" ]; then
+            echo "TAG=${{ inputs.tag }}" >> $GITHUB_OUTPUT
+          else
+            # For push/create on a tag, github.ref looks like 'refs/tags/<tag>'
+            echo "TAG=${GITHUB_REF#refs/tags/}" >> $GITHUB_OUTPUT
+          fi
+          echo "Resolved TAG=${{ steps.vars.outputs.TAG }}"
+
       - name: Checkout the repository
         uses: actions/checkout@v4
         with:
-          ref: ${{ inputs.commit }}
+          ref: ${{ steps.vars.outputs.TAG }}
           submodules: recursive
 
       - name: Install foundry-zksync
@@ -45,7 +55,6 @@ jobs:
         id: init
         run: |
           yarn
-          echo "release_tag=${{ inputs.prefix }}-${{ inputs.commit }}" >> $GITHUB_OUTPUT
 
       - name: Build l1 contracts
         working-directory: l1-contracts
@@ -70,12 +79,10 @@ jobs:
           tar -czvf system-contracts.tar.gz ./system-contracts
 
       - name: Release
-        uses: softprops/action-gh-release@v1
+        uses: softprops/action-gh-release@v2
         with:
-          tag_name: ${{ steps.init.outputs.release_tag }}
+          tag_name: ${{ steps.vars.outputs.TAG }}
           fail_on_unmatched_files: true
-          target_commitish: ${{ inputs.commit }}
-          body: ""
           files: |
             l1-contracts.tar.gz
             l2-contracts.tar.gz

.gitignore

@@ -35,3 +35,4 @@ l1-contracts/test/foundry/l1/integration/deploy-scripts/script-config/config-dep
 l1-contracts/test/foundry/integration/deploy-scripts/script-out/*
 l1-contracts/test/foundry/l1/integration/upgrade-envs/script-out/*.toml
 l1-contracts/zkout/*
+.lycheecache

_typos.toml

@@ -16,6 +16,8 @@ extend-exclude = [
     "*.json",
     "*.lock",
     ".git/",
+    # Typo inside (unaccessible vs inaccessible) fix before v30.
+    "/system-contracts/contracts/abstract/SystemContractBase.sol",
     "SECURITY.md"
 ]
 

docs/evm_emulation/technical_overview.md

@@ -44,7 +44,7 @@ Additionally EVM contracts can be deployed from EraVM environment using **system
 - `createEVM` - `CREATE`-like behavior
 - `create2EVM` - `CREATE2`-like behavior
 
-They use the same address derivation schemes as corresponding EVM opcodes. To derive the deployed contract’s address for EOAs we use the main nonce for this operation, while for contracts we use their deployment nonce. You can read more about the two types of nonces in the [NonceHolder system contract’s documentation](https://docs.zksync.io/build/developer-reference/era-contracts/system-contracts#nonceholder).
+They use the same address derivation schemes as corresponding EVM opcodes. To derive the deployed contract’s address for EOAs we use the main nonce for this operation, while for contracts we use their deployment nonce. You can read more about the two types of nonces in the [NonceHolder system contract’s documentation](https://docs.zksync.io/zksync-protocol/contracts/system-contracts#nonceholder).
 
 ❗ Note, that these two functions are not used (and can’t be used!) from the EVM environment. EVM smart contracts can’t perform **system** calls. EVM opcodes `CREATE` and `CREATE2` should be used instead.