Update Fleet-maintained apps

[fleet-release]

Automated ingestion of latest Fleet-maintained app data.

Summary by CodeRabbit

Updates

• Updated DBeaver Community to version 26.0.5 with new installation files and verification checksums
• Updated Windsurf to version 2.3.9 with new installation files and verification checksums

[claude]

Claude Code Review

This repository is configured for manual code reviews. Comment @claude review to trigger a review and subscribe this PR to future pushes, or @claude review once for a one-time review.

_{Tip: disable this comment in your organization's Code Review settings.}

[coderabbitai]

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: be46e626-5763-4826-96b7-cc6b34bcb7d7

📥 Commits

Reviewing files that changed from the base of the PR and between dd86dc9 and 2d24914.

📒 Files selected for processing (2)

• ee/maintained-apps/outputs/dbeaver-community/darwin.json
• ee/maintained-apps/outputs/windsurf/darwin.json

---

Walkthrough

This PR updates macOS manifests for two maintained applications. DBeaver Community's darwin.json is updated from version 26.0.4 to 26.0.5, with the installer URL, SHA256 checksum, and version comparison query synchronized to the new release. Windsurf's darwin.json is similarly updated from version 2.2.17 to 2.3.9 with corresponding URL, checksum, and query adjustments. Both changes preserve existing script references and query structure.

Possibly related PRs

• fleetdm/fleet#44977: Updates macOS app manifest JSONs by bumping versions and adjusting the queries.patched version comparison plus installer_url and sha256 for updated app releases.
• fleetdm/fleet#45565: Updates macOS maintained-apps manifest entries by changing version, queries.patched version comparison, installer_url, and sha256 to match new releases.
• fleetdm/fleet#44900: Updates Fleet app macOS manifests by bumping version, queries.patched version threshold, installer_url, and sha256 in the Windsurf manifest.

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The description is minimal and lacks required sections from the template such as related issue, checklists for validation/testing/database migrations, and other process-specific items.	Add a related issue reference and complete relevant checklist items from the template, or clarify why sections don't apply to this automated data ingestion change.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title 'Update Fleet-maintained apps' is directly related to the changeset, which updates version information for two Fleet-maintained applications (DBeaver Community and Windsurf).
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.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fma-2605180020

---

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

[qodo-free-for-open-source-projects]

CI Feedback 🧐

A test triggered by this PR failed. Here is an AI-generated analysis of the failure:

Action: build (20.x)

Failed stage: Run cd website/ && BUILD_SCRIPT_ARGS="--githubAccessToken=***" npm run build-for-prod [❌]

Failed test name: ""

Failure summary: The action failed during the cd website/ && BUILD_SCRIPT_ARGS="--githubAccessToken=***" npm run build-for-prod step because the static content build (sails run build-static-content) errored while compiling markdown. - The markdown compiler detected an invalid/too-long meta description tag in articles/build-byod-security-program.md: exceeded the 150 character limit (log points to /home/runner/work/fleet/fleet/articles/build-byod-security-program.md). - The error is raised from website/scripts/build-static-content.js:706:25. - Because the build failed, the www output directory was never created; the subsequent mv www .www then failed with mv: cannot stat 'www': No such file or directory, and the job exited with code 1.

Relevant error logs: 1: ##[group]Runner Image Provisioner 2: Hosted Compute Agent ... 664: run `npm fund` for details 665: ##[group]Run cd website/ && npm test 666: �[36;1mcd website/ && npm test�[0m 667: shell: /usr/bin/bash --noprofile --norc -e -o pipefail {0} 668: env: 669: NPM_CONFIG_MIN_RELEASE_AGE: 0.5 670: ##[endgroup] 671: > @fleetdm/website@0.0.21 test 672: > npm run lint && npm run custom-tests && echo 'Done.' 673: > @fleetdm/website@0.0.21 lint 674: > ./node_modules/eslint/bin/eslint.js . --max-warnings=0 --report-unused-disable-directives && echo '✔ Your .js files look so good.' && ./node_modules/htmlhint/bin/htmlhint -c ./.htmlhintrc views/*.ejs && ./node_modules/htmlhint/bin/htmlhint -c ./.htmlhintrc views/**/*.ejs && ./node_modules/htmlhint/bin/htmlhint -c ./.htmlhintrc views/**/**/*.ejs && ./node_modules/htmlhint/bin/htmlhint -c ./.htmlhintrc views/pages/**/**/*.ejs && ./node_modules/htmlhint/bin/htmlhint -c ./.htmlhintrc views/pages/**/**/**/*.ejs && ./node_modules/htmlhint/bin/htmlhint -c ./.htmlhintrc views/pages/**/**/**/**/*.ejs && ./node_modules/htmlhint/bin/htmlhint -c ./.htmlhintrc views/pages/**/**/**/**/**/*.ejs && echo '✔ So do your .ejs files.' && ./node_modules/lesshint/bin/lesshint assets/styles/ --max-warnings=0 && echo '✔ Your .less files look good, too.' 675: ✔ Your .js files look so good. 676: Config loaded: ./.htmlhintrc 677: Config loaded: ./.htmlhintrc 678: Config loaded: ./.htmlhintrc 679: Scanned 3 files, no errors found (20 ms). 680: Config loaded: ./.htmlhintrc ... 719: Config loaded: ./.htmlhintrc 720: Config loaded: ./.htmlhintrc 721: Config loaded: ./.htmlhintrc 722: Config loaded: ./.htmlhintrc 723: Config loaded: ./.htmlhintrc 724: Config loaded: ./.htmlhintrc 725: Config loaded: ./.htmlhintrc 726: Config loaded: ./.htmlhintrc 727: Config loaded: ./.htmlhintrc 728: Config loaded: ./.htmlhintrc 729: Config loaded: ./.htmlhintrc 730: Config loaded: ./.htmlhintrc 731: Config loaded: ./.htmlhintrc 732: Config loaded: ./.htmlhintrc 733: Config loaded: ./.htmlhintrc 734: Scanned 54 files, no errors found (126 ms). 735: Config loaded: ./.htmlhintrc ... 772: Config loaded: ./.htmlhintrc 773: Config loaded: ./.htmlhintrc 774: Config loaded: ./.htmlhintrc 775: Config loaded: ./.htmlhintrc 776: Config loaded: ./.htmlhintrc 777: Config loaded: ./.htmlhintrc 778: Config loaded: ./.htmlhintrc 779: Config loaded: ./.htmlhintrc 780: Config loaded: ./.htmlhintrc 781: Config loaded: ./.htmlhintrc 782: Config loaded: ./.htmlhintrc 783: Config loaded: ./.htmlhintrc 784: Config loaded: ./.htmlhintrc 785: Config loaded: ./.htmlhintrc 786: Config loaded: ./.htmlhintrc 787: Scanned 52 files, no errors found (94 ms). 788: Config loaded: ./.htmlhintrc 789: Scanned 77 files, no errors found (130 ms). 790: Config loaded: ./.htmlhintrc 791: Scanned 77 files, no errors found (148 ms). 792: Config loaded: ./.htmlhintrc 793: Scanned 77 files, no errors found (181 ms). 794: Config loaded: ./.htmlhintrc 795: Scanned 77 files, no errors found (167 ms). 796: ✔ So do your .ejs files. 797: ✔ Your .less files look good, too. 798: > @fleetdm/website@0.0.21 custom-tests 799: > echo "(No other custom tests yet.)" && echo 800: (No other custom tests yet.) 801: Done. 802: ##[group]Run cd website/ && BUILD_SCRIPT_ARGS="--githubAccessToken=***" npm run build-for-prod 803: �[36;1mcd website/ && BUILD_SCRIPT_ARGS="--githubAccessToken=***" npm run build-for-prod�[0m 804: shell: /usr/bin/bash --noprofile --norc -e -o pipefail {0} 805: env: 806: NPM_CONFIG_MIN_RELEASE_AGE: 0.5 807: ##[endgroup] 808: > @fleetdm/website@0.0.21 build-for-prod 809: > echo 'Now compiling markdown content and building+minifying assets for production...' && echo '(Hang tight, this could take a while.)' && echo && ./node_modules/sails/bin/sails.js run build-static-content ${BUILD_SCRIPT_ARGS} && echo && node node_modules/grunt/bin/grunt buildProd || (echo && echo '------------------------------------------' && echo 'IMPORTANT! IMPORTANT! IMPORTANT!' && echo 'ERROR: Could not compile assets for production!' && echo && echo 'Please fix the issues logged above' && echo 'and push that up. Then, try deploying again.' && echo '------------------------------------------' && echo) && mv www .www && node -e 'sailsrc = JSON.parse(require("fs").readFileSync("./.sailsrc", "utf8")); if (sailsrc.paths&&sailsrc.paths.public !== undefined || sailsrc.hooks&&sailsrc.hooks.grunt !== undefined) { throw new Error("Cannot complete deployment script: .sailsrc file has conflicting contents! Please remove the conflicting stuff from .sailsrc, then commit and push that up."); } sailsrc.paths = sailsrc.paths || {}; sailsrc.paths.public = "./.www"; sailsrc.hooks = sailsrc.hooks || {}; sailsrc.hooks.grunt = false; require("fs").writeFileSync("./.sailsrc", JSON.stringify(sailsrc))' && echo 'Build is complete. Ready to deploy.' 810: Now compiling markdown content and building+minifying assets for production... 811: (Hang tight, this could take a while.) 812: info: Initializing project hook... (`api/hooks/custom/`) 813: info: Initializing `apianalytics` hook... (requests to monitored routes will be logged!) 814: info: ·• Auto-migrating... (alter) 815: info: Hold tight, this could take a moment. 816: info: ✓ Auto-migration complete. 817: Could not generate HTML partials from source files in fleetdm/fleet repo (e.g. docs in markdown, or queries in YAML), and configure metadata about the generated files so it is available in `sails.config.builtStaticContent`. 818: Error: Failed compiling markdown content: An article page has an invalid description meta tag (<meta name="description" value="How to structure a multi-platform BYOD security program, from enrollment models and access tiers to posture signals, standards, and compliance evidence.">) at "/home/runner/work/fleet/fleet/home/runner/work/fleet/fleet/articles/build-byod-security-program.md". To resolve, make sure the value of the meta description is less than 150 characters long. 819: at sails.helpers.flow.simultaneously.RELATIVE_PATH_TO_PRICING_TABLE_YML_IN_FLEET_REPO (/home/runner/work/fleet/fleet/website/scripts/build-static-content.js:706:25) 820: ------------------------------------------ 821: IMPORTANT! IMPORTANT! IMPORTANT! 822: ERROR: Could not compile assets for production! 823: Please fix the issues logged above 824: and push that up. Then, try deploying again. 825: ------------------------------------------ 826: mv: cannot stat 'www': No such file or directory 827: ##[error]Process completed with exit code 1. 828: Post job cleanup.