Skip to content

dbx: Add version 0.5.24#17914

Open
t8y2 wants to merge 2 commits into
ScoopInstaller:masterfrom
t8y2:add-dbx
Open

dbx: Add version 0.5.24#17914
t8y2 wants to merge 2 commits into
ScoopInstaller:masterfrom
t8y2:add-dbx

Conversation

@t8y2

@t8y2 t8y2 commented May 29, 2026

Copy link
Copy Markdown

DBX is a lightweight, cross-platform database management tool.

Description: 15MB, lightweight, cross-platform database client. Supports MySQL, PostgreSQL, SQLite, Redis, MongoDB, DuckDB, ClickHouse, SQL Server and more.

Closes #17915

Note

This manifest was previously distributed via t8y2/scoop-bucket — this PR migrates it to the official Scoop Extras bucket.

@coderabbitai

coderabbitai Bot commented May 29, 2026

Copy link
Copy Markdown

Review Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 2863eb59-8a6d-4391-a724-8419fae4e9ea

📥 Commits

Reviewing files that changed from the base of the PR and between 51d9f5b and 0af834c.

📒 Files selected for processing (1)
  • bucket/dbx.json
🚧 Files skipped from review as they are similar to previous changes (1)
  • bucket/dbx.json

📝 Walkthrough

Walkthrough

The PR updates bucket/dbx.json to version 0.5.24, changing the top-level version, the x64 installer download URL, and the x64 SHA256 hash. The autoupdate x64 URL template now interpolates $version; installer/uninstaller args and other JSON structure are unchanged.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Suggested labels

package-request-needed

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name Status Explanation Resolution
Description check ⚠️ Warning The description is missing the required conventional PR title checkbox and lacks explicit confirmation of having read the Contributing Guide, as specified in the template. Add the required checkbox items from the template: confirm use of conventional PR title format and reading of the Contributing Guide before merging.
✅ Passed checks (4 passed)
Check name Status Explanation
Title check ✅ Passed The title directly reflects the main change: adding version 0.5.24 for the dbx package to the bucket configuration.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.


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 and usage tips.

@coderabbitai coderabbitai Bot added the package-request-needed Create a package request issue before raising PR. Check the criteria for a package to be accepted. label May 29, 2026

@coderabbitai coderabbitai 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.

Actionable comments posted: 2

🧹 Nitpick comments (1)
bucket/dbx.json (1)

1-29: Local validation steps before merge

Please run manifest checks locally:

scoop config debug true
scoop config gh_token <your-github-token>
.\bin\checkver.ps1 -App dbx -f
.\bin\formatjson.ps1 -App dbx
scoop install bucket\dbx.json -a 64bit

Reference:

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@bucket/dbx.json` around lines 1 - 29, Run the local manifest validation steps
described in the review: enable scoop debug and set GH token, then run
.\bin\checkver.ps1 -App dbx -f to validate checkver, .\bin\formatjson.ps1 -App
dbx to normalize JSON, and attempt install with scoop install bucket\dbx.json -a
64bit; while doing this, confirm the "checkver" github URL and "autoupdate"
pattern correctly detect the latest "version" and that
"architecture"/"installer"/"uninstaller" fields (especially the installer args
and 64bit url template) work as expected, fixing any mismatches or formatting
issues discovered.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@bucket/dbx.json`:
- Line 5: The package metadata uses a deprecated bare SPDX identifier in the
"license" field ("AGPL-3.0"); update that value to a modern SPDX expression such
as "AGPL-3.0-only" or "AGPL-3.0-or-later" in bucket/dbx.json by replacing the
"license" value accordingly (choose the variant that matches the upstream
project's intended licensing).
- Line 3: Update the new manifest (the "description" value in bucket/dbx.json)
to include a link to the corresponding Scoop package-request issue (or add a
clear reference in the PR body) so intake policy is satisfied; specifically,
modify the description string for the manifest entry (the "description" field in
dbx.json) to append the package-request URL (created via the provided
package-request template link) or add a short "package_request" note in the
manifest metadata pointing to the issue URL and ensure the PR body references
that same issue.

---

Nitpick comments:
In `@bucket/dbx.json`:
- Around line 1-29: Run the local manifest validation steps described in the
review: enable scoop debug and set GH token, then run .\bin\checkver.ps1 -App
dbx -f to validate checkver, .\bin\formatjson.ps1 -App dbx to normalize JSON,
and attempt install with scoop install bucket\dbx.json -a 64bit; while doing
this, confirm the "checkver" github URL and "autoupdate" pattern correctly
detect the latest "version" and that "architecture"/"installer"/"uninstaller"
fields (especially the installer args and 64bit url template) work as expected,
fixing any mismatches or formatting issues discovered.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 4d4628fd-4d85-4244-b21c-6c1ab8551c80

📥 Commits

Reviewing files that changed from the base of the PR and between 62b7d20 and 51d9f5b.

📒 Files selected for processing (1)
  • bucket/dbx.json

Comment thread bucket/dbx.json
@@ -0,0 +1,29 @@
{
"version": "0.5.24",
"description": "Lightweight, cross-platform database management tool",

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

⚠️ Potential issue | 🟠 Major | ⚡ Quick win

Link a package-request issue for this new manifest.

This is a newly added app manifest, but I don’t see a linked package-request issue in the manifest description or PR body. Please add one to satisfy intake policy for new packages.

Use:

As per coding guidelines, new manifest submissions must reference a valid package-request issue.

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@bucket/dbx.json` at line 3, Update the new manifest (the "description" value
in bucket/dbx.json) to include a link to the corresponding Scoop package-request
issue (or add a clear reference in the PR body) so intake policy is satisfied;
specifically, modify the description string for the manifest entry (the
"description" field in dbx.json) to append the package-request URL (created via
the provided package-request template link) or add a short "package_request"
note in the manifest metadata pointing to the issue URL and ensure the PR body
references that same issue.

Comment thread bucket/dbx.json Outdated
arvdk added a commit to arvdk/Extras that referenced this pull request Jun 9, 2026
@aliesbelik aliesbelik removed the package-request-needed Create a package request issue before raising PR. Check the criteria for a package to be accepted. label Jun 9, 2026
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.

[Request]: dbx

2 participants