dmde: Add version 4.4.4.842

[sitiom]

https://dmde.com/

• Use conventional PR title: <manifest-name[@version]|chore>: <general summary of the pull request>
• I have read the Contributing Guide

[coderabbitai]

📝 Walkthrough

Walkthrough

This pull request adds a new package manifest file bucket/dmde.json for the DMDE Windows application to the Scoop Extras repository. The manifest declares version 4.4.4.842, provides application metadata (description, homepage, and proprietary license), defines download endpoints and SHA-256 hashes for both 64-bit and 32-bit builds, configures installation artifacts (executable shortcut and INI configuration file), and establishes version detection via changelog regex and autoupdate mechanisms with parameterized URL templates for both architectures.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Suggested labels

package-request-needed

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and specifically describes the main change: adding a new version of the dmde package.
Description check	✅ Passed	The description includes required checklist items and project reference, but lacks issue/PR reference section and detailed change description.
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.}

Tip

💬 Introducing Slack Agent: The best way for teams to turn conversations into code.

Slack Agent is built on CodeRabbit's deep understanding of your code, so your team can collaborate across the entire SDLC without losing context.

• Generate code and open pull requests
• Plan features and break down work
• Investigate incidents and troubleshoot customer tickets together
• Automate recurring tasks and respond to alerts with triggers
• Summarize progress and report instantly

Built for teams:

• Shared memory across your entire org—no repeating context
• Per-thread sandboxes to safely plan and execute work
• Governance built-in—scoped access, auditability, and budget controls

One agent for your entire SDLC. Right inside Slack.

👉 Get started

---

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

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[github-actions]

All changes look good.

Wait for review from human collaborators.

dmde

• Lint
• Description
• License
• Hashes
• Checkver
• Autoupdate

Check the full log for details.

[coderabbitai]

Actionable comments posted: 1

🧹 Nitpick comments (2)

bucket/dmde.json (2)

1-1: 💤 Low value

Reminder: Verify CRLF line endings.

Scoop manifests must use CRLF (\r\n) line endings. Please ensure your editor is configured to use CRLF for JSON files in this repository.

Most Git configurations will handle this automatically via .gitattributes, but it's worth verifying if you encounter any issues.

As per coding guidelines: "Line Endings: Scoop manifests must use CRLF line endings. Remind the contributor if you detect LF."

🤖 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/dmde.json` at line 1, dmde.json currently uses LF endings; convert
this Scoop manifest to CRLF (\r\n) line endings, update and recommit the file,
and ensure your editor or Git settings enforce CRLF for JSON (e.g., set
core.autocrlf or add a .gitattributes entry like *.json eol=crlf) so future
changes keep CRLF for the dmde.json manifest.

---

1-37: Testing instructions for the manifest.

Before merging, please test the manifest locally using these commands:

1. Optional: Enable debug mode (helps with troubleshooting)

scoop config debug true

2. Test version detection and autoupdate

.\bin\checkver.ps1 -App dmde -f

3. Auto-format the manifest

.\bin\formatjson.ps1 -App dmde

4. Test installation for both architectures

# Test 64-bit installation
scoop install .\bucket\dmde.json -a 64bit

# After testing, uninstall
scoop uninstall dmde

# Test 32-bit installation
scoop install .\bucket\dmde.json -a 32bit

5. Verify the application launches correctly

• Check that the shortcut is created in the Start Menu
• Verify that dmde.ini is persisted correctly across reinstalls

As per coding guidelines: "Provide clear instructions for testing the manifest locally before submission."

🤖 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/dmde.json` around lines 1 - 37, Add the required "Testing instructions
for the manifest" to the PR description (or commit message) so reviewers can
validate dmde.json locally: include steps to enable debug (scoop config debug
true), run version detection/autoupdate check (.\bin\checkver.ps1 -App dmde -f),
run formatter (.\bin\formatjson.ps1 -App dmde), install/uninstall both
architectures (scoop install .\bucket\dmde.json -a 64bit; scoop uninstall dmde;
scoop install .\bucket\dmde.json -a 32bit), and verify the shortcut and persist
file (dmde.ini) persist across reinstalls; reference the manifest symbols like
"dmde.json", "checkver", "autoupdate", "shortcuts", and "persist" so reviewers
know what to validate.

🤖 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/dmde.json`:
- Around line 1-5: This new manifest (dmde.json) is missing a package-request
issue link; create a package request issue (using the provided template) and add
the issue number or full URL to the PR description or the manifest's
description/PR body, then update the PR to include that link; ensure the package
meets the acceptance criteria (stable release, English docs/interface,
reasonably well-known) before proceeding.

---

Nitpick comments:
In `@bucket/dmde.json`:
- Line 1: dmde.json currently uses LF endings; convert this Scoop manifest to
CRLF (\r\n) line endings, update and recommit the file, and ensure your editor
or Git settings enforce CRLF for JSON (e.g., set core.autocrlf or add a
.gitattributes entry like *.json eol=crlf) so future changes keep CRLF for the
dmde.json manifest.
- Around line 1-37: Add the required "Testing instructions for the manifest" to
the PR description (or commit message) so reviewers can validate dmde.json
locally: include steps to enable debug (scoop config debug true), run version
detection/autoupdate check (.\bin\checkver.ps1 -App dmde -f), run formatter
(.\bin\formatjson.ps1 -App dmde), install/uninstall both architectures (scoop
install .\bucket\dmde.json -a 64bit; scoop uninstall dmde; scoop install
.\bucket\dmde.json -a 32bit), and verify the shortcut and persist file
(dmde.ini) persist across reinstalls; reference the manifest symbols like
"dmde.json", "checkver", "autoupdate", "shortcuts", and "persist" so reviewers
know what to validate.

🪄 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: 56f42422-ecee-4ef9-935f-bbe138a743c6

📥 Commits

Reviewing files that changed from the base of the PR and between ae4eff8 and 0d9bd6b.

📒 Files selected for processing (1)

• bucket/dmde.json