chore(deps-dev): Bump the npm group with 2 updates#32
Conversation
Bumps the npm group with 2 updates: [@langfuse/client](https://github.com/langfuse/langfuse-js/tree/HEAD/packages/client) and [eslint](https://github.com/eslint/eslint). Updates `@langfuse/client` from 5.3.0-beta.0 to 5.3.0 - [Release notes](https://github.com/langfuse/langfuse-js/releases) - [Changelog](https://github.com/langfuse/langfuse-js/blob/main/CHANGELOG.md) - [Commits](https://github.com/langfuse/langfuse-js/commits/v5.3.0/packages/client) Updates `eslint` from 10.2.1 to 10.3.0 - [Release notes](https://github.com/eslint/eslint/releases) - [Commits](eslint/eslint@v10.2.1...v10.3.0) --- updated-dependencies: - dependency-name: "@langfuse/client" dependency-version: 5.3.0 dependency-type: direct:development update-type: version-update:semver-patch dependency-group: npm - dependency-name: eslint dependency-version: 10.3.0 dependency-type: direct:development update-type: version-update:semver-minor dependency-group: npm ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
![claude[bot]](https://avatars.githubusercontent.com/in/1236702?s=60&v=4){kind=small}
There was a problem hiding this comment.
LGTM, straightforward dependabot bump of two devDependencies (@langfuse/client beta→stable and eslint patch-level minor).
Extended reasoning...
Overview
This PR bumps two devDependencies via dependabot: @langfuse/client from 5.3.0-beta.0 → 5.3.0 (beta → stable release of the same minor version) and eslint from ^10.2.1 → ^10.3.0 (minor bump). Only package.json and pnpm-lock.yaml are touched, and the lockfile changes are mechanical re-resolutions consistent with the package.json updates.
Security risks
Minimal. Both packages are well-known and trusted upstream sources (langfuse and eslint), and the changes only affect dev-time tooling — neither dependency is in the dependencies block, so they are not bundled into the production action artifact. Integrity hashes are updated in the lockfile as expected.
Level of scrutiny
Low. This is a routine dependency bump PR with no logic changes. The @langfuse/client change is effectively pinning to a stable release of an already-vetted beta. The eslint change is a minor version bump with only feature additions, bug fixes, and chores per the release notes — no breaking changes flagged.
Other factors
No bugs were flagged by the bug hunting system. No prior reviewer comments are outstanding. The PR is self-contained and reversible.
Co-Authored-By: Codex Opus 4.6 (1M context) <noreply@anthropic.com>
|
| Experiment | Status | Actions |
|---|---|---|
| Uppercase (py) | ✅ Pass | View GitHub Action Run · View in Langfuse |
| Uppercase (ts) | ✅ Pass | View GitHub Action Run · View in Langfuse |
| Mixed dir (node) | ✅ Pass | View GitHub Action Run · View in Langfuse |
| Mixed dir (python) | ✅ Pass | View GitHub Action Run · View in Langfuse |
| Regression fixture | ❌ Regression | View GitHub Action Run · View in Langfuse |
Details
1 participant
Bumps the npm group with 2 updates: @langfuse/client and eslint.
Updates
@langfuse/clientfrom 5.3.0-beta.0 to 5.3.0Release notes
Sourced from @langfuse/client's releases.
Commits
9381615chore: release v5.3.0Updates
eslintfrom 10.2.1 to 10.3.0Release notes
Sourced from eslint's releases.
Commits
788920410.3.05b69b4fBuild: changelog update for 10.3.0d32235eci: use pnpm ineslint-flat-config-utilstype integration test (#20826)b6ae5cffix: handle unavailable require cache (#20812)3ffb14echore: clean up typos in comments and JSDoc (#20821)6fb3685fix: rule suggestions cause continuation in class body (#20787)22eb58achore: add missing continue-on-error to ecosystem-tests.yml (#20818)88bf002ci: bump pnpm/action-setup from 6.0.1 to 6.0.3 (#20815)379571afeat: add suggestions for no-unused-private-class-members (#20773)97c8c33chore: update ilshidur/action-discord action to v0.4.0 (#20811)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore <dependency name> major versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)@dependabot ignore <dependency name> minor versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)@dependabot ignore <dependency name>will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)@dependabot unignore <dependency name>will remove all of the ignore conditions of the specified dependency@dependabot unignore <dependency name> <ignore condition>will remove the ignore condition of the specified dependency and ignore conditions