Ruby 4.0.0-1 release

[N6REJ]

PR Type

Enhancement

---

Description

• Add Ruby 4.0.0-1 release configuration and installation scripts

• Update bundle release version to 2026.1.16

• Remove Eclipse IDE project configuration files

• Add RubyGems installation and update batch script

---

Diagram Walkthrough

flowchart LR
  A["Ruby 4.0.0-1 Release"] --> B["Configuration Files"]
  A --> C["Installation Scripts"]
  A --> D["Cleanup"]
  B --> B1["bearsampp.conf"]
  B --> B2["rubygems.properties"]
  B --> B3["build.properties"]
  C --> C1["install.bat"]
  D --> D1["Remove Eclipse Files"]

Loading

File Walkthrough

	Relevant files
Enhancement	install.bat Add RubyGems installation batch script                                      bin/ruby4.0.0-1/rubygems/install.bat New batch script for installing and updating RubyGems Sets Ruby binary path and executes gem installation commands Includes error handling for installation failures +10/-0
Configuration changes	bearsampp.conf Add Ruby 4.0.0-1 Bearsampp configuration                                  bin/ruby4.0.0-1/bearsampp.conf New configuration file for Ruby 4.0.0-1 release Specifies Ruby executable paths and bundle release version Defines console executable and RubyGems configuration +5/-0      rubygems.properties Add RubyGems properties configuration                                        bin/ruby4.0.0-1/rubygems/rubygems.properties New properties file pointing to RubyGems update package References specific RubyGems version 4.0.4 from GitHub releases +1/-0      build.properties Update bundle release version                                                        build.properties Update bundle release version from 2025.11.23 to 2026.1.16 Remove commented build path configuration line +1/-2
Miscellaneous	.buildpath Remove Eclipse buildpath configuration                                      .buildpath Remove Eclipse IDE build path configuration file File was XML-based Eclipse project metadata +0/-4      .project Remove Eclipse project configuration                                          .project Remove Eclipse IDE project description file File contained Eclipse project metadata and build specifications +0/-11    org.eclipse.core.resources.prefs Remove Eclipse resource preferences                                            .settings/org.eclipse.core.resources.prefs Remove Eclipse IDE resource preferences file File contained Eclipse encoding and version preferences +0/-2

---

[qodo-code-review]

PR Compliance Guide 🔍

Below is a summary of compliance checks for this PR:

Security Compliance
⚪	Supply chain integrity Description: The script updates RubyGems (gem.cmd install rubygems-update.gem --local then gem.cmd update --system) without any integrity/authenticity verification (e.g., checksum/signature/pinned source), creating a supply-chain risk where a tampered or replaced rubygems-update.gem could execute attacker-controlled code during installation. install.bat [7-10] Referred Code CALL "%RUBYBINPATH%\gem.cmd" install rubygems-update.gem --local --no-document IF %ERRORLEVEL% NEQ 0 exit /b %ERRORLEVEL% "%RUBYBINPATH%\gem.cmd" update --system --no-document
	Supply chain integrity Description: RubyGems is sourced from a remote GitHub release URL without a pinned digest/signature, so compromise of the release asset or URL substitution could lead to installing a malicious rubygems-update-4.0.4.gem and executing it during the update process. rubygems.properties [1-1] Referred Code rubygems = https://github.com/Bearsampp/modules-untouched/releases/download/Ruby-2026.1.16/rubygems-update-4.0.4.gem
Ticket Compliance
⚪	🎫 No ticket provided Create ticket/issue
Codebase Duplication Compliance
⚪	Codebase context is not defined Follow the guide to enable codebase context checks.
Custom Compliance
🟢	Generic: Meaningful Naming and Self-Documenting Code Objective: Ensure all identifiers clearly express their purpose and intent, making code self-documenting Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Secure Error Handling Objective: To prevent the leakage of sensitive system information through error messages while providing sufficient detail for internal debugging. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Secure Logging Practices Objective: To ensure logs are useful for debugging and auditing without exposing sensitive information like PII, PHI, or cardholder data. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
🔴	Generic: Robust Error Handling and Edge Case Management Objective: Ensure comprehensive error handling that provides meaningful context and graceful degradation Status: Missing error checks: The script does not validate key prerequisites (e.g., gem.cmd existence) and does not check/propagate the failure code after the gem update --system step, which can result in silent or hard-to-debug failures. Referred Code CALL "%RUBYBINPATH%\gem.cmd" install rubygems-update.gem --local --no-document IF %ERRORLEVEL% NEQ 0 exit /b %ERRORLEVEL% "%RUBYBINPATH%\gem.cmd" update --system --no-document Learn more about managing compliance generic rules or creating your own custom rules
⚪	Generic: Comprehensive Audit Trails Objective: To create a detailed and reliable record of critical system actions for security analysis and compliance. Status: No audit trail: The new installation script performs system-modifying actions (RubyGems install/update) without any logging/audit trail to reconstruct what happened and with what outcome. Referred Code CALL "%RUBYBINPATH%\gem.cmd" install rubygems-update.gem --local --no-document IF %ERRORLEVEL% NEQ 0 exit /b %ERRORLEVEL% "%RUBYBINPATH%\gem.cmd" update --system --no-document Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Security-First Input Validation and Data Handling Objective: Ensure all data inputs are validated, sanitized, and handled securely to prevent vulnerabilities Status: Unverified external artifact: The RubyGems update package is referenced via an external GitHub URL without any visible integrity controls (e.g., checksum/signature pinning), requiring verification that the download/install pipeline validates the artifact. Referred Code rubygems = https://github.com/Bearsampp/modules-untouched/releases/download/Ruby-2026.1.16/rubygems-update-4.0.4.gem Learn more about managing compliance generic rules or creating your own custom rules

