Extend tests with PQC coverage - #1535
Conversation
d9078c4 to
f6bdfb4
Compare
|
@pedro-psb See: the "phase out" test removal |
|
Does not test: actually verifying the signatures on sync, since that requires more involved fixture changes. I can file an issue for that if desired. |
Assisted-By: Codex 5.6 Luna
Damn, it worked... |
| # All things django and asyncio are deliberately left to pulpcore | ||
| # Example transitive requirements: asgiref, asyncio, aiohttp | ||
| "pulpcore>=3.113.0,<3.130", | ||
| "pulpcore>=3.117.2,<3.130", |
|
@pedro-psb Does this mean we should backport this to our supported branches, since the CI Update wants to raise the floor, which triggers the reminder test? e.g.: #1543 |
I'm not sure why pulpbot started bumping pulpcore's lowerbound. We usually do that manually when we have a reason to. I guess I'm missing something... But if you really wanna bump it on supported branches, then sure, backport the test removal. |
@pedro-psb: I am going to drop a link to what @mdellweg told me here: #1542 (comment) |
|
Oh, that makes some sense. Thanks |
Assisted-By: Codex 5.6 Luna
📜 Checklist
See: Pull Request Walkthrough