chore: add workflow for stale prs and issue type bug

[MatteoGabriele]

🧭 Context

We need an automated system to manage stale issues and PRs to keep the project clean. ✨
We have decided to focus only on "Bug" issues, as they typically have a shorter lifespan, along with all PRs. These will be tagged and then automatically closed.

📚 Description

These changes add the built-in GitHub stale action to automate the entire stale-tagging process and auto-close.
Issues of type "Bug" and PRs will be tagged after 30 days of inactivity and then automatically closed 7 days later.

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
npmx.dev	Ready	Preview, Comment	Apr 18, 2026 9:29pm

2 Skipped Deployments

Project	Deployment	Actions	Updated (UTC)
docs.npmx.dev	Ignored	Preview	Apr 18, 2026 9:29pm
npmx-lunaria	Ignored		Apr 18, 2026 9:29pm

[coderabbitai]

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 68622165-e826-41b1-86e8-728c5328ab4c

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

📝 Walkthrough

Walkthrough

Introduces a new GitHub Actions workflow that automatically marks issues and pull requests as stale after 30 days of inactivity and closes them after 7 additional days, with separate processing jobs for bugs and pull requests.

Changes

Cohort / File(s)	Summary
Stale workflow automation .github/workflows/stale.yml	Adds GitHub Actions workflow scheduled to run daily at 02:00 UTC with manual trigger support. Defines two jobs: stale-bugs marks bug-type issues as stale after 30 days and closes after 7 days; stale-prs applies the same logic to pull requests. Both jobs process up to 500 operations per run and use the stale label.

Possibly related PRs

• chore: increase operation per run in stale workflow #2564 — Modifies the same stale workflow configuration by adjusting the operations-per-run setting for the actions/stale action.
• chore: remove stale bot #2566 — Removes the previous stale workflow file (.github/workflows/close-stale.yml) that performed equivalent stale-marking and closing functionality.
• feat: add stale workflow #2555 — Adds a GitHub Actions workflow using the same actions/stale action to mark and close stale issues and pull requests with similar but distinct configuration parameters.

Suggested reviewers

• 43081j
• graphieros
• patak-cat

🚥 Pre-merge checks | ✅ 2

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately summarizes the main change: adding a GitHub Actions workflow to manage stale PRs and bug-type issues.
Description check	✅ Passed	The description is directly related to the changeset, explaining the context, purpose, and specific behaviour of the new stale workflow being added.

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

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

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

• X
• Mastodon
• Reddit
• LinkedIn

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

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ All tests successful. No failed tests found.

📢 Thoughts on this report? Let us know!

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In @.github/workflows/stale.yml:
- Around line 17-37: The stale workflow is unintentionally processing the
opposite item type because the action defaults unset PR/issue params to 60 days;
update the job that targets issues to disable PR handling by setting
days-before-pr-stale: -1 and days-before-pr-close: -1, and update the stale-prs
job to disable issue handling by setting days-before-issue-stale: -1 and
days-before-issue-close: -1 so each job only processes its intended item type
(refer to the input names days-before-pr-stale, days-before-pr-close,
days-before-issue-stale, days-before-issue-close and the job identifier
stale-prs).

🪄 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: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 93b28aff-d8ef-4837-80ed-03bfa49e2d76

📥 Commits

Reviewing files that changed from the base of the PR and between 5f30d25 and 2ac53f2.

📒 Files selected for processing (1)

• .github/workflows/stale.yml