check-async-need

Name: check-async-need
Availability: InStock
Author: aio-libs

Classify botocore version bumps as no-port, port-required, or ambiguous for aiobotocore.

1.4k|208|Updated May 31, 2015

Search Tags:#version compatibility #version bump #code classification #botocore #aiobotocore

Ready to run

npx skills add https://github.com/aio-libs/aiobotocore --skill check-async-need

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: check-async-need
Source: https://github.com/aio-libs/aiobotocore/tree/main/plugins/aiobotocore-bot/skills/check-async-need
Command: npx skills add https://github.com/aio-libs/aiobotocore --skill check-async-need

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git, python, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the classification of botocore version bumps as no-port, port-required, or ambiguous, providing an efficient way to decide if code changes are needed for aiobotocore compatibility.

Core Features & Use Cases

Version Classification: Diffs botocore tags to determine the level of compatibility needed for aiobotocore updates.
Function Analysis: Inspects every added/changed function in overridden files for async contamination and emits classification results.
Use Case: Integrate this Skill into your CI/CD pipeline to ensure botocore updates don't break aiobotocore functionality before release.

Quick Start

Use the check-async-need skill with the following command:

check-async-need --from=1.42.84 --to=1.42.89

Frequently Asked Questions about check-async-need

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I check if a botocore version bump requires async code changes for aiobotocore?▼

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.

How does async contamination analysis work for overridden botocore functions?▼

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.

Can I integrate botocore version compatibility checks into my CI/CD pipeline?▼

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.

What does no-port, port-required, or ambiguous classification mean for aiobotocore updates?▼

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.

Do I need git and Python installed to classify botocore version bumps?▼

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.