Skip to content

chore(deps): bump @pleaseai/soop-linux-arm64-musl from 0.1.22 to 0.1.33#311

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/bun/pleaseai/soop-linux-arm64-musl-0.1.33
Open

chore(deps): bump @pleaseai/soop-linux-arm64-musl from 0.1.22 to 0.1.33#311
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/bun/pleaseai/soop-linux-arm64-musl-0.1.33

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github May 20, 2026

Copy link
Copy Markdown
Contributor

Bumps @pleaseai/soop-linux-arm64-musl from 0.1.22 to 0.1.33.

Release notes

Sourced from @​pleaseai/soop-linux-arm64-musl's releases.

soop: v0.1.33

0.1.33 (2026-04-20)

Dependencies

  • The following workspace dependencies were updated
    • devDependencies
      • @​pleaseai/soop-cli bumped to 0.2.5
      • @​pleaseai/soop-encoder bumped to 0.3.3
      • @​pleaseai/soop-mcp bumped to 0.4.3
      • @​pleaseai/soop-tools bumped to 0.1.15

soop: v0.1.32

0.1.32 (2026-04-02)

Features

  • cli: integrate soop-mcp into soop mcp subcommand (#228) (8dd7426)
  • rebrand from rpg to repo please with monorepo restructure (#117) (d4b805a)
  • soop-native: split platform binaries into @​pleaseai/soop-native package (#194) (facd2ca)

Bug Fixes

  • add workspace dependencies to trigger release-please cascade bumps (#175) (ce5ff56)
  • build: fix Bun.build compile API and add robustness to generate-packages script (#131) (24e8609)
  • build: fix release build failures from wasm imports and stale artifact check (#256) (b14c5b8)
  • encoder: spread Map.entries() to array before calling toSorted (#251) (8a49ae5)
  • release: promote @​pleaseai/soop from alpha to stable 0.1.31 (#275) (f256f5d)
  • resolve bun install -g failure and correct CI command name (#135) (6af1dc3)
  • soop: strip workspace devDependencies on npm publish (#181) (c310452)
  • soop: update minimum Node.js requirement to 24 (#198) (a4cffad)

soop: v0.1.31-alpha.1

0.1.31-alpha.1 (2026-04-02)

Dependencies

  • The following workspace dependencies were updated
    • devDependencies
      • @​pleaseai/soop-cli bumped to 0.2.4
      • @​pleaseai/soop-encoder bumped to 0.3.2
      • @​pleaseai/soop-graph bumped to 0.1.12
      • @​pleaseai/soop-mcp bumped to 0.4.2
      • @​pleaseai/soop-tools bumped to 0.1.14
      • @​pleaseai/soop-zerorepo bumped to 0.1.12

... (truncated)

Commits
  • 752ee83 chore: release main (#283)
  • 29d524d chore(soop): update graph (#279)
  • 03b462e fix(encoder): spread Map before toSorted to avoid iterator error (#282)
  • 93d30eb ci(soop): add force_encode input to soop-encode workflow (#281)
  • 2aeb819 ci(soop): use @​latest tag instead of @​next for soop-encode workflow (#280)
  • 24a11a3 chore(soop): update graph (#272)
  • 266a672 chore: release main (#276)
  • f256f5d fix(release): promote @​pleaseai/soop from alpha to stable 0.1.31 (#275)
  • 5ca0783 docs: fix stale references and remove orphaned plan document (#273)
  • 5c14328 fix(build): externalize gemini-cli-core and tree-sitter-bash in binary build ...
  • Additional commits viewable in compare view

Dependabot compatibility score

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 rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Summary by cubic

Bump @pleaseai/soop-linux-arm64-musl from 0.1.22 to 0.1.33 to pull the latest Linux ARM64 musl binary and upstream fixes. Only updates packages/soop-native/package.json.

  • Migration
    • Ensure Node.js 24+ in CI/runtime if you run the soop binary on Linux ARM64 musl.

Written for commit 8b90c97. Summary will update on new commits.

Bumps [@pleaseai/soop-linux-arm64-musl](https://github.com/pleaseai/soop) from 0.1.22 to 0.1.33.
- [Release notes](https://github.com/pleaseai/soop/releases)
- [Changelog](https://github.com/pleaseai/soop/blob/main/CHANGELOG.md)
- [Commits](soop-native-v0.1.22...soop-v0.1.33)

---
updated-dependencies:
- dependency-name: "@pleaseai/soop-linux-arm64-musl"
  dependency-version: 0.1.33
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels May 20, 2026
@sonarqubecloud

Copy link
Copy Markdown

@cubic-dev-ai cubic-dev-ai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

No issues found across 1 file

Confidence score: 5/5

  • Automated review surfaced no issues in the provided summaries.
  • No files require special attention.

Re-trigger cubic

@codacy-production codacy-production Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Pull Request Overview

The PR aims to update a dependency, but no file modifications were detected in the analysis, meaning the intended version bump has not been applied. Furthermore, the update introduces a breaking change by increasing the minimum Node.js runtime requirement, which requires verification against CI/CD pipelines and deployment environments to prevent service disruption.

About this PR

  • The dependency update introduces a breaking change by increasing the minimum required Node.js version. This poses a high risk to infrastructure compatibility and must be validated before merging.
  • The PR contains no file changes. The intended dependency update has not been reflected in manifest files, and the PR cannot achieve its goal in its current state.

Test suggestions

  • Verification of the package version in the manifest files.
  • Runtime check to ensure compatibility with the updated minimum Node.js requirement.
Prompt proposal for missing tests
Consider implementing these tests if applicable:
1. Verification of the package version in the manifest files.
2. Runtime check to ensure compatibility with the updated minimum Node.js requirement.

TIP Improve review quality by adding custom instructions
TIP How was this review? Give us feedback

@codacy-production

Copy link
Copy Markdown

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

AI Reviewer: first review requested successfully. AI can make mistakes. Always validate suggestions.

Run reviewer

TIP This summary will be updated as you push new changes.

@codacy-production codacy-production Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Pull Request Overview

This PR contains a critical mismatch between its stated objective and the code changes. Although the title and description indicate an update for @pleaseai/soop-linux-arm64-musl, the changes actually modify @pleaseai/soop-darwin-arm64. This results in the primary acceptance criterion remaining unaddressed.

Additionally, native platform-specific packages must be updated in unison to prevent version drift and runtime inconsistencies across different operating systems. This PR should not be merged until the target dependency is corrected and all related platform packages are synchronized to version 0.1.33.

About this PR

  • Significant misalignment: The PR title and description state that '@pleaseai/soop-linux-arm64-musl' is being updated, but the code changes actually update '@pleaseai/soop-darwin-arm64' instead. The targeted dependency remains at its previous version.

Test suggestions

  • Verify that the version of @pleaseai/soop-linux-arm64-musl in package.json matches 0.1.33
Prompt proposal for missing tests
Consider implementing these tests if applicable:
1. Verify that the version of @pleaseai/soop-linux-arm64-musl in package.json matches 0.1.33

TIP Improve review quality by adding custom instructions
TIP How was this review? Give us feedback

Comment thread packages/soop-native/package.json Outdated
},
"optionalDependencies": {
"@pleaseai/soop-darwin-arm64": "0.1.22",
"@pleaseai/soop-darwin-arm64": "0.1.33",

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

🔴 HIGH RISK

The implementation diverges from the PR intent. This line updates '@pleaseai/soop-darwin-arm64' to 0.1.33, but the PR title and description explicitly state the intent is to bump '@pleaseai/soop-linux-arm64-musl'. All platform-specific optional dependencies (including darwin-x64 and linux-*) should be updated to version 0.1.33 simultaneously to maintain cross-platform consistency.

Try running the following prompt in your coding agent:

Update all @pleaseai/soop- optional dependencies in packages/soop-native/package.json to version 0.1.33.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants