Skip to content

Conversation

@beeman
Copy link
Member

@beeman beeman commented May 2, 2025

No description provided.

@changeset-bot
Copy link

changeset-bot bot commented May 2, 2025

🦋 Changeset detected

Latest commit: 22e0cd7

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 5 packages
Name Type
@pubkey-cache/resolver Patch
node-redis Patch
@pubkey-cache/server Patch
@pubkey-cache/core Patch
@pubkey-cache/react Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

@bundlemon
Copy link

bundlemon bot commented May 2, 2025

BundleMon

Files updated (3)
Status Path Size Limits
resolver/dist/index.native.mjs
1.96KB (+54B +2.77%) -
resolver/dist/index.node.mjs
1.96KB (+54B +2.77%) -
resolver/dist/index.browser.mjs
1.96KB (+52B +2.66%) -
Unchanged files (10)
Status Path Size Limits
server/dist/index.browser.mjs
702B -
server/dist/index.native.mjs
701B -
server/dist/index.node.mjs
698B -
react/dist/index.browser.mjs
471B -
react/dist/index.native.mjs
469B -
react/dist/index.node.mjs
468B -
@pubkey-cache/core production bundle
core/dist/index.production.min.js
141B -
core/dist/index.browser.mjs
125B -
core/dist/index.native.mjs
124B -
core/dist/index.node.mjs
122B -

Total files change +160B +1.62%

Final result: ✅

View report in BundleMon website ➡️


Current branch size history | Target branch size history

@beeman beeman force-pushed the beeman/resolver-asset branch from fa46f15 to 53e4e1c Compare May 2, 2025 01:06
@beeman beeman force-pushed the beeman/resolver-asset branch from 53e4e1c to 22e0cd7 Compare May 2, 2025 01:10
@beeman beeman merged commit 22e0cd7 into main May 2, 2025
5 checks passed
@beeman beeman deleted the beeman/resolver-asset branch May 2, 2025 01:17
@github-actions github-actions bot mentioned this pull request May 2, 2025
@github-actions
Copy link

Because there has been no activity on this PR for 14 days since it was merged, it has been automatically locked. Please open a new issue if it requires a follow up.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators May 16, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants