Unpin click and packages version

[UsamaSadiq]

Description

• click and packages versions are being pinned in the PR because the upgrade was causing error in the repo before this.
• The requirements upgrade is needed for Django 5.2 upgrade so pinning the versions for now.
• Last requirements upgrade was made in the repo 2 months ago and the requirements upgrade workflow has been disabled.

TODO

• This ticket is being created to investigate and fix the upgrade issue by resolving these constraints.

[robrap]

Thanks @UsamaSadiq.

click and packages versions are being pinned in the PR because the upgrade was causing error in the repo before this.

• Is there any more details about the errors? Were they unit test failures, or bugs found in stage or production, etc.?
• Do someone need to unpin again to find out what is involved in this ticket?

Last requirements upgrade was made in the repo 2 months ago and the requirements upgrade workflow has been disabled.

Do you have more information on this, or should someone from Cosmonauts need to ticket adding back the workflow and taking on this unpin ticket?

Thank you.

[UsamaSadiq]

Thanks @UsamaSadiq.

click and packages versions are being pinned in the PR because the upgrade was causing error in the repo before this.

• Is there any more details about the errors? Were they unit test failures, or bugs found in stage or production, etc.?
• Do someone need to unpin again to find out what is involved in this ticket?

Last requirements upgrade was made in the repo 2 months ago and the requirements upgrade workflow has been disabled.

Do you have more information on this, or should someone from Cosmonauts need to ticket adding back the workflow and taking on this unpin ticket?

Thank you.

• The error will be reproduced when these constraints are removed and make upgrade is ran either locally or using CI. Here is a sample trace of it

virtualenv==20.26.3
    # via tox
pip-compile --rebuild  -o requirements/dev.txt requirements/dev.in
  ERROR: Cannot install click==8.1.8 and click==8.2.1 because these package versions have conflicting dependencies.
Traceback (most recent call last):
  File "/opt/hostedtoolcache/Python/3.11.12/x64/lib/python3.11/site-packages/pip/_vendor/resolvelib/resolvers.py", line 397, in resolve
    self._add_to_criteria(self.state.criteria, r, parent=None)
  File "/opt/hostedtoolcache/Python/3.11.12/x64/lib/python3.11/site-packages/pip/_vendor/resolvelib/resolvers.py", line 174, in _add_to_criteria
    raise RequirementsConflicted(criterion)
pip._vendor.resolvelib.resolvers.RequirementsConflicted: Requirements conflict: SpecifierRequirement('click==8.2.1'), SpecifierRequirement('click==8.1.8')

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/opt/hostedtoolcache/Python/3.11.12/x64/lib/python3.11/site-packages/pip/_internal/resolution/resolvelib/resolver.py", line 95, in resolve
    result = self._result = resolver.resolve(
                            ^^^^^^^^^^^^^^^^^
  File "/opt/hostedtoolcache/Python/3.11.12/x64/lib/python3.11/site-packages/pip/_vendor/resolvelib/resolvers.py", line 546, in resolve
    state = resolution.resolve(requirements, max_rounds=max_rounds)
            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/hostedtoolcache/Python/3.11.12/x64/lib/python3.11/site-packages/pip/_vendor/resolvelib/resolvers.py", line 399, in resolve
    raise ResolutionImpossible(e.criterion.information)
pip._vendor.resolvelib.resolvers.ResolutionImpossible: [RequirementInformation(requirement=SpecifierRequirement('click==8.2.1'), parent=None), RequirementInformation(requirement=SpecifierRequirement('click==8.1.8'), parent=None)]

• The workflow was automatically disabled because this repo wasn't updated in the last two months (default behavior of GitHub Actions to save credits). I suggest we evaluate if this repo needs any active maintenance or is it still needed or not.
• The disabled workflow can be enabled by anyone with write access in the Actions tab once this PR is merged so the upgrade job won't fail again.