Skip to content

chore(deps): bump packumeta#2814

Merged
ghostdevv merged 1 commit into
mainfrom
bump-packumeta
May 29, 2026
Merged

chore(deps): bump packumeta#2814
ghostdevv merged 1 commit into
mainfrom
bump-packumeta

Conversation

@43081j
Copy link
Copy Markdown
Contributor

@43081j 43081j commented May 29, 2026

This will switch us over to the new staging signal npm just released.

🔗 Linked issue

🧭 Context

📚 Description

This will switch us over to the new staging signal npm just released.
@vercel
Copy link
Copy Markdown
Contributor

vercel Bot commented May 29, 2026

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

Project Deployment Actions Updated (UTC)
docs.npmx.dev Ready Ready Preview, Comment May 29, 2026 8:14am
npmx.dev Ready Ready Preview, Comment May 29, 2026 8:14am
1 Skipped Deployment
Project Deployment Actions Updated (UTC)
npmx-lunaria Ignored Ignored May 29, 2026 8:14am

Request Review

@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented May 29, 2026

Review Change Stack

📝 Walkthrough

Walkthrough

The packumeta dependency is bumped from version 0.4.0 to 0.4.1 in package.json.

Changes

Dependency Update

Layer / File(s) Summary
Packumeta version bump
package.json
The packumeta dependency version is updated from 0.4.0 to 0.4.1 in the dependencies block.

Possibly related PRs

  • npmx-dev/npmx.dev#2804: This PR's packumeta dependency bump (0.4.00.4.1) is directly tied to the refactor that switches trust-level logic to use packumeta.

Suggested reviewers

  • ghostdevv
  • serhalp
🚥 Pre-merge checks | ✅ 4
✅ Passed checks (4 passed)
Check name Status Explanation
Description check ✅ Passed The description mentions switching to a new staging signal npm released, which relates to the packumeta dependency bump, though details are minimal.
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.
Title check ✅ Passed The title 'chore(deps): bump packumeta' directly and clearly describes the main change—a dependency version bump of the packumeta package, which aligns precisely with the changeset.

✏️ 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 bump-packumeta

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.

@socket-security
Copy link
Copy Markdown

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff Package Supply Chain
Security
Vulnerability Quality Maintenance License
Addedpackumeta@​0.4.1711008991100

View full report

@github-actions
Copy link
Copy Markdown

e18e dependency analysis

No dependency warnings found.

@codecov
Copy link
Copy Markdown

codecov Bot commented May 29, 2026

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!

@43081j 43081j added this pull request to the merge queue May 29, 2026
@ghostdevv ghostdevv removed this pull request from the merge queue due to a manual request May 29, 2026
@ghostdevv ghostdevv changed the title chore: bump packumeta chore(deps): bump packumeta May 29, 2026
@ghostdevv ghostdevv added this pull request to the merge queue May 29, 2026
Merged via the queue into main with commit b3ba515 May 29, 2026
30 checks passed
@ghostdevv ghostdevv deleted the bump-packumeta branch May 29, 2026 13:04
@github-actions github-actions Bot mentioned this pull request May 29, 2026
@sxzz sxzz mentioned this pull request May 29, 2026
3 tasks
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.

2 participants