@Ollie That pattern looks like it's already caught by Potentially bad keyword in answer and Potentially bad keyword in body Append -force to the command word(s) if you really want to add the pattern you provided.
@Mast Who knows. There's no more information than what's in the PR. Prior to running the CI testing on it (which is, of course, a prerequisite for approving it), I'd want to check to see what the changes were between the versions listed. Obviously, we'll want the CI tests to actually run. I'm also not all that thrilled with changing from specifying major versions to specifying a specific patch version.
@Makyen I'm not thrilled by any such action from a user not affiliated with the project at all, since they are not concerned about potential side-effects.
@Mast Yes, I share that feeling. It feels like just an opportunistic PR being made in order to have a PR, because they happened to see that we weren't explicitly specifying the most recent versions.
I don't know if I object to updating those specific dependencies to "current" (i.e. I haven't investigated the differences). In general, staying current is a good idea, but I'd prefer for there to be a reason stated for updating. If it was from a current contributor, I even a "just because" reason would be OK, assuming they had looked at the differences between, at least, the major versions and verified there weren't any problems introduced.
I do mind a choice to lock in a specific patch version without an indication of why that lock should exist. There can be legit reasons, but if the change in major versions is being made, then it would be normal to just change to the new major version and allow the system to maintain using the latest released version (i.e. not specifying the minor and patch).
teward/Osiris: In getting MS post information, recovered from `requests.exceptions.JSONDecodeError: [Errno Expecting value] <html> <head><title>502 Bad Gateway</title></head> <body> <center><h1>502 Bad Gateway</h1></center> <hr><center>nginx/1.18.0 (Ubuntu)</center> </body> </html> : 0`
