Skip to content

chore: prep v1.1.1#3274

Open
julienrbrt wants to merge 1 commit intomainfrom
julien/prep-111
Open

chore: prep v1.1.1#3274
julienrbrt wants to merge 1 commit intomainfrom
julien/prep-111

Conversation

@julienrbrt
Copy link
Copy Markdown
Member

@julienrbrt julienrbrt commented Apr 21, 2026

Overview

Summary by CodeRabbit

  • Chores
    • Updated changelog documentation to organize and clarify version 1.1.1 release information, moving previously unreleased entries into the appropriate versioned section for better clarity.

@github-actions
Copy link
Copy Markdown
Contributor

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

BuildFormatLintBreakingUpdated (UTC)
✅ passed⏩ skipped✅ passed✅ passedApr 21, 2026, 3:18 PM

@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai bot commented Apr 21, 2026

📝 Walkthrough

Walkthrough

The pull request reorganizes a single fixed item in the changelog by moving it from the unreleased section to a newly created v1.1.1 release section. The "Raft HA production hardening" fix entry is repositioned under the version-specific fixes subsection.

Changes

Cohort / File(s) Summary
Changelog Update
CHANGELOG.md
Created new v1.1.1 release section and relocated "Raft HA production hardening…" entry from unreleased fixes to version-specific fixes.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Suggested reviewers

  • tac0turtle
  • chatton

Poem

🐰 A changelog tale, oh what a treat,
Version bumps make releases complete,
From unreleased depths to v1.1.1,
The fix finds its home, the sorting is done! ✨

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name Status Explanation Resolution
Description check ⚠️ Warning The description contains only the template structure with no substantive content provided in the Overview section. Fill in the Overview section with explanation of the v1.1.1 release changes, context, and rationale for the changelog updates.
✅ Passed checks (4 passed)
Check name Status Explanation
Title check ✅ Passed The title 'chore: prep v1.1.1' is clear and specific about the release preparation work, matching the changelog changes that establish v1.1.1.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
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.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch julien/prep-111

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@claude
Copy link
Copy Markdown
Contributor

claude bot commented Apr 21, 2026

Claude finished @julienrbrt's task in 40s —— View job


Code Review: chore: prep v1.1.1

  • Gather context
  • Review CHANGELOG.md changes
  • Post final review

This is a straightforward changelog prep for v1.1.1 — moving entries from [Unreleased] into a versioned section and leaving an empty [Unreleased] block for future changes. The structure is correct and consistent with the existing format in the file.

Minor observations:

  1. Duplicate PR referenceCHANGELOG.md:18-19: PR #3235 is cited for two separate entries ("Make it easier to override DefaultMaxBlobSize by ldflags" and "Add solo sequencer"). This is fine if both features landed in the same PR, but worth double-checking that the reference is intentional and not a copy-paste slip.

  2. Section header convention — The ### Changes header is used consistently throughout this repo (vs. the Keep a Changelog spec's ### Changed), so no issue there.

  3. Version header format## v1.1.1 (without brackets) is consistent with how all other version entries (## v1.1.0, ## v1.1.0-rc.1, etc.) are formatted in this file. ✅

Overall the change looks correct. No blocking issues.

Copy link
Copy Markdown
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)
CHANGELOG.md (1)

271-271: ⚠️ Potential issue | 🟡 Minor

Update the Unreleased comparison link to reference latest version.

The [Unreleased] link compares from v1.0.0-beta.1, which is outdated. It should compare from v1.1.0...HEAD currently, and once v1.1.1 is released and tagged, update it to v1.1.1...HEAD to accurately show only unreleased changes.

📝 Suggested fix

Update now:

-[Unreleased]: https://github.com/evstack/ev-node/compare/v1.0.0-beta.1...HEAD
+[Unreleased]: https://github.com/evstack/ev-node/compare/v1.1.0...HEAD

After tagging v1.1.1:

-[Unreleased]: https://github.com/evstack/ev-node/compare/v1.1.0...HEAD
+[Unreleased]: https://github.com/evstack/ev-node/compare/v1.1.1...HEAD
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@CHANGELOG.md` at line 271, Update the [Unreleased] comparison URL in
CHANGELOG.md so it compares from the current latest release: replace the
existing "v1.0.0-beta.1...HEAD" target with "v1.1.0...HEAD" now (and after
v1.1.1 is tagged, update it to "v1.1.1...HEAD") to ensure the Unreleased link
shows only changes since the latest release.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Outside diff comments:
In `@CHANGELOG.md`:
- Line 271: Update the [Unreleased] comparison URL in CHANGELOG.md so it
compares from the current latest release: replace the existing
"v1.0.0-beta.1...HEAD" target with "v1.1.0...HEAD" now (and after v1.1.1 is
tagged, update it to "v1.1.1...HEAD") to ensure the Unreleased link shows only
changes since the latest release.

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 445794da-86f4-4693-bc79-953732f85ba4

📥 Commits

Reviewing files that changed from the base of the PR and between c1d4996 and b033c3f.

📒 Files selected for processing (1)
  • CHANGELOG.md

@codecov
Copy link
Copy Markdown

codecov bot commented Apr 21, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 62.51%. Comparing base (c1d4996) to head (b033c3f).

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #3274      +/-   ##
==========================================
- Coverage   62.60%   62.51%   -0.09%     
==========================================
  Files         122      122              
  Lines       13020    13020              
==========================================
- Hits         8151     8140      -11     
- Misses       3984     3993       +9     
- Partials      885      887       +2     
Flag Coverage Δ
combined 62.51% <ø> (-0.09%) ⬇️

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant