Skip to content

Bump @lokalise/backend-http-client from 9.0.0 to 10.0.0 #331

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.

Sign up for GitHub

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 1 commit into from
Nov 24, 2025
Merged

Bump @lokalise/backend-http-client from 9.0.0 to 10.0.0 #331

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -61,7 +61,7 @@
"devDependencies": {
"@amplitude/analytics-types": "^2.10.0",
"@biomejs/biome": "^1.9.4",
"@lokalise/backend-http-client": "^9.0.0",
"@lokalise/backend-http-client": "^10.0.0",
Copy link

@coderabbitai coderabbitai bot Nov 17, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🔴 Critical

🧩 Analysis chain

Verify compatibility and test coverage for the major version bump.

A major version bump typically introduces breaking changes. Since this is a development dependency, the risk is lower, but the test suite and development tooling should be validated to ensure no breakage.

Please verify the following before merging:

  1. Run the full test suite: Ensure all tests pass with the new version.

    npm run test:ci

  2. Check for security advisories: Verify there are no security vulnerabilities in the new version.

    npm audit --omit=prod

  3. Validate breaking changes: Review the CHANGELOG or release notes for @lokalise/backend-http-client 10.0.0 to understand what breaking changes were introduced and confirm the codebase is compatible.

If there are API changes in the new version that affect how tests or development tools use this package, those changes will need to be reflected in the codebase.


---

🏁 Script executed:

```shell
#!/bin/bash
# Find usages of @lokalise/backend-http-client in the codebase
echo "=== Searching for @lokalise/backend-http-client usage ==="
rg -i "lokalise.*backend.*http" -n --type=ts --type=js --type=json

echo ""
echo "=== Checking package.json test scripts ==="
cat package.json | grep -A 20 '"scripts"'

echo ""
echo "=== Full devDependencies section ==="
cat package.json | grep -A 50 '"devDependencies"'

Length of output: 2630

🌐 Web query:

@lokalise/backend-http-client 10.0.0 breaking changes

💡 Result:

I couldn't find a 10.0.0 release for @lokalise/backend-http-client. The npm package's latest published version is 7.2.0 (package page). [1] Historic listings (Libraries.io / npm archive) likewise show v7.x as the published major line. [2]

If you expected a v10.0.0 release, options:

  • Check the repository (github.com/lokalise/shared-ts-libs) for a changelog or unreleased/branch tags.
  • If you want, I can search the repo releases/tags and changelogs for any mention of a v10.0.0 or breaking-change notes — shall I do that?

Sources:
[1] npm package page for @lokalise/backend-http-client (shows v7.2.0).
[2] Libraries.io / package history for @lokalise/backend-http-client (shows v7.x releases).


---

🏁 Script executed:

```shell
#!/bin/bash
# Check for npm configuration, registry setup, or monorepo structure
echo "=== Checking for .npmrc or npm configuration ==="
find . -maxdepth 2 -name ".npmrc" -o -name ".npmrc.example" 2>/dev/null | head -20

echo ""
echo "=== Checking for monorepo setup (package.json workspaces) ==="
cat package.json | grep -A 5 '"workspaces"'

echo ""
echo "=== Checking for lerna.json or pnpm-workspace.yaml ==="
ls -la lerna.json pnpm-workspace.yaml 2>/dev/null

echo ""
echo "=== Checking git log for recent version changes to this dependency ==="
git log --oneline -n 20 -- package.json 2>/dev/null | head -10

echo ""
echo "=== Checking if there's a lock file that shows resolved version ==="
if [ -f "package-lock.json" ]; then
  echo "package-lock.json found. Checking @lokalise/backend-http-client entry:"
  grep -A 10 '"@lokalise/backend-http-client"' package-lock.json | head -15
elif [ -f "yarn.lock" ]; then
  echo "yarn.lock found. Checking @lokalise/backend-http-client entry:"
  grep -A 5 '@lokalise/backend-http-client' yarn.lock | head -10
else
  echo "No lock file found"
fi

Length of output: 741

🌐 Web query:

@lokalise/backend-http-client latest npm registry version 2025

💡 Result:

As of November 17, 2025 the latest npm registry version of @lokalise/backend-http-client is 7.2.0. [1][2]

Sources:

  • npm package page (version 7.2.0). [1]
  • yarnpkg listing (shows 7.0.0, published June 9, 2025). [2]

Version 10.0.0 of @lokalise/backend-http-client does not exist on npm and will cause installation failures.

The public npm registry only has version 7.2.0 as the latest release. Versions 9.0.0 and 10.0.0 do not exist. Without a configured private registry or lock file, npm will fail to resolve the dependency. This will block the build and prevent tests from running.

The version in package.json line 64 must be corrected to an actual published version (e.g., ^7.2.0 or the appropriate version that contains the required APIs used in the test files).

🤖 Prompt for AI Agents 
In package.json around line 64, the dependency "@lokalise/backend-http-client":
"^10.0.0" references a non-existent npm version and will break installs; change
the version to a published release (for example "^7.2.0" or the specific version
your code relies on), run npm install to verify resolution, and update
package-lock.json/yarn.lock accordingly before committing.

"@lokalise/background-jobs-common": "^14.0.2",
"@lokalise/biome-config": "^2.0.0",
"@lokalise/node-core": "^14.4.2",
Expand Down