Skip to content

Conversation

@mariolenz
Copy link
Collaborator

Now that 12.0.0 is out, I think we should create the directory for the next major version.

This is just quick'n'dirty without checking if we wanted to remove any collections from 13. We can do this later IMHO.

@felixfontein
Copy link
Contributor

We can do this later IMHO.

Linter says no ;-)

@mariolenz
Copy link
Collaborator Author

We can do this later IMHO.

Linter says no ;-)

I'll have a look tomorrow. Will be AFK soon.

@mariolenz
Copy link
Collaborator Author

@felixfontein I think I've fixed one problem (with ibm.qradar) but the linter still has a problem with google.cloud. I'm not sure what to do there... should I just remove the complete removal section? I guess this will fix the sanity test, but I'm not sure if this is the right thing to do.

Co-authored-by: Felix Fontein <felix@fontein.de>
@mariolenz
Copy link
Collaborator Author

Thanks @felixfontein! I wasn't sure if dropping this would be OK, or if we should keep it documented somewhere or somehow.

@mariolenz mariolenz merged commit d567c52 into ansible-community:main Sep 10, 2025
5 checks passed
@mariolenz mariolenz deleted the v13-dir branch September 10, 2025 17:38
@felixfontein
Copy link
Contributor

@mariolenz thanks for working on this!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

2 participants