[bhoy-troy]

Upgrade to Fedora 44 and Python 3.14 with Code Modernization

Summary

Ugrades Content Resolver to Fedora 44 and Python 3.14, while modernizing the codebase with f-string formatting and improved Docker build efficiency. Addresses the issues identified in #105.

Changes

1. Infrastructure Upgrades

Container Images:

• ✅ Dockerfile: fedora:42 → fedora:44
• ✅ GitHub Actions CI: fedora:41 → fedora:44 ─

Docker Improvements:

• ✅ Added .dockerignore to reduce build context (excludes cache, output, IDE files)
• ✅ Enhanced DNF cache management in Dockerfile
• ✅ Improved build layer efficiency ─

2. Python Code Modernization

Python 3.14 changed the default multiprocessing start method from fork to forkserver for improved safety. However, forkserver requires all objects to be picklable. DNF repository objects contain SWIG-wrapped C objects (SwigPyObject) that cannot be pickled,
causing this error:

TypeError: cannot pickle 'swig_runtime_data5.SwigPyObject' object

Solution:
Added explicit multiprocessing.set_start_method('fork'). This forces Python 3.14 to use the traditional fork method (same as Python ≤3.13), avoiding the need to pickle DNF objects, will need to be fixed for future versions.

• Set multiprocessing start method to fork (instead of default forkserver)
• F-string Conversion* faster string formatting performance
• Reduced code base size
• Improved readability ─

3. GitHub Actions Node.js 24 Support

Problem:
GitHub Actions announced deprecation of Node.js 20:

• Warning starts: Now (April 2026)
• Removal date: September 16, 2026

Solution:
Set FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable to opt into Node.js 24 early. This:

• Eliminates deprecation warnings
• Ensures CI continues working after Sept 2026
• Uses the latest Node.js runtime for better performance

Reference: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

[bhoy-troy]

Closing for now, seems to be breaking changes with how concurrency is handled in Python 3.14

https://docs.python.org/3/whatsnew/3.14.html#concurrent-futures

[yselkowitz]

@bhoy-troy if the rest of these changes are safe even on f42/py3.13, perhaps we could handle those first without the f44/py3.14 change?

[bhoy-troy]

@yselkowitz , I have set content-resolver to use fork as the multiprocessing entry, this was default in Python <= 3.13. We'll need to make changes to be able to use the the 3.14 default of forkserver, we'll need to handle the pickling.

[yselkowitz]

@yselkowitz , I have set content-resolver to use fork as the multiprocessing entry, this was default in Python <= 3.13. We'll need to make changes to be able to use the the 3.14 default of forkserver, we'll need to handle the pickling.

Please make a new ticket for that against this repo.

[yselkowitz]

The changes look good, and I successfully tested this on my flatpak CR repo. If you could please just fix the commit message of the string formatting (currently commit d7d005c) so that the first line (commit title) is of standard length, and squash the typo fix (currently commit fbc60b2) into that. There should be no net change to the code, just cleaner commits.