Skip to content

chore(deps): update dependency ruby to v4.0.5 - #42

Merged
renovate[bot] merged 1 commit into
mainfrom
renovate/ruby-4.x
Jun 4, 2026
Merged

renovate[bot] merged 1 commit into
mainfrom
renovate/ruby-4.x

Conversation

@renovate

@renovate renovate Bot commented May 29, 2026 •

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Update Change
ruby (source) patch 4.0.4 → 4.0.5

Release Notes

ruby/ruby (ruby)

v4.0.5

Compare Source


Configuration

📅 Schedule: (in timezone America/Chicago)

  • Branch creation
    • Only on Friday (* * * * 5)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@greptile-apps

greptile-apps Bot commented May 29, 2026

Copy link
Copy Markdown

PR author is in the excluded authors list.

jdx commented Jun 4, 2026

Copy link
Copy Markdown
Owner

@renovatebot rebase

@renovate
renovate Bot force-pushed the renovate/ruby-4.x branch from 30a88c0 to ce0b71c Compare June 4, 2026 18:18
@coderabbitai

coderabbitai Bot commented Jun 4, 2026 •

Copy link
Copy Markdown

Review Change Stack

📝 Walkthrough

Walkthrough

The .ruby-version file is updated to specify Ruby 4.0.5 instead of 4.0.4, affecting the default Ruby version for the project.

Changes

Ruby Version Update

Layer / File(s) Summary
Ruby version bump
.ruby-version
The Ruby version is updated from 4.0.4 to 4.0.5.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~1 minute

Poem

🐰 A tiny hop from four-oh-four,
To four-oh-five, the rabbit's lore!
One line changed, so swift and light,
Ruby shines a little brighter bright! ✨

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Title check ✅ Passed The title accurately describes the main change: updating the Ruby dependency from version 4.0.4 to 4.0.5, which matches the file modification in .ruby-version.
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 renovate/ruby-4.x

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

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

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)
.ruby-version (1)

1-2: ⚠️ Potential issue | 🟠 Major | ⚡ Quick win

Remove the extra token from .ruby-version (keep a single version line only).

Line 2 (2) makes the file malformed; .ruby-version should contain just the version string. This can break local Ruby version resolution even if CI uses workflow inputs.

Suggested fix
 4.0.5
-2
🤖 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 @.ruby-version around lines 1 - 2, The .ruby-version file currently contains
an extra token on the second line ("2"); edit .ruby-version so it contains only
the single version string "4.0.5" (remove the stray "2" or any extra
newline/content) to ensure the file is a single-line valid Ruby version
specification.
🤖 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.

Outside diff comments:
In @.ruby-version:
- Around line 1-2: The .ruby-version file currently contains an extra token on
the second line ("2"); edit .ruby-version so it contains only the single version
string "4.0.5" (remove the stray "2" or any extra newline/content) to ensure the
file is a single-line valid Ruby version specification.

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 485da120-28ea-4a75-8237-49b42ec364d5

📥 Commits

Reviewing files that changed from the base of the PR and between 43ceb68 and ce0b71c.

📒 Files selected for processing (1)
  • .ruby-version

@renovate
renovate Bot merged commit 7123d57 into main Jun 4, 2026
11 checks passed
@renovate
renovate Bot deleted the renovate/ruby-4.x branch June 4, 2026 22:06
jdx added a commit that referenced this pull request Sep 21, 2026
…#61)

GitHub links merged pull requests to **issues** through `Closes #N`, but
discussions have no equivalent. A discussion that asks for a feature
stays open and unlinked after the pull request implementing it merges,
so the person who filed it is never told it shipped and the thread has
to be closed by hand.

This adds a workflow that runs when a pull request merges, scans its
body for discussion references, and comments on each referenced
discussion with a link back to the pull request.

| In the PR body | Effect on the discussion |
|---|---|
| `Closes #N`, `Fixes #N`, `Resolves #N` | Comment, then close as
`RESOLVED` |
| `Refs #N`, `Discussion: #N` | Comment only |

A PR titled `feat(status): show the last cron start and next scheduled
time` whose body ends in `Closes #901` posts this on discussion #901 the
moment it merges:

> Implemented in [#902](jdx/pitchfork#902):
feat(status): show the last cron start and next scheduled time

Numbers that turn out to be issues or pull requests are skipped, so
GitHub's native issue linking is unaffected, and a pull request whose
body references no discussion does nothing at all. Only same-repository
references (`#42`) are recognized, not `owner/repo#42`.

The action is pinned to `jdx/link-discussion-action@38e7537` — a fork of
[`gaojunran/link-discussion-action`](https://github.com/gaojunran/link-discussion-action)
v0.1 (MIT) taken at that same commit, so the code that runs against this
repository's token is not controlled by a third-party account. The
committed `dist/index.js` was verified byte-identical (sha256
`ec31b601…`) to a rebuild from `src/` with the locked dependencies. It
authenticates with the automatic `GITHUB_TOKEN` scoped to `discussions:
write` and `pull-requests: read`; no new secrets are required.

This has been running in
[jdx/pitchfork](https://github.com/jdx/pitchfork) since
[#596](jdx/pitchfork#596) and is being rolled
out to every repository with Discussions enabled.

*AI-assisted — Tool: Claude Code; model: anthropic/claude-opus-5;
version: 2.1.270.*

🤖 Generated with [Claude Code](https://claude.com/claude-code)

<!-- CURSOR_SUMMARY -->
---

> [!NOTE]
> **Low Risk**
> CI-only automation using scoped GITHUB_TOKEN; no application or
runtime behavior changes.
> 
> **Overview**
> Adds a **`link-discussion`** GitHub Actions workflow that runs when a
pull request is **merged** (not merely closed). It uses the pinned
**`jdx/link-discussion-action`** with the default **`GITHUB_TOKEN`**,
granted **`discussions: write`** and **`pull-requests: read`**, to find
discussion references in the PR body and post a back-link comment (and
optionally resolve discussions when keywords like **`Closes #N`** are
used).
> 
> This mirrors issue auto-linking for GitHub Discussions so requesters
get notified when their feature ships, without adding new secrets.
> 
> <sup>Reviewed by [Cursor Bugbot](https://cursor.com/bugbot) for commit
95ab9db. Bugbot is set up for automated
code reviews on this repo. Configure
[here](https://www.cursor.com/dashboard/bugbot).</sup>
<!-- /CURSOR_SUMMARY -->

<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->

## Summary by CodeRabbit

* **Chores**
* Added automated linking between merged pull requests and related
discussions.
* Improved visibility and traceability between development changes and
community conversations.

<!-- end of auto-generated comment: release notes by coderabbit.ai -->

Co-authored-by: Claude Opus 5 <noreply@anthropic.com>
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