Update releases.properties from release 2026.7.11

[N6REJ]

🤖 Automated Releases Properties Update

This PR updates the releases.properties file with new versions from release 2026.7.11.

Changes:

• Extracted .7z assets from the release
• Removed stale/invalid existing URLs from releases.properties
• Added version entries with download URLs
• Maintained semver ordering (newest first)

Release URL: https://github.com/Bearsampp/module-nodejs/releases/tag/2026.7.11

Next Steps:

1. ⏳ Link validation will run automatically
2. ✅ Once validation passes, this PR will auto-merge
3. ❌ If validation fails, review logs for transient network/service issues

[qodo-code-review]

PR Summary by Qodo

Update releases.properties for Node.js release 2026.7.11

⚙️ Configuration changes 🕐 Less than 5 minutes

AI Description

• Add Node.js 26.5.0 download URL for release 2026.7.11.
• Remove stale 25.2.1 and 24.11.1 entries from the releases list.
• Keep version ordering newest-first for consumers of the properties file.

Diagram

graph TD
  A["releases.properties"] --> B(["Bearsampp updater/installer"]) --> C{{"GitHub Releases"}} --> D[".7z assets"]
  subgraph Legend
    direction LR
    _file["Config file"] ~~~ _svc(["Consumer component"]) ~~~ _ext{{"External"}} ~~~ _asset["Release asset"]
  end

Loading

High-Level Assessment

The following are alternative approaches to this PR:

1. Generate releases.properties from GitHub Releases API in CI

• ➕ Eliminates manual/stale URL drift by rebuilding the file from the source of truth
• ➕ Can enforce ordering, de-duplication, and link validation automatically
• ➖ Adds CI complexity and requires a GitHub token/rate-limit handling
• ➖ API-driven generation can be brittle if naming conventions change

2. Store only release tags and derive asset URLs at runtime

• ➕ Reduces churn in releases.properties (less frequent updates)
• ➕ Avoids hard-coding full URLs if asset naming is consistent
• ➖ Moves logic into the consumer component; harder to audit exact URLs
• ➖ Still relies on stable asset naming conventions

Recommendation: For now, the PR’s approach (directly updating releases.properties and pruning stale entries) is appropriate and low-risk. If stale URLs are a recurring problem, consider CI generation from the GitHub Releases API plus link validation as a longer-term improvement.

Files changed (1) +1 / -2

Other (1) +1 / -2

releases.propertiesAdd 26.5.0 URL and remove stale 25.2.1/24.11.1 entries +1/-2

Add 26.5.0 URL and remove stale 25.2.1/24.11.1 entries

• Adds a new mapping for Node.js 26.5.0 pointing to the 2026.7.11 GitHub release asset. Removes two older entries (25.2.1 and 24.11.1) with now-stale/invalid URLs while preserving newest-first ordering.

releases.properties

[qodo-code-review]

Code Review by Qodo

🐞 Bugs (1) 📘 Rule violations (0) 📜 Skill insights (0)

1. Removed release mappings 🐞 Bug ≡ Correctness

Description

This PR deletes the 25.2.1 and 24.11.1 entries from releases.properties, so any consumer using this
file to resolve download URLs will no longer be able to fetch those versions. This is inconsistent
with the repository still containing those version bundles/configs, making availability/version
resolution regress for those versions.

Code

releases.properties[L4-7]

-25.2.1 = https://github.com/Bearsampp/module-nodejs/releases/download/2025.12.30/bearsampp-nodejs-25.2.1-2025.12.30.7z
24.14.1 = https://github.com/Bearsampp/module-nodejs/releases/download/2026.4.12/bearsampp-nodejs-24.14.1-2026.4.12.7z
24.14.0 = https://github.com/Bearsampp/module-nodejs/releases/download/2026.3.7/bearsampp-nodejs-24.14.0-2026.3.7.7z
-24.11.1 = https://github.com/Bearsampp/module-nodejs/releases/download/2025.12.30/bearsampp-nodejs-24.11.1-2025.12.30.7z

Evidence

releases.properties is explicitly treated as the list of available releases, and the repo still
ships config/bundles for the two removed versions; removing their mappings makes those versions
non-resolvable via this release map.

.gradle-docs/README.md[186-199]
bin/nodejs25.2.1/bearsampp.conf[1-8]
bin/archived/nodejs24.11.1/bearsampp.conf[1-8]
.github/workflows/update-releases-properties.yml[1-5]
.github/workflows/update-releases-properties.yml[218-230]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
Two versions (25.2.1 and 24.11.1) were removed from `releases.properties`. If `releases.properties` is used as the authoritative version→download URL mapping, these versions can no longer be resolved/downloaded via that mechanism.

## Issue Context
The repo still contains configuration/bundles for these versions under `bin/`, which suggests they are still part of the module’s supported inventory. If the URLs were removed because they are truly gone upstream, then the repo should explicitly deprecate them (or remove/relocate their bundles) so the on-disk versions and the “available releases” mapping don’t diverge.

## Fix Focus Areas
- releases.properties[1-12]
- bin/nodejs25.2.1/bearsampp.conf[1-8]
- bin/archived/nodejs24.11.1/bearsampp.conf[1-8]
- .github/workflows/update-releases-properties.yml[218-230]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

---

[qodo-code-review]

1. Removed release mappings 🐞 Bug ≡ Correctness

This PR deletes the 25.2.1 and 24.11.1 entries from releases.properties, so any consumer using this
file to resolve download URLs will no longer be able to fetch those versions. This is inconsistent
with the repository still containing those version bundles/configs, making availability/version
resolution regress for those versions.

Agent Prompt

## Issue description
Two versions (25.2.1 and 24.11.1) were removed from `releases.properties`. If `releases.properties` is used as the authoritative version→download URL mapping, these versions can no longer be resolved/downloaded via that mechanism.

## Issue Context
The repo still contains configuration/bundles for these versions under `bin/`, which suggests they are still part of the module’s supported inventory. If the URLs were removed because they are truly gone upstream, then the repo should explicitly deprecate them (or remove/relocate their bundles) so the on-disk versions and the “available releases” mapping don’t diverge.

## Fix Focus Areas
- releases.properties[1-12]
- bin/nodejs25.2.1/bearsampp.conf[1-8]
- bin/archived/nodejs24.11.1/bearsampp.conf[1-8]
- .github/workflows/update-releases-properties.yml[218-230]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools