Skip to content

Conversation

@ggainey
Copy link
Contributor

@ggainey ggainey commented Jan 8, 2026

No description provided.

@quba42
Copy link
Collaborator

quba42 commented Jan 8, 2026

Hmm. Nightly tests are green, so these test failures do appear to be a consequence of the new pulpcore version. @hstct Or do you have any other ideas? Have you seen test failures like this before?

@ggainey
Copy link
Contributor Author

ggainey commented Jan 8, 2026

core/3.100 allows Django5.2 and django-import-export/4. d-i-e/4 has a different behavior than /3 did - it can pass a value of None into the modelresource.render() calls, which never happens in the /3 codepath. #1378 will fix the problem.

With core/3.100, an installation can use either Django4 or Django5 - which is Important, because Django4.2 is going EOL in April.

@ggainey ggainey closed this Jan 8, 2026
@ggainey ggainey reopened this Jan 8, 2026
@hstct hstct merged commit 56b4fd1 into pulp:main Jan 8, 2026
30 of 38 checks passed
@patchback
Copy link

patchback bot commented Jan 8, 2026

Backport to 3.8: 💚 backport PR created

✅ Backport PR branch: patchback/backports/3.8/56b4fd189cae71433a8c3c078fb8b8f7fb8be7fc/pr-1377

Backported as #1380

🤖 @patchback
I'm built with octomachinery and
my source is open — https://github.com/sanitizers/patchback-github-app.

patchback bot pushed a commit that referenced this pull request Jan 8, 2026
Update to allow core/3.100.

(cherry picked from commit 56b4fd1)
ggainey added a commit that referenced this pull request Jan 8, 2026
…ae71433a8c3c078fb8b8f7fb8be7fc/pr-1377

[PR #1377/56b4fd18 backport][3.8] Update to allow core/3.100.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants