Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

#

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Jump to bottom

Upgrade Catalog to use CKAN 2.10.7 #5078

Closed
4 tasks
FuhuXia opened this issue Feb 7, 2025 · 2 comments
Closed
4 tasks

Upgrade Catalog to use CKAN 2.10.7 #5078

FuhuXia opened this issue Feb 7, 2025 · 2 comments
Assignees
@FuhuXia
Labels
bug Software defect or bug

Comments

@FuhuXia
Copy link
Member

FuhuXia commented Feb 7, 2025

User Story

Upgrade Catalog to use CKAN 2.10.7

Acceptance Criteria

[ACs should be clearly demoable/verifiable whenever possible. Try specifying them using BDD.]

  • Catalog CKAN status shows ckan_version: "2.10.7"
  • Finished harvest jobs.
  • QA done, focusing on changes from the changelog.
  • Catalog requirement.in file is updated with ckan upstream.

Sketch

[Notes or a checklist reflecting our understanding of the selected approach]
@FuhuXia FuhuXia added the bug Software defect or bug label Feb 7, 2025
@Bagesary
Copy link

This is to address the vulnerability

@Bagesary Bagesary moved this to 📟 Sprint Backlog [7] in data.gov team board Feb 13, 2025
@btylerburton btylerburton moved this from 📟 Sprint Backlog [7] to 📥 Queue in data.gov team board Feb 27, 2025
@FuhuXia
Copy link
Member Author

FuhuXia commented Mar 20, 2025

we are moving to ckan 2.11

@FuhuXia FuhuXia closed this as completed Mar 20, 2025
@github-project-automation github-project-automation bot moved this from 📥 Queue to ✔ Done in data.gov team board Mar 20, 2025
# for free to join this conversation on GitHub. Already have an account? # to comment
Assignees

@FuhuXia FuhuXia

Labels
bug Software defect or bug
Projects
data.gov team board
Status: ✔ Done
Milestone
No milestone
Development

No branches or pull requests
2 participants
@FuhuXia @Bagesary