Skip to content

update compatible versions list for CKAN 2.11.7 - #26

Merged
paulmueller merged 1 commit into
DCOR-dev:masterfrom
paulmueller-agent:update-compatible-versions
Nov 4, 2026
Merged

paulmueller merged 1 commit into
DCOR-dev:masterfrom
paulmueller-agent:update-compatible-versions

Conversation

@paulmueller-agent

Copy link
Copy Markdown

Updates resources/compatible_versions.txt for the upgrade to CKAN 2.11.7 (DCOR-dev/ansible-for-dcor#13).

New rows

ckan      ckanext-dc_log_view  ckanext-dc_serve  ckanext-dc_view  ckanext-dcor_depot  ckanext-dcor_schemas  ckanext-dcor_theme  dcor_control  dcor_shared
2.11.7    1.0.1                1.0.10            1.0.3            1.0.6               1.2.0                 1.1.5               1.17.4        1.0.4
2.11.6    1.0.1                1.0.10            1.0.3            1.0.6               1.2.0                 1.1.5               1.17.4        1.0.4
2.11.5    1.0.1                1.0.10            1.0.3            1.0.6               1.2.0                 1.1.5               1.17.4        1.0.4
  • Extension versions: these are today's releases. Each of them contains the setuptools ≥ 82 fix (guarded namespace declaration, importlib.resources), and ckanext-dcor_theme 1.1.5 additionally contains the rgb() color fix for 2.11.7 (fix: also replace colors in rgb() notation in main.css ckanext-dcor_theme#10). I checked this at the release tags.
  • dcor_control: 1.17.4 is the release that will contain this file (as 1.17.3 was for the current top row). dcor_shared is unchanged at 1.0.4.

Why also 2.11.5 and 2.11.6

get_max_compatible_version() returns the latest releases if the installed CKAN is at least the top row's version. Otherwise it needs a row with exactly the installed CKAN version. Production and dcor-dev currently run CKAN 2.11.5, which had no row. With only a 2.11.7 row, running the new dcor_control there before the CKAN upgrade (e.g. dcor update) would raise IndexError: Could not find current CKAN version 2.11.5. The new releases are backwards compatible, so 2.11.5 and 2.11.6 get the same versions. CKAN 2.11.3 keeps its previous rows.

Resolved versions with this change (e.g. ckanext-dcor_theme / ckanext-dcor_schemas):

installed CKAN result
2.11.3 1.1.4 / 1.1.0 (unchanged)
2.11.5, 2.11.6 1.1.5 / 1.2.0
2.11.7 and newer latest (None)

Tests

tests/test_update.py: new cases for 2.11.7 (latest), 2.11.6 and 2.11.5 (new releases), and 2.11.3 (previous releases). Run locally: all get_max_compatible_version cases pass, plus test_parse_compatible_versions and the invalid-version test. I skipped the existing ckan_version=None case, which needs pip in the environment.

CHANGELOG: new version 1.17.4.

🤖 Generated with Claude Code

Add the releases made for CKAN 2.11.7 (setuptools>=82 compatibility,
dcor_theme rgb colors). They also work with CKAN 2.11.5 and 2.11.6, so
these versions are listed as well. Otherwise, `get_max_compatible_version`
would raise an IndexError on servers still running CKAN 2.11.5/2.11.6,
because it matches older CKAN versions exactly.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@paulmueller
paulmueller merged commit 2b78409 into DCOR-dev:master Nov 4, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants