Skip to content

chore: release v4.1.1#504

Open
jdx wants to merge 1 commit into
mainfrom
release
Open

chore: release v4.1.1#504
jdx wants to merge 1 commit into
mainfrom
release

Conversation

@jdx
Copy link
Copy Markdown
Owner

@jdx jdx commented Jun 4, 2026


4.1.1 - 2026-06-05

📚 Documentation

⚙️ Miscellaneous Tasks


Note

Low Risk
Version and changelog-only release with no action logic or dist changes; low impact for consumers pinning the new tag.

Overview
Release v4.1.1 bumps the package version from 4.1.0 to 4.1.1 in package.json and package-lock.json, and adds a new 4.1.1 section at the top of CHANGELOG.md (2026-06-05).

The changelog entry documents what shipped since v4.1.0: a documentation update linking a Rust cache issue (#496), plus CI maintenance (zizmor version comment fixes #506, adopting the pr-closer action #505). The diff also adds a missing 4.1.0 bug-fix note for resolving zizmor findings (#503) under the existing 4.1.0 section.

There are no changes to action source, dist/, or runtime behavior in this PR—only version and release notes.

Reviewed by Cursor Bugbot for commit d1ec2cc. Bugbot is set up for automated code reviews on this repo. Configure here.

@jdx jdx added the release label Jun 4, 2026
@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented Jun 4, 2026

Too much diff to scan? Review this PR in Change Stack to start with the highest-impact changes.

Review Change Stack

Note

Reviews paused

It looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the reviews.auto_review.auto_pause_after_reviewed_commits setting.

Use the following commands to manage reviews:

  • @coderabbitai resume to resume automatic reviews.
  • @coderabbitai review to trigger a single review.

Use the checkboxes below for quick actions:

  • ▶️ Resume reviews
  • 🔍 Trigger review
📝 Walkthrough

Walkthrough

Prepends a new 4.1.1 release (2026-06-05) to CHANGELOG.md with two CI bullets and inserts a “resolve zizmor findings” CI bullet into the 4.1.0 Bug Fixes; bumps package.json version from 4.1.0 to 4.1.1.

Changes

Release metadata update

Layer / File(s) Summary
Changelog updates
CHANGELOG.md
Adds topmost 4.1.1 release section (2026-06-05) with a “Miscellaneous Tasks” subsection containing CI bullets for fixing zizmor version comments (#506) and using the pr-closer action (#505); inserts a CI bullet under 4.1.0 Bug Fixes for resolving zizmor findings (#503).
Package version bump
package.json
Updates version from 4.1.0 to 4.1.1.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

Poem

🐇 New version hops into sight,
Changelog crumbs in silver light,
CI notes fixed, a tiny cheer,
Four-dot-one-dot-one is here,
Nibble the carrot, merge with delight.

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Title check ✅ Passed The pull request title 'chore: release v4.1.1' is clear and directly reflects the main objective of the changeset—releasing version 4.1.1 by bumping the package version and updating the changelog.
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.
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.

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

✨ Finishing Touches
📝 Generate docstrings
  • Create stacked PR
  • Commit on current branch
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch release

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

@greptile-apps
Copy link
Copy Markdown

greptile-apps Bot commented Jun 4, 2026

Greptile Summary

This is a patch release bump from v4.1.0 to v4.1.1, updating the version in package.json and package-lock.json and adding the corresponding changelog entry.

  • Version bumped from 4.1.0 to 4.1.1 in package.json and package-lock.json.
  • CHANGELOG.md updated with entries for documentation and CI miscellaneous tasks included in this patch release.

Confidence Score: 5/5

Routine patch release with only version number and changelog updates — no logic, dependencies, or configuration changed.

The diff is limited to version string bumps in package.json and package-lock.json and the corresponding CHANGELOG.md entry. No code, dependencies, or workflows were modified.

No files require special attention.

Important Files Changed

Filename Overview
CHANGELOG.md Adds v4.1.1 changelog section with documentation and CI task entries; also backfills one CI entry under v4.1.0.
package.json Version field bumped from 4.1.0 to 4.1.1; no other changes.
package-lock.json Version field bumped from 4.1.0 to 4.1.1 in both the root and packages[""] entries; no dependency changes.

Reviews (7): Last reviewed commit: "chore: release v4.1.1" | Re-trigger Greptile

@jdx jdx changed the title chore: release v4.1.0 chore: release v4.1.1 Jun 4, 2026
Copy link
Copy Markdown

@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.

Actionable comments posted: 1

🤖 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 `@CHANGELOG.md`:
- Line 30: Update the changelog entry string that currently reads "github
actions" to the correct product casing "GitHub Actions" in the changelog line
beginning with "- **(ci)** add zizmor workflow for github actions security
analysis (`#471`)"; ensure the rest of the entry (bold tag, workflow name,
PR/author markup) remains unchanged.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

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

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 3eed6f64-747a-4529-9da1-57417eb5cc90

📥 Commits

Reviewing files that changed from the base of the PR and between 47bac75 and 2ea116e.

⛔ Files ignored due to path filters (1)
  • package-lock.json is excluded by !**/package-lock.json
📒 Files selected for processing (2)
  • CHANGELOG.md
  • package.json
🚧 Files skipped from review as they are similar to previous changes (1)
  • package.json

Copy link
Copy Markdown

@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

Inline review comments failed to post. This is likely due to GitHub's internal server error or limits when posting large numbers of comments. If you are seeing this consistently it is likely a permissions issue. Please check "Moderation" -> "Code review limits" under your organization settings.

Actionable comments posted: 1

🤖 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 `@CHANGELOG.md`:
- Line 30: Update the changelog entry string that currently reads "github
actions" to the correct product casing "GitHub Actions" in the changelog line
beginning with "- **(ci)** add zizmor workflow for github actions security
analysis (`#471`)"; ensure the rest of the entry (bold tag, workflow name,
PR/author markup) remains unchanged.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

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

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 3eed6f64-747a-4529-9da1-57417eb5cc90

📥 Commits

Reviewing files that changed from the base of the PR and between 47bac75 and 2ea116e.

⛔ Files ignored due to path filters (1)
  • package-lock.json is excluded by !**/package-lock.json
📒 Files selected for processing (2)
  • CHANGELOG.md
  • package.json
🚧 Files skipped from review as they are similar to previous changes (1)
  • package.json
🛑 Comments failed to post (1)
CHANGELOG.md (1)

30-30: ⚠️ Potential issue | 🟡 Minor | ⚡ Quick win

Capitalize product name consistently in changelog text.

Line 30 uses “github actions”; use “GitHub Actions” to match official naming in user-facing release notes.

🧰 Tools
🪛 LanguageTool

[uncategorized] ~30-~30: The official name of this software platform is spelled with a capital “H”.
Context: ...470) - (ci) add zizmor workflow for github actions security analysis (#471) by [@j...

(GITHUB)

🤖 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 `@CHANGELOG.md` at line 30, Update the changelog entry string that currently
reads "github actions" to the correct product casing "GitHub Actions" in the
changelog line beginning with "- **(ci)** add zizmor workflow for github actions
security analysis (`#471`)"; ensure the rest of the entry (bold tag, workflow
name, PR/author markup) remains unchanged.

@jdx jdx force-pushed the release branch 4 times, most recently from 9ded155 to 09e8fe1 Compare June 5, 2026 22:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants