check-async-need

To check if a botocore version bump requires async code changes for aiobotocore, run the check-async-need script with the --from and --to version flags. It diffs botocore tags and classifies the update as no-port, port-required, or ambiguous.

Async contamination analysis works by inspecting every added or changed function in overridden botocore files using git diff. It evaluates asynchronous programming patterns to determine if aiobotocore compatibility is broken by the version bump.

Yes, you can integrate botocore version compatibility checks into your CI/CD pipeline using Bash and Python scripting. Running the classification script ensures botocore updates do not break aiobotocore functionality before release.

No-port, port-required, and ambiguous classifications indicate whether aiobotocore needs code changes for a botocore version bump. No-port means no changes needed, port-required means changes are necessary, and ambiguous requires manual inspection.

Yes, you need git and Python installed to classify botocore version bumps. The Skill utilizes Bash and Python scripting along with git diff functionality to compare version tags and inspect overridden files for async contamination.