Skip to content

chore(release): bump to 0.7.3#52

Merged
GeiserX merged 1 commit into
mainfrom
chore/v0.7.3-release
Jul 5, 2026
Merged

chore(release): bump to 0.7.3#52
GeiserX merged 1 commit into
mainfrom
chore/v0.7.3-release

Conversation

@GeiserX

@GeiserX GeiserX commented Jul 5, 2026

Copy link
Copy Markdown
Owner

Prepares v0.7.3, shipping the deploy-command security hardening (#51):

  • Command injection fixed (CWE-78) — container commands are built as an argv list (tokenize the trusted template, substitute credentials per-token) instead of sh -c "<interpolated>", so a password/token with shell metacharacters is inert data, never executed. Verified live against all 7 command-setting services (honeygain, iproyal, packetshare, traffmonetizer, urnetwork, mysterium, storj) — each starts and the flags reach the real image entrypoint.
  • Mysterium management UI bound to 127.0.0.1 (was 0.0.0.0, exposed to the LAN under host networking).

Bumps wails.json, both package.json, and the frontend lockfile to 0.7.3. After merge, tagging v0.7.3 builds the 3-platform release.

Ships the deploy-command security hardening (S3/S2): container commands are now
built as argv with no shell, so a credential containing shell metacharacters can
no longer break a deploy or inject commands (CWE-78); Mysterium's management UI is
bound to 127.0.0.1. Verified live against all 7 command-setting services.
@coderabbitai

coderabbitai Bot commented Jul 5, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@GeiserX, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 48 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 8983877a-fb1e-4271-aa4a-7bbb22d80d57

📥 Commits

Reviewing files that changed from the base of the PR and between 0c36493 and cb441bf.

⛔ Files ignored due to path filters (1)
  • frontend/package-lock.json is excluded by !**/package-lock.json
📒 Files selected for processing (3)
  • frontend/package.json
  • package.json
  • wails.json
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch chore/v0.7.3-release

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@GeiserX GeiserX merged commit d3140e6 into main Jul 5, 2026
5 checks passed
@GeiserX GeiserX deleted the chore/v0.7.3-release branch July 5, 2026 08:00
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.

1 participant