Thank you for your contribution to Astropy! 🌌 This checklist is meant to remind the package maintainers who will review this pull request of some common things to look for.

• Do the proposed changes actually accomplish desired goals?
• Do the proposed changes follow the Astropy coding guidelines?
• Are tests added/updated as required? If so, do they follow the Astropy testing guidelines?
• Are docs added/updated as required? If so, do they follow the Astropy documentation guidelines?
• Is rebase and/or squash necessary? If so, please provide the author with appropriate instructions. Also see instructions for rebase and squash.
• Did the CI pass? If no, are the failures related? If you need to run daily and weekly cron jobs as part of the PR, please apply the "Extra CI" label. Codestyle issues can be fixed by the bot.
• Is a change log needed? If yes, did the change log check pass? If no, add the "no-changelog-entry-needed" label. If this is a manual backport, use the "skip-changelog-checks" label unless special changelog handling is necessary.
• Is this a big PR that makes a "What's new?" entry worthwhile and if so, is (1) a "what's new" entry included in this PR and (2) the "whatsnew-needed" label applied?
• At the time of adding the milestone, if the milestone set requires a backport to release branch(es), apply the appropriate "backport-X.Y.x" label(s) before merge.

Unfortunately this is causing all the wheel builds to fail - @neutrinoceros, any ideas?

Hmm looks like it is choking on an error message check but the log truncated the display.

assert err == f"Warning: failed to open {tmp} (or {Zfile}). Skipping.\n"

you need #18901 first

Oh wait, here it is: E assert "Warning: fai...n continue\n" == 'Warning: fai.... Skipping.\n'

(I've had the same problem while working on main, rebasing onto #18890 (backported as #18901) solved it)

Note that you'll also need #18888 and #18892 if you want all extra CI to go green again (boy, what a week)