Dep Updates 2026-05-01

[mynameistito]

Dep Updates 2026-05-01

Note

Update p-queue to ^9.2.0 and ultracite to ^7.6.2

Bumps two dependencies in package.json: p-queue from ^9.1.2 to ^9.2.0 and ultracite from ^7.6.1 to ^7.6.2. The lockfile reflects the resolved versions and updated integrity hashes.

^{Macroscope summarized e3cec1b.}

[coderabbitai]

📝 Walkthrough

Summary by CodeRabbit

• Chores
  • Updated project dependencies to their latest compatible versions.

Walkthrough

Updates project dependencies: runtime dependency p-queue from ^9.1.2 to ^9.2.0 and dev dependency ultracite from ^7.6.1 to ^7.6.2. Adds a Changesets markdown file declaring a patch release for github-archiver with the p-queue update.

Changes

Cohort / File(s)	Summary
Dependency Updates .changeset/dep-updates-1777619917587.md, package.json	Bumps p-queue runtime dependency to ^9.2.0 and ultracite dev dependency to ^7.6.2. Introduces Changesets file for patch release declaration.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• Dep Updates 2026-04-03 #20: Updates p-queue dependency version to align with runtime dependency management.
• Dep Updates 2026-04-14 #24: Modifies ultracite dev dependency version in the same manner.
• dep update #12: Updates multiple dependencies and includes Changesets file for patch release.

Poem

🐰 Hop, hop! The queue gets faster still,
Ultracite polished with each hill,
A changeset marks our update's way,
Dependencies dance in harmony today! ✨

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Title check	❓ Inconclusive	The title is vague and generic, using 'Dep Updates' without specifying which dependencies were changed or their version details.	Consider using a more descriptive title that specifies the key dependencies updated, such as 'Update p-queue to ^9.2.0 and ultracite to ^7.6.2'.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Description check	✅ Passed	The description clearly explains that p-queue and ultracite dependencies were updated, with specific version details matching the changeset.
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 chore/dep-updates-2026-05-01-1777619917587

---

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

_{Review rate limit: 0/1 reviews remaining, refill in 60 minutes.}

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

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[coderabbitai]

Caution

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

⚠️ Outside diff range comments (1)

.changeset/dep-updates-1777619917587.md (1)

1-7: 🧹 Nitpick | 🔵 Trivial

Exclude .changeset/*.md from MD041 in markdownlint-cli2 configuration.

MD041 will trigger on the frontmatter delimiters (---) because the front matter lacks a title field (not how Changesets structures metadata). The changeset file is correctly formatted per spec. Verify that your markdownlint-cli2 config excludes .changeset/*.md from MD041 checking, either via an ignores glob pattern or by excluding the directory from the linter invocation. Do not add a heading to changeset files; they require frontmatter at the top.

🤖 Prompt for AI Agents

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

In @.changeset/dep-updates-1777619917587.md around lines 1 - 7, Update the
markdownlint-cli2 configuration to exclude changeset files from rule MD041 by
adding an ignore pattern for ".changeset/*.md" (or excluding that directory from
the linter invocation); specifically, modify the markdownlint-cli2 config object
where rules/ignores are defined so MD041 is not applied to ".changeset/*.md"
(use the "ignores" glob or equivalent exclude setting), and ensure the exclusion
targets MD041 only for those files so you do not alter linting for other
markdown files.

🤖 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 @.changeset/dep-updates-1777619917587.md:
- Around line 1-7: Update the markdownlint-cli2 configuration to exclude
changeset files from rule MD041 by adding an ignore pattern for
".changeset/*.md" (or excluding that directory from the linter invocation);
specifically, modify the markdownlint-cli2 config object where rules/ignores are
defined so MD041 is not applied to ".changeset/*.md" (use the "ignores" glob or
equivalent exclude setting), and ensure the exclusion targets MD041 only for
those files so you do not alter linting for other markdown files.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: 8d6ba0ba-8592-47c4-afd1-f614d135b5f3

📥 Commits

Reviewing files that changed from the base of the PR and between 356e757 and e3cec1b.

⛔ Files ignored due to path filters (1)

• bun.lock is excluded by !**/*.lock

📒 Files selected for processing (2)

• .changeset/dep-updates-1777619917587.md
• package.json

[cubic-dev-ai]

No issues found across 3 files