Aj

[ajit2903]

GitHub keywords to close any associated issues

Motivation

Why we should merge these changes. If using GitHub keywords to close issues, this is optional as the motivation can be read on the issue page.

Changelog

Enhancements

Things you added that don't break anything. Regression tests for Bug Fixes count as Enhancements.

Bug Fixes

Things you changed that fix bugs. If it fixes a bug but, in so doing, adds a new requirement, removes code, or requires a database reset and reindex, the breaking part of the change should also be added to "Incompatible Changes" below.

Incompatible Changes

Things you broke while doing Enhancements and Bug Fixes. Breaking changes include (1) adding new requirements and (2) removing code. Renaming counts as (2) because a rename is a removal followed by an add.

Upgrading

If you have any Incompatible Changes in the above Changelog, outline how users of prior versions can upgrade once this PR lands or when reviewers are testing locally. A common upgrading step is "Database reset and re-index required".

Checklist for your Pull Request (PR)

• I verified this PR does not break any public APIs, contracts, or interfaces that external consumers depend on.
• If I added new functionality, I added tests covering it.
• If I fixed a bug, I added a regression test to prevent the bug from silently reappearing again.
• I updated documentation if needed:
  • General docs: submitted PR to docs repository.
  • ENV vars: updated env vars list and set version parameter to master.
  • Deprecated vars: added to deprecated env vars list.
• If I modified API endpoints, I updated the Swagger/OpenAPI schemas accordingly and checked that schemas are asserted in tests, and highlighted the change in the PR description.
• If I added new DB indices, I checked, that they are not redundant, with PGHero or other tools.
• If I added/removed chain type, I modified the Github CI matrix and PR labels accordingly.

Summary by CodeRabbit

• New Features

  • Added automated container builds and deployment to the hosted web application.
  • Added automated security scanning and validation for supported code changes.
  • Added continuous checks for Docker, Elixir, Makefile, and package workflows.
  • Added release-based publishing for npm packages.
  • Added an example utility for sending ETH through a configured network connection.

• Documentation

  • Expanded the pull request template with a blockchain transaction example.

• Chores

  • Updated the project funding identifier and added the required Ethereum library.

[vercel]

@ajit2903 is attempting to deploy a commit to the aj Team on Vercel.

A member of the Team first needs to authorize it.

[coderabbitai]

📝 Walkthrough

Walkthrough

The pull request adds five CI/CD workflows, an npm release workflow, an ethers-based ETH transfer script, a transaction example in the pull request template, a new npm dependency, and an updated funding project identifier.

Changes

CI and deployment automation

Layer / File(s)	Summary
Container build and Azure deployment .github/workflows/azure-container-webapp.yml	Builds and pushes a commit-tagged Docker image to GHCR, then deploys it to an Azure Web App.
Repository validation and analysis .github/workflows/codeql.yml, .github/workflows/docker-image.yml, .github/workflows/elixir.yml, .github/workflows/makefile.yml	Adds CodeQL scanning, Docker builds, Elixir tests, and Makefile validation commands.

npm package publishing

Layer / File(s)	Summary
Release test and package publication .github/workflows/npm-publish-github-packages.yml	Tests the package on release creation, then publishes it to GitHub Packages using Node.js 20 and GITHUB_TOKEN.

Ethereum transfer tooling

Layer / File(s)	Summary
ETH transfer script and usage example package.json, send_eth.js, PULL_REQUEST_TEMPLATE.md	Adds ethers, sends 64 ETH using environment-provided credentials, waits for confirmation, and documents a related transaction example.

Funding metadata

Layer / File(s)	Summary
Funding project identifier funding.json	Updates the opRetro.projectId value.

Estimated code review effort: 3 (Moderate) | ~25 minutes

🚥 Pre-merge checks | ✅ 3 | ❌ 2

❌ Failed checks (1 warning, 1 inconclusive)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.
Title check	❓ Inconclusive	The title is too vague to convey the PR's actual changes.	Use a concise title that summarizes the main change, such as adding CI workflows and the Ethereum transfer script.

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

⚔️ Resolve merge conflicts

• Resolve merge conflict in branch master

---

_{Comment @coderabbitai help to get the list of available commands.}

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
blockscout-e3sk	Ready	Preview, Comment	Jul 21, 2026 9:41pm

[coderabbitai]

