Skip to content

chore(deps): bump @pleaseai/soop-darwin-arm64 from 0.1.22 to 0.1.33#310

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

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

Conversation

@dependabot

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

Copy link
Copy Markdown
Contributor

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

Release notes

Sourced from @​pleaseai/soop-darwin-arm64'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-darwin-arm64 from 0.1.22 to 0.1.33 to pull in the latest macOS ARM64 binary and upstream fixes.

  • Migration
    • macOS arm64 environments must use Node.js >= 24.

Written for commit 21267ba. Summary will update on new commits.

Bumps [@pleaseai/soop-darwin-arm64](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-darwin-arm64"
  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.

1 issue found across 1 file

Confidence score: 3/5

  • There is a concrete cross-platform regression risk in packages/soop-native/package.json: only darwin-arm64 was bumped to 0.1.33 while other optionalDependencies remain at 0.1.22.
  • Because this issue is severity 6/10 with high confidence (9/10) and can affect users on non-macOS ARM platforms, this sits in “some risk” rather than a low-risk merge.
  • This is likely straightforward to fix by aligning all platform-specific optional dependency versions before merging.
  • Pay close attention to packages/soop-native/package.json - platform dependency versions are out of sync and may deliver inconsistent binaries across OS/architectures.
Prompt for AI agents (unresolved issues)

Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name="packages/soop-native/package.json">

<violation number="1" location="packages/soop-native/package.json:15">
P2: Only darwin-arm64 was bumped to 0.1.33; the other six optionalDependencies platform entries still reference 0.1.22. Keeping these out of sync means users on other platforms will receive an older version, which can lead to inconsistent behavior across platforms.

(Based on your team's feedback about using the full TARGETS list when syncing optionalDependencies versions.) [FEEDBACK_USED]</violation>
</file>

Reply with feedback, questions, or to request a fix.

Re-trigger cubic

},
"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.

P2: Only darwin-arm64 was bumped to 0.1.33; the other six optionalDependencies platform entries still reference 0.1.22. Keeping these out of sync means users on other platforms will receive an older version, which can lead to inconsistent behavior across platforms.

(Based on your team's feedback about using the full TARGETS list when syncing optionalDependencies versions.)

View Feedback

Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. At packages/soop-native/package.json, line 15:

<comment>Only darwin-arm64 was bumped to 0.1.33; the other six optionalDependencies platform entries still reference 0.1.22. Keeping these out of sync means users on other platforms will receive an older version, which can lead to inconsistent behavior across platforms.

(Based on your team's feedback about using the full TARGETS list when syncing optionalDependencies versions.) </comment>

<file context>
@@ -12,7 +12,7 @@
   },
   "optionalDependencies": {
-    "@pleaseai/soop-darwin-arm64": "0.1.22",
+    "@pleaseai/soop-darwin-arm64": "0.1.33",
     "@pleaseai/soop-darwin-x64": "0.1.22",
     "@pleaseai/soop-linux-x64-glibc": "0.1.22",
</file context>

@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 current PR contains no file changes, meaning the intended dependency update has not been implemented. Beyond the empty diff, the targeted update introduces a breaking change by increasing the minimum runtime version requirement. Additionally, the upstream dependency has transitioned to a new distribution model for platform-specific binaries, which may require the addition of new packages to the project. These issues should be resolved to ensure compatibility and correct installation before merging.

About this PR

  • The intended update introduces a breaking change regarding the minimum runtime version requirement. The environment configuration and CI pipelines should be checked for compatibility.
  • The PR does not contain any file changes. The package manifest and lockfile must be updated to reflect the intended dependency bump.

Test suggestions

  • Verify the dependency version is correctly updated in the manifest
  • Verify the lockfile is synchronized with the new version
  • Verify application compatibility with the updated minimum runtime requirement
Prompt proposal for missing tests
Consider implementing these tests if applicable:
1. Verify the dependency version is correctly updated in the manifest
2. Verify the lockfile is synchronized with the new version
3. Verify application compatibility with the updated minimum runtime requirement
Low confidence findings
  • The upstream package has changed how platform-specific binaries are distributed. It should be verified if an additional native package needs to be explicitly added to the project dependencies.

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

🟢 Metrics 0 complexity · 0 duplication

Metric Results
Complexity 0
Duplication 0

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.

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