Repository navigation
update compatible versions list for CKAN 2.11.7 - #26
Merged
paulmueller merged 1 commit intoNov 4, 2026
Merged
Conversation
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>
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
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.
Updates
resources/compatible_versions.txtfor the upgrade to CKAN 2.11.7 (DCOR-dev/ansible-for-dcor#13).New rows
importlib.resources), and ckanext-dcor_theme 1.1.5 additionally contains thergb()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_sharedis 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 newdcor_controlthere before the CKAN upgrade (e.g.dcor update) would raiseIndexError: 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):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: allget_max_compatible_versioncases pass, plustest_parse_compatible_versionsand the invalid-version test. I skipped the existingckan_version=Nonecase, which needspipin the environment.CHANGELOG: new version 1.17.4.
🤖 Generated with Claude Code