From 1b6286d7b433f94ae904ecf647a12d59c42e9b0b Mon Sep 17 00:00:00 2001 From: "dependabot[bot]" <49699333+dependabot[bot]@users.noreply.github.com> Date: Tue, 10 Dec 2024 15:12:00 +0000 Subject: [PATCH] Update ansible requirement from <11,>=10 to >=10,<12 Updates the requirements on [ansible](https://github.com/ansible-community/ansible-build-data) to permit the latest version. - [Changelog](https://github.com/ansible-community/ansible-build-data/blob/main/docs/release-process.md) - [Commits](https://github.com/ansible-community/ansible-build-data/compare/10.0.0...11.1.0) --- updated-dependencies: - dependency-name: ansible dependency-type: direct:production ... Signed-off-by: dependabot[bot] --- requirements.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/requirements.txt b/requirements.txt index d98d7ea..812047c 100644 --- a/requirements.txt +++ b/requirements.txt @@ -20,7 +20,7 @@ # jumping to another major version without testing, since there are # often breaking changes across major versions. This is the reason # for the upper bound. -ansible>=10,<11 +ansible>=10,<12 # ansible-core 2.16.3 through 2.16.6 suffer from the bug discussed in # ansible/ansible#82702, which breaks any symlinked files in vars, # tasks, etc. for any Ansible role installed via ansible-galaxy.