Hardhat@3.1.9 #7947

.changeset/beige-ladybugs-confess.md

@@ -0,0 +1,6 @@
+---
+"hardhat": patch
+---
+
+Added a notification when a new Hardhat version is available
+

.changeset/bright-onions-switch.md

@@ -0,0 +1,5 @@
+---
+"@nomicfoundation/hardhat-chai-matchers": patch
+---
+Added support for Typed objects (thanks @RenanSouza2!)
+

.changeset/curvy-cherries-beg.md

@@ -0,0 +1,7 @@
+---
+"@nomicfoundation/hardhat-chai-matchers": patch
+"hardhat": patch
+"@nomicfoundation/hardhat-viem": patch
+---
+
+Improved loading performance

.changeset/dry-pianos-scream.md

@@ -0,0 +1,5 @@
+---
+"hardhat": patch
+---
+
+Fixed a bug during project initialization when using yarn or pnpm

.changeset/modern-fishes-look.md

@@ -0,0 +1,6 @@
+---
+"hardhat": patch
+---
+
+Added a fix to prevent submitting transactions with 0 priority fee (thanks @itsdevbear!)
+

.changeset/twelve-mails-heal.md

@@ -0,0 +1,5 @@
+---
+"@nomicfoundation/hardhat-verify": patch
+---
+Added support for programmatic verification in Sourcify
+

.circleci/config.yml

@@ -0,0 +1,32 @@
+# Use the latest 2.1 version of CircleCI pipeline process engine.
+# See: https://circleci.com/docs/configuration-reference
+version: 2.1
+
+# Define a job to be invoked later in a workflow.
+# See: https://circleci.com/docs/jobs-steps/#jobs-overview & https://circleci.com/docs/configuration-reference/#jobs
+jobs:
+  say-hello:
+    # Specify the execution environment. You can specify an image from Docker Hub or use one of our convenience images from CircleCI's Developer Hub.
+    # See: https://circleci.com/docs/executor-intro/ & https://circleci.com/docs/configuration-reference/#executor-job
+    docker:
+      # Specify the version you desire here
+      # See: https://circleci.com/developer/images/image/cimg/base
+      - image: cimg/base:current
+
+    # Add steps to the job
+    # See: https://circleci.com/docs/jobs-steps/#steps-overview & https://circleci.com/docs/configuration-reference/#steps
+    steps:
+      # Checkout the code as the first step.
+      - checkout
+      - run:
+          name: "Say hello"
+          command: "echo Hello, World!"
+
+# Orchestrate jobs using workflows
+# See: https://circleci.com/docs/workflows/ & https://circleci.com/docs/configuration-reference/#workflows
+workflows:
+  say-hello-workflow: # This is the name of the workflow, feel free to change it to better match your workflow.
+    # Inside the workflow, you define the jobs you want to run.
+    jobs:
+      - say-hello
+

.devcontainer/devcontainer.json

@@ -0,0 +1,15 @@
+{
+  "name": "Hardhat + EDR",
+  "image": "mcr.microsoft.com/devcontainers/base:bullseye",
+  "features": {
+    "ghcr.io/devcontainers/features/node:1": {
+      "version": "16" /* Keep in sync with the oldest version of Node.js that Hardhat supports */
+    },
+    "ghcr.io/devcontainers/features/rust:1": {
+      "version": "1.70" /* Keep in sync with rust-toolchain */,
+      "profile": "default"
+    }
+  },
+  /* libudev-dev is required by hardhat-ledger. pkg-config is required by EDR to use OpenSSL */
+  "postCreateCommand": "sudo apt update && sudo apt install -y libudev-dev pkg-config"
+}

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,35 @@
+---
+name: Bug report
+about: Create a report to help us improve
+title: ""
+labels: ""
+assignees: ""
+---
+
+**Describe the bug** A clear and concise description of what the bug is.
+
+**To Reproduce** Steps to reproduce the behavior:
+
+1. Go to '...'
+2. Click on '....'
+3. Scroll down to '....'
+4. See error
+
+**Expected behavior** A clear and concise description of what you expected to happen.
+
+**Screenshots** If applicable, add screenshots to help explain your problem.
+
+**Desktop (please complete the following information):**
+
+- OS: [e.g. iOS]
+- Browser [e.g. chrome, safari]
+- Version [e.g. 22]
+
+**Smartphone (please complete the following information):**
+
+- Device: [e.g. iPhone6]
+- OS: [e.g. iOS8.1]
+- Browser [e.g. stock browser, safari]
+- Version [e.g. 22]
+
+**Additional context** Add any other context about the problem here.

.github/ISSUE_TEMPLATE/custom.md

@@ -0,0 +1,7 @@
+---
+name: Custom issue template
+about: Describe this issue template's purpose here.
+title: ""
+labels: ""
+assignees: ""
+---

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,15 @@
+---
+name: Feature request
+about: Suggest an idea for this project
+title: ""
+labels: ""
+assignees: ""
+---
+
+**Is your feature request related to a problem? Please describe.** A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
+
+**Describe the solution you'd like** A clear and concise description of what you want to happen.
+
+**Describe alternatives you've considered** A clear and concise description of any alternative solutions or features you've considered.
+
+**Additional context** Add any other context or screenshots about the feature request here.

.github/ISSUE_TEMPLATE/other-issue.md

@@ -1,4 +1,7 @@
 ---
 name: Other issue
 about: Other kind of issue. Please don't use this to ask questions.
+title: ""
+labels: ""
+assignees: ""
 ---

.github/workflows/Compile-with-typescript-v4.yml

@@ -0,0 +1,34 @@
+name: Compile with typescript v4
+permissions:
+  contents: read
+
+on:
+  push:
+    branches: main
+  pull_request:
+    branches:
+      - "**"
+  workflow_dispatch:
+
+jobs:
+  compile_with_typescript_v4:
+    name: Compile with typescript v4
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v2
+      - uses: pnpm/action-setup@v2
+        with:
+          version: 8
+      - uses: actions/setup-node@v2
+        with:
+          node-version: 16
+          cache: "pnpm"
+      - name: Remove packages that can't be compiled with TypeScript v4
+        run: rm -fr packages/hardhat-viem packages/hardhat-toolbox-viem packages/hardhat-web3-v4
+      - name: Remove packages that can't be compiled with TypeScript v4 from the build script
+        run: sed -i 's/packages\/\(hardhat-viem\|hardhat-toolbox-viem\|hardhat-web3-v4\) *//g' package.json
+      - name: Install typescript v4 in all packages
+        run: |
+          sed -i 's/"typescript": "~5.0.0"/"typescript": "^4.0.0"/' package.json packages/*/package.json && pnpm install --no-frozen-lockfile
+      - name: Build
+        run: pnpm build

.github/workflows/LATEST_DEPENDENCY_VERSIONS.yml

@@ -6,28 +6,32 @@ on:
   workflow_dispatch:
 
 jobs:
-  test-without-yarn-lock:
-    name: Test without yarn.lock
+  test-without-pnpm-lock-yaml:
+    name: Test without pnpm-lock.yaml
     strategy:
       matrix:
         system: ["ubuntu-latest", "windows-latest"]
     runs-on: ${{ matrix.system }}
     steps:
-      - uses: actions/setup-node@v2
-        with:
-          node-version: 14
       - uses: actions/checkout@v2
-      - name: Delete yarn.lock
-        run: "rm yarn.lock"
+      - uses: pnpm/action-setup@v2
+        with:
+          version: 9
+      - uses: actions/setup-node@v3
+        with:
+          node-version: 20
+          cache: "pnpm"
+      - name: Delete pnpm-lock.yaml
+        run: "rm pnpm-lock.yaml"
       - name: Install
-        run: yarn
+        run: pnpm install --no-frozen-lockfile
       - name: List dependencies
-        run: yarn list
+        run: pnpm list -r --depth 2
       - name: Run tests
         env:
           DO_NOT_SET_THIS_ENV_VAR____IS_HARDHAT_CI: true
           FORCE_COLOR: 3
-        run: yarn test || (echo "===== Retry =====" && yarn test)
+        run: pnpm test || (echo "===== Retry =====" && pnpm test)
       - name: Notify failures
         if: failure()
         uses: slackapi/slack-github-action@v1.18.0

.github/workflows/add-label-to-new-issue.yml

@@ -21,17 +21,18 @@ jobs:
               repo: context.issue.repo,
               issue_number: context.issue.number
             });
-
             const statusLabel = issue.data.labels.find(({ name }) =>
               name.startsWith("status:")
             );
-
             if (statusLabel === undefined) {
+              console.log("Author association:", issue.data.author_association);
+              const isCollaborator = ["OWNER", "MEMBER", "COLLABORATOR"].includes(issue.data.author_association)
+              const label = isCollaborator ? "status:ready" : "status:triaging"
               await github.rest.issues.addLabels({
                 owner: context.issue.owner,
                 repo: context.issue.repo,
                 issue_number: context.issue.number,
-                labels: ["status:triaging"]
+                labels: [label]
               });
             } else {
               console.log(`Issue already has a status: ${statusLabel.name}`);

.github/workflows/apisec-scan.yml

@@ -0,0 +1,71 @@
+# This workflow uses actions that are not certified by GitHub.
+# They are provided by a third-party and are governed by
+# separate terms of service, privacy policy, and support
+# documentation.
+
+# APIsec addresses the critical need to secure APIs before they reach production.
+# APIsec provides the industry’s only automated and continuous API testing platform that uncovers security vulnerabilities and logic flaws in APIs.
+# Clients rely on APIsec to evaluate every update and release, ensuring that no APIs go to production with vulnerabilities.
+
+# How to Get Started with APIsec.ai
+# 1. Schedule a demo at https://www.apisec.ai/request-a-demo .
+#
+# 2. Register your account at https://cloud.apisec.ai/#/signup .
+#
+# 3. Register your API . See the video (https://www.youtube.com/watch?v=MK3Xo9Dbvac) to get up and running with APIsec quickly.
+#
+# 4. Get GitHub Actions scan attributes from APIsec Project -> Configurations -> Integrations -> CI-CD -> GitHub Actions
+#
+# apisec-run-scan
+#
+# This action triggers the on-demand scans for projects registered in APIsec.
+# If your GitHub account allows code scanning alerts, you can then upload the sarif file generated by this action to show the scan findings.
+# Else you can view the scan results from the project home page in APIsec Platform.
+# The link to view the scan results is also displayed on the console on successful completion of action.
+
+# This is a starter workflow to help you get started with APIsec-Scan Actions
+
+name: APIsec
+
+# Controls when the workflow will run
+on:
+  # Triggers the workflow on push or pull request events but only for the "main" branch
+  # Customize trigger events based on your DevSecOps processes.
+  push:
+    branches: [ "main" ]
+  pull_request:
+    branches: [ "main" ]
+  schedule:
+    - cron: '31 16 * * 2'
+
+  # Allows you to run this workflow manually from the Actions tab
+  workflow_dispatch:
+
+
+permissions:
+  contents: read
+
+jobs:
+
+  Trigger_APIsec_scan:
+    permissions:
+      security-events: write # for github/codeql-action/upload-sarif to upload SARIF results
+      actions: read # only required for a private repository by github/codeql-action/upload-sarif to get the Action run status
+    runs-on: ubuntu-latest
+
+    steps:
+       - name: APIsec scan
+         uses: apisec-inc/apisec-run-scan@025432089674a28ba8fb55f8ab06c10215e772ea
+         with:
+          # The APIsec username with which the scans will be executed
+          apisec-username: ${{ secrets.apisec_username }}
+          # The Password of the APIsec user with which the scans will be executed
+          apisec-password: ${{ secrets.apisec_password}}
+          # The name of the project for security scan
+          apisec-project: "VAmPI"
+          # The name of the sarif format result file The file is written only if this property is provided.
+          sarif-result-file: "apisec-results.sarif"
+       - name: Import results
+         uses: github/codeql-action/upload-sarif@v3
+         with:
+          sarif_file: ./apisec-results.sarif