chore: update changlog

[tac0turtle]

Overview

[github-actions]

The latest Buf updates on your PR. Results from workflow CI and Release / buf-check (pull_request).

Build	Format	Lint	Breaking	Updated (UTC)
✅ passed	⏩ skipped	✅ passed	✅ passed	Nov 4, 2025, 2:37 PM

[claude]

Claude finished @tac0turtle's task —— View job

---

Changelog Review Complete

Tasks

• Read the modified CHANGELOG.md file
• Review the git diff to see exact changes
• Analyze changelog format and content
• Provide comprehensive review feedback

---

Review Summary

This PR updates the CHANGELOG.md file to document recent changes. Overall, the additions follow good changelog practices and adhere to the repository's Keep a Changelog format. However, there are several issues that should be addressed:

Issues Found

1. Missing PR Reference (CHANGELOG.md:30)

- Updated EVM execution client to use new `txpoolExt_getTxs` RPC API for retrieving pending transactions as RLP-encoded bytes

Issue: This entry is missing a PR reference link, unlike all other entries. All changelog entries should include the PR number in the format ([#XXXX](https://github.com/evstack/ev-node/pull/XXXX)).

Recommendation: Add the PR reference for consistency and traceability.

---

2. Removed Entry from Fixed Section (CHANGELOG.md:44)

-### Fixed
-
-
-- Pass correct namespaces for header and data to the da layer for posting ([#2560](https://github.com/evstack/ev-node/pull/2560))

Issue: A bug fix entry was removed from the Fixed section. This appears to be an existing fix that was already in the changelog.

Questions:

• Was this fix already released in a previous version? If so, it should have been moved to that version's section, not deleted.
• If this is being removed because it's no longer relevant or was incorrect, the PR description should explain why.
• If the fix is being reclassified to a different category, it should be moved, not deleted.

Recommendation: Clarify the reason for removing this entry. If it was already released, ensure it's documented in the appropriate version section.

---

3. Incomplete PR Description

The PR description only contains:

## Overview

Issue: There's no explanation of what changes were made to the changelog or why.

Recommendation: Add a description explaining:

• Which PRs are being added to the changelog
• Why the fixed entry was removed
• Any other context about the changelog update

---

Positive Observations

✅ Good Practices Followed:

1. All new entries start with action verbs ("Added", "Hardened", "Increased", etc.)
2. Entries are descriptive and explain both WHAT changed and WHY it matters
3. Breaking changes are clearly marked with "(BREAKING)"
4. PR references are included for traceability (except the one noted above)
5. Entries are properly categorized into Added, Changed, and Removed sections
6. Technical details are explained in user-friendly language

✅ Content Quality:

• The "Added" entries clearly describe new features and their benefits
• The security hardening entry in "Changed" provides specific details about the changes
• The "Removed" entry explains what was removed and where the functionality moved to

✅ Format Compliance:

• Follows Keep a Changelog 1.0.0 format
• Maintains consistent markdown formatting
• Properly uses the Unreleased section

---

Recommendations for Improvement

1. Add missing PR reference to the txpoolExt_getTxs entry
2. Clarify or restore the removed bug fix entry (fix!: header & data namespace DA  #2560)
3. Update PR description with context about the changelog changes
4. Consider adding a note if any of these changes represent breaking changes that users need to be aware of during upgrades

---

Minor Style Suggestion

The PR title has a typo: "chore: update changlog" should be "chore: update changelog"

---

Verdict

The changelog additions are well-written and informative. Once the missing PR reference is added and the removal of the bug fix entry is clarified, this will be ready to merge. The changes properly document important new features, security improvements, and breaking changes that users need to know about.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 62.37%. Comparing base (a2f0d68) to head (7988382).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #2804   +/-   ##
=======================================
  Coverage   62.37%   62.37%           
=======================================
  Files          82       82           
  Lines        7304     7304           
=======================================
  Hits         4556     4556           
  Misses       2203     2203           
  Partials      545      545           

Flag	Coverage Δ
combined	62.37% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.