Upgrade to CKAN 2.10 #4209
Description
Turning this into an epic
User Story
In order to utilize latest CKAN patches, data.gov admins want CKAN updated to 2.10.
Acceptance Criteria
[ACs should be clearly demoable/verifiable whenever possible. Try specifying them using BDD.]
- GIVEN catalog is upgraded
WHEN I go to https://catalog.data.gov/api/action/status_show
THEN ckan version shows 2.10.0 (or equivalent)
Background
https://github.com/GSA/catalog.data.gov/blob/main/ckan/requirements.txt#L11
#4113
See email on CKAN mailing list:
Hi all,
If all goes according to plan, next Wednesday 15th February around 13:00 UTC (14:00 CET, 08:00 EST) we will be releasing the next stable version of CKAN, 2.10, as well as patch releases for the 2.9 line (2.9.8).
Users are strongly encouraged to always run on the latest patch release for their version, as these include important security and
stability fixes. The latest patch release is the only one supported by the CKAN team (patch releases don't contain backwards incompatible changes).
More information about CKAN releases can be found here:
http://docs.ckan.org/en/latest/maintaining/upgrading/index.html#ckan-releases
Best,
Adrià
Security Considerations (required)
None
Sketch
This will be a major lift, and will require picking up the work again here: #4113
Ideally every extension should test against 2.10, and verify things work. If they don't work, a new issue may be created to investigate further.
Final step will be upgrading catalog, and may require docker changes (among others).
Metadata
Metadata
Assignees
Type
Projects
Status