ci+meta: modernize supported versions (CI matrix + minimum requirements) for next - #358
Merged
Conversation
dkastl
force-pushed
the
ci/modernize-test-matrix
branch
4 times, most recently
from
June 9, 2026 16:09
a37ae4f to
b7aec57
Compare
Test each supported Redmine version against the still-in-support Ruby versions it allows (https://redmine.jp/tech_note/supported-rubies/; 3.1/3.2 are EOL): - 6.0-stable -> Ruby 3.3 - 6.1-stable -> Ruby 3.3, 3.4 - Drop 5.1-stable (no currently supported Ruby) and master - PostGIS (postgis/postgis): span PG 15/17/18 + PostGIS 3.4/3.5/3.6 (13-3.4 & 17-3.5 -> 15-3.4, 17-3.5, 18-3.6) - system_test row on 6.1-stable + Ruby 3.4 - Drop the now-dead 5.1-stable rgeo gem-version override step
dkastl
force-pushed
the
ci/modernize-test-matrix
branch
from
June 9, 2026 16:12
b7aec57 to
6fcc155
Compare
dkastl
changed the title
Now that 5.1-stable is dropped from CI, align the documented/enforced minimums: - init.rb: requires_redmine 5.1.0 -> 6.0.0 - README: Redmine >= 6.0.0, add Ruby >= 3.3, PostgreSQL >= 13 -> 15, PostGIS >= 3.0 -> 3.4, NodeJS v18 -> >= 22 - CI: install Node 22 (setup_20.x -> setup_22.x) to match the README minimum (Node 20 nears EOL; 22 is current LTS)
dkastl
force-pushed
the
ci/modernize-test-matrix
branch
from
June 9, 2026 16:21
1bdd098 to
d7944a0
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
The supported-version story on
nexthad drifted: CI pinned EOL Ruby and PostgreSQL 13 / PostGIS 3.4, still tested5.1-stable(no supported Ruby left), and the documented/enforced minimums (README,requires_redmine) were stale.What
CI matrix (
test-postgis.yml) — test each supported Redmine version against the Ruby versions it supports (redmine.jp supported-rubies), limited to Rubies still in upstream support (3.1 EOL 2025-03, 3.2 EOL 2026-03):Each runs across
postgis/postgis15-3.4,17-3.5,18-3.6(PG 15/17/18 × PostGIS 3.4/3.5/3.6) → 9 jobs + the 6.1/Ruby-3.4 system_test. Drops5.1-stable+masterand the dead5.1-stablergeo override step. CI now installs Node 22 (was 20).Minimum requirements (kept consistent with the above):
init.rb:requires_redmine5.1.0->6.0.0.README:Redmine >= 6.0.0, addRuby >= 3.3,PostgreSQL >= 13 -> 15,PostGIS >= 3.0 -> 3.4,NodeJS v18 -> >= 22.Notes
postgis/postgis:{15-3.4,17-3.5,18-3.6},ruby:{3.3,3.4}-bullseye.masterdropped (it floats); can re-add as an allow-failure row for a forward signal.