mirror of
https://github.com/discourse/discourse.git
synced 2026-08-12 05:37:26 +08:00
9d144cac4bWhen security fixes are staged for the main branch via the `stage_security_fixes` task, the development version is now automatically incremented (e.g. `2026.2.0-latest` to `2026.2.0-latest.1`). This ensures each security fix batch gets its own tagged version, allowing docker_manager to detect that installations on `latest` need a critical update. To support this, a new `ReleaseUtils::Version` value object encapsulates version parsing, comparison, and manipulation logic that was previously done through ad-hoc string splitting and `Gem::Version` comparisons in release.rake. It understands Discourse's versioning scheme (major.minor.patch-pre.revision) and provides methods like `#next_revision`, `#same_development_cycle?`, and `#next_development_cycle`. All existing rake tasks have been refactored to use `Version` objects, the unused `parse_current_version` helper and `prepare_next_version_branch` task have been removed, and the release specs have been rewritten following RSpec style guide conventions. |
||
|---|---|---|
| .. | ||
| assets_precompile_spec.rb | ||
| compatibility_spec.rb | ||
| destroy_spec.rb | ||
| hashtags_spec.rb | ||
| incoming_emails_spec.rb | ||
| migrate_advanced_search_banner_to_welcome_banner_spec.rb | ||
| posts_spec.rb | ||
| qunit_cli_spec.rb | ||
| redis_spec.rb | ||
| release_spec.rb | ||
| themes_spec.rb | ||
| topic_localizations_spec.rb | ||
| topics_spec.rb | ||
| uploads_spec.rb | ||
| users_spec.rb | ||