Compliance status legend

🟢 - Fully Compliant
🟡 - Partial Compliant
🔴 - Not Compliant
⚪ - Requires Further Human Verification
🏷️ - Compliance label

[qodo-code-review]

PR Code Suggestions ✨

Explore these optional code suggestions:

Category	Suggestion	Impact
High-level	Centralize version-specific installation logic The current approach duplicates installation and configuration files for each new Ruby version. This should be refactored into a single, parameterized script to centralize logic and reduce maintenance overhead. Examples: bin/ruby4.0.0-1/bearsampp.conf [1-5] rubyVersion = "4.0.0-1" rubyExe = "bin/ruby.exe" rubyConsoleExe = "bin/setrbvars.cmd" bundleRelease = "@RELEASE_VERSION@" bin/ruby4.0.0-1/rubygems/install.bat [1-10] @echo off set RUBYBINPATH=%~dp0..\bin pushd %RUBYBINPATH% set RUBYBINPATH=%CD% popd CALL "%RUBYBINPATH%\gem.cmd" install rubygems-update.gem --local --no-document IF %ERRORLEVEL% NEQ 0 exit /b %ERRORLEVEL% "%RUBYBINPATH%\gem.cmd" update --system --no-document Solution Walkthrough: Before: # Each version has its own set of files # bin/ruby4.0.0-1/bearsampp.conf rubyVersion = "4.0.0-1" rubyExe = "bin/ruby.exe" ... # bin/ruby4.0.0-1/rubygems/install.bat @echo off set RUBYBINPATH=%~dp0..\bin pushd %RUBYBINPATH% set RUBYBINPATH=%CD% popd CALL "%RUBYBINPATH%\gem.cmd" install ... ... After: # A single, parameterized script # scripts/install_gems.bat <version> @echo off set VERSION=%1 # Logic to find the correct ruby path based on version set RUBYBINPATH=../bin/ruby%VERSION%/bin ... CALL "%RUBYBINPATH%\gem.cmd" install ... ... # Version-specific configuration remains # config/ruby-4.0.0-1.conf rubyVersion = "4.0.0-1" rubyExe = "bin/ruby.exe" ... Suggestion importance[1-10]: 8 __ Why: The suggestion correctly identifies a structural issue of code duplication for version management, which impacts long-term maintainability, and proposes a valid architectural improvement.	Medium
Possible issue	Add CALL and error handling for update In install.bat, add CALL and an ERRORLEVEL check to the gem.cmd update command to ensure the script exits if the update fails. bin/ruby4.0.0-1/rubygems/install.bat [10] -"%RUBYBINPATH%\gem.cmd" update --system --no-document +CALL "%RUBYBINPATH%\gem.cmd" update --system --no-document +IF %ERRORLEVEL% NEQ 0 exit /b %ERRORLEVEL% Apply / Chat Suggestion importance[1-10]: 7 __ Why: The suggestion correctly points out missing error handling, which improves the script's reliability by ensuring it exits upon failure, consistent with other commands in the file.	Medium
	Quote path variable to handle spaces In install.bat, quote the %RUBYBINPATH% variable in the pushd command to prevent errors when the file path contains spaces. bin/ruby4.0.0-1/rubygems/install.bat [3] -pushd %RUBYBINPATH% +pushd "%RUBYBINPATH%" Apply / Chat Suggestion importance[1-10]: 6 __ Why: The suggestion correctly identifies a potential robustness issue where paths containing spaces would cause the script to fail and provides a simple, standard fix.	Low
More