-
-
Notifications
You must be signed in to change notification settings - Fork 8.8k
⬆️ chore: Bump @librechat/agents to v3.6.0
#14890
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Update
bun.lockalongside this manifest change. It still records both workspace requirements and the resolved package as@librechat/agents@3.5.1, which no longer satisfies^3.6.0; therefore Bun-based checkouts lose reproducibility, andbun install --frozen-lockfilecannot accept the committed state. Bun 1.2.14'sbun install --helpdefines that flag as “Disallow changes to lockfile,” so the lockfile needs to contain the new workspace ranges and 3.6.0 resolution rather than relying on each user to rewrite it.Useful? React with 👍 / 👎.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Correct, and I missed it — thanks.
bun.lockwas only added to the repo in db67520 (the merge of #14873), so it was not on my radar when I scoped this bump. It did still record^3.5.1in both workspace requirement blocks and@librechat/agents@3.5.1as the resolution, sobun install --frozen-lockfilewould have rejected the committed state. Fixed in 8535fed.One caveat worth stating plainly, since it affects how you should read that commit: I could not regenerate it with bun.
bun install --lockfile-onlyfails here because bun stores no integrity for thexlsxURL dependency and re-fetchescdn.sheetjs.comon every resolve, which this sandbox's network policy denies:(Confirmed at the proxy layer, not just as a bun error — the gateway answers 403 to
CONNECT cdn.sheetjs.com:443.) The same constraint is whynpm cicannot run here either.So I updated the entry directly. That is exact rather than approximate in this specific case, because the package's dependency graph does not move between the two versions — I verified against the registry that
dependencies,peerDependenciesandoptionalPeersat3.6.0are byte-identical to3.5.1. Only three things can therefore change, and only those three did:^3.6.0@librechat/agents@3.6.0sha512-PWDd29NL2Mtuomt…— which I cross-checked equals the hash npm independently resolved intopackage-lock.jsonThe existing
@librechat/agents/*hoisting overrides (@anthropic-ai/sdk,@opentelemetry/sdk-node,diff,openai,uuid) stay valid untouched, since the dependency set they resolve is unchanged. Net diff is 3 lines. I also confirmed the file still parses.If you'd rather have a bun-authored lockfile than a hand-verified one, a
bun install --lockfile-onlyon a machine that can reachcdn.sheetjs.comshould produce no further change — but I'd rather flag that I couldn't run it than imply I did.Generated by Claude Code