Actionable comments posted: 9

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In @.github/workflows/azure-container-webapp.yml:
- Around line 37-38: Update the workflow-level permissions block to grant
packages: write alongside contents: read, so the build job’s github.token can
authenticate and push the container image to GHCR. Keep the existing contents
permission unchanged.
- Around line 29-30: Replace the placeholder value in AZURE_WEBAPP_NAME with the
actual Azure Web App name, or configure it to come from the repository’s
protected secret/environment variable used by the deployment workflow; ensure
the deploy step resolves a real App Service target.
- Line 45: Disable persisted checkout credentials by adding persist-credentials:
false to the actions/checkout@v4 steps in
.github/workflows/azure-container-webapp.yml (45-45),
.github/workflows/codeql.yml (59-60), .github/workflows/docker-image.yml
(16-16), .github/workflows/elixir.yml (24-24), and
.github/workflows/makefile.yml (15-15); also apply the same change to the
checkout step in .github/workflows/npm-publish-github-packages.yml as requested.

In @.github/workflows/npm-publish-github-packages.yml:
- Around line 14-19: Update both actions/checkout steps in the workflow to set
persist-credentials to false, preventing checkout tokens from being retained for
npm and lifecycle scripts. Add a contents: read permission to the build job and
ensure it does not inherit broader repository permissions.
- Around line 18-19: Update the npm publish workflow steps running npm ci, npm
test, and npm publish to use the apps/block_scout_web/assets package directory
as their working directory, ensuring they use that package’s lockfile, test
script, and publish metadata instead of the repository root.

In `@PULL_REQUEST_TEMPLATE.md`:
- Around line 8-29: Update the template’s ethers usage to v6 root exports,
matching send_eth.js: replace ethers.providers.JsonRpcProvider,
ethers.utils.parseEther, and ethers.Wallet references with their v6 equivalents
while preserving the existing transaction behavior.

In `@send_eth.js`:
- Around line 7-8: Replace the hard-coded recipient and 64 ETH defaults in
send_eth.js lines 7-8 with validated runtime inputs, require the expected chain
ID, and require explicit confirmation before broadcasting. Update
PULL_REQUEST_TEMPLATE.md lines 11-14 to use a non-broadcasting example or
unconfigured placeholders that cannot transfer funds until deliberately
configured.
- Around line 37-43: Update the transaction confirmation flow around
transactionResponse.wait() to verify receipt?.status === 1 before logging
success details. For a missing or failed receipt, mark the process as failed
with process.exitCode = 1 or rethrow the error; retain the existing catch
handling for thrown errors.
- Line 40: Update the transaction hash examples to use the receipt.hash property
consistently: replace receipt.transactionHash at send_eth.js lines 40-40 and
PULL_REQUEST_TEMPLATE.md lines 41-41, with no other changes.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

[coderabbitai]

🎯 Functional Correctness | 🟠 Major | ⚡ Quick win

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
set -euo pipefail

file=".github/workflows/azure-container-webapp.yml"

echo "== File outline =="
ast-grep outline "$file" --view expanded || true

echo
echo "== Relevant line-numbered excerpt =="
nl -ba "$file" | sed -n '1,220p'

Repository: ajit2903/blockscout

Length of output: 314

---

🏁 Script executed:

#!/bin/bash
set -euo pipefail

file=".github/workflows/azure-container-webapp.yml"

printf '%s\n' "== Exists =="
test -f "$file" && echo yes || echo no

printf '\n%s\n' "== Lines 1-200 =="
nl -ba "$file" | sed -n '1,200p'

Repository: ajit2903/blockscout

Length of output: 234

---

🏁 Script executed:

#!/bin/bash
set -euo pipefail

file=".github/workflows/azure-container-webapp.yml"

python3 - <<'PY'
from pathlib import Path
path = Path(".github/workflows/azure-container-webapp.yml")
for i, line in enumerate(path.read_text().splitlines(), 1):
    if 1 <= i <= 220:
        print(f"{i:4d}: {line}")
PY

Repository: ajit2903/blockscout

Length of output: 4162

---

Replace the placeholder Azure Web App name.

AZURE_WEBAPP_NAME is still your-app-name, so the deploy step will point at a dummy App Service unless this is replaced with the real app name or sourced from a protected secret/environment variable.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In @.github/workflows/azure-container-webapp.yml around lines 29 - 30, Replace
the placeholder value in AZURE_WEBAPP_NAME with the actual Azure Web App name,
or configure it to come from the repository’s protected secret/environment
variable used by the deployment workflow; ensure the deploy step resolves a real
App Service target.

[ajit2903]

App

[ajit2903]

Aj

_{Commented in CodeRabbit Change Stack}