Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[QA]: remove package-pinning for ansible-deploy #330

Open
kitsudaiki opened this issue May 26, 2024 · 0 comments
Open

[QA]: remove package-pinning for ansible-deploy #330

kitsudaiki opened this issue May 26, 2024 · 0 comments
Labels
Env: Deploy-Process in case the deploy-process has to be updated L: ★☆☆ Expect low difficulty QA Any tasks, witch improve the quality of the code, documentation and so on
Milestone
backlog CI

Comments

@kitsudaiki
Copy link
Owner

QA

Description

In context of issue #328 the requests pip-package was pinned to version 2.31.0 as workaround for the upstream-bug. This hard pinning should be removed again, after the conflict was resolved in the docker pip package.

Acceptance Criteria

  • the version-pin for the requests packages was removed from the CI
  • CI-pipeline is still green

Additional Information

Blocked by

How to test
@kitsudaiki kitsudaiki added QA Any tasks, witch improve the quality of the code, documentation and so on Env: Deploy-Process in case the deploy-process has to be updated L: ★☆☆ Expect low difficulty labels May 26, 2024
@kitsudaiki kitsudaiki added this to the backlog CI milestone May 26, 2024
@kitsudaiki kitsudaiki self-assigned this May 26, 2024
@kitsudaiki kitsudaiki mentioned this issue May 26, 2024
Closed
@kitsudaiki kitsudaiki removed their assignment Aug 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Env: Deploy-Process in case the deploy-process has to be updated L: ★☆☆ Expect low difficulty QA Any tasks, witch improve the quality of the code, documentation and so on
Projects
Hanami
Status: No status
Milestone
backlog CI
Development

No branches or pull requests
1 participant
@kitsudaiki