Skip to content

v4.1.0 - #634

Merged
danny-avila merged 1 commit into
mainfrom
lia/release-4-1-0
Oct 22, 2026
Merged

v4.1.0#634
danny-avila merged 1 commit into
mainfrom
lia/release-4-1-0

Conversation

@lia-by-librechat

@lia-by-librechat lia-by-librechat Bot commented Oct 22, 2026 •

Copy link
Copy Markdown
Contributor

Summary

Prepare @librechat/agents 4.1.0 from current main. Leave unmerged until approved.

This patch changes only the version in package.json and the two root version fields in package-lock.json, from 4.0.6 to 4.1.0. Dependency resolutions, source, exports and configuration are unchanged.

Already merged since 4.0.6

Verification

Verified on pushed head 314362a1bca762686c51dc5277f144079f679016, based on main 6dfab76d:

  • Semantic manifest/lockfile comparison: only the three intended version values changed; dependency resolutions unchanged.
  • npm ci, workspace npx tsc --noEmit, manifest formatting and diff checks: passed.
  • Focused decision/rerank tests: 452 passed across 12 suites.
  • Package build, circular dependencies, release-workflow syntax and built light-entry ESM/CJS/declaration guards: passed.
  • Pack dry-run: version 4.1.0; all new light subpaths include ESM/CJS/types; task scratch excluded. No tarball published.

Exact-head CI passed all 13 validation jobs. Independent review of 314362a1bca762686c51dc5277f144079f679016 completed with no findings, including the final remote-head/base refresh. The reviewer verified exact JSON/lock changes and release-detector behavior; its isolated lane did not rerun the parent task's local tests/typecheck/build or exercise publishing. No TypeScript source changed, so touched-source ESLint/import-order checks are not applicable.

Release control

PR title and commit are v4.1.0, matching the existing workflow's version-commit detection. Merging to main runs the configured publish/release pipeline; no merge, tag, release, publishing workflow dispatch or package publication has been performed by this task. Auto-merge is not enabled. No consumer migration, live-provider verification, calibration or performance claim is included.

@lia-by-librechat

lia-by-librechat Bot commented Oct 22, 2026 •

Copy link
Copy Markdown
Contributor Author

Final verification for exact pushed and independently reviewed head 314362a1bca762686c51dc5277f144079f679016, based on main/merge-base 6dfab76d2daa914e121f58f7d45cded43cb4b62c.

Hold unmerged, per request. Auto-merge is disabled. No version tag, GitHub release, publishing dispatch or package publication was performed by this task.

The patch changes only the package version and two root npm lockfile version fields to 4.1.0. Every dependency record, resolution, source file, export and configuration remains unchanged. Title/commit v4.1.0 matches the existing release detector, including squash subjects.

Local checks passed: 452 decision/rerank tests across 12 focused suites; clean npm ci; full workspace typecheck; manifest formatting and diff checks; release-workflow syntax; circular dependencies; package build; built light-entry ESM/CJS/declaration guards; pack dry-run containing all three light subpaths and no scratch files. No TypeScript source changed, so touched-source lint/import ordering is not applicable.

CI for this exact head passed all 13 validation jobs. Independent review is complete with no findings and no rejected/open findings. Final remote-head/base freshness was independently confirmed. The isolated reviewer did not rerun local tests/typecheck/build, and publishing was not exercised.

No live-provider, calibration, performance, or consumer-migration evaluation. Merging would invoke the existing main-branch release pipeline; this PR remains unmerged.

@danny-avila
danny-avila merged commit f4695e4 into main Oct 22, 2026
13 checks passed
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