Update version numbers for Python and TypeScript SDKs to 0.1.1 and 2.…

[xav-db]

…0.5 respectively

Greptile Summary

This PR bumps the version of the Python SDK from 0.1.0 to 0.1.1 and the TypeScript SDK from 2.0.3 to 2.0.5.

• The Python SDK receives a standard sequential patch bump (0.1.0 → 0.1.1).
• The TypeScript SDK skips 2.0.4 and lands on 2.0.5, which may be intentional (e.g., 2.0.4 was already published with a defect) but should be confirmed.

Important Files Changed

Filename	Overview
sdks/python/pyproject.toml	Patch version bump from 0.1.0 to 0.1.1 — straightforward and sequential.
sdks/typescript/package.json	Version bumped from 2.0.3 to 2.0.5, skipping 2.0.4 — may be intentional but worth confirming.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[Python SDK] --> B["0.1.0 → 0.1.1 ✅ sequential patch"]
    C[TypeScript SDK] --> D["2.0.3 → 2.0.5 ⚠️ skips 2.0.4"]

Loading

%%{init: {'theme': 'base', 'themeVariables': {"darkMode": true, "background": "#0d1117", "primaryColor": "#21262d", "primaryTextColor": "#e6edf3", "primaryBorderColor": "#8b949e", "lineColor": "#8b949e", "textColor": "#e6edf3", "edgeLabelBackground": "#161b22", "actorBkg": "#21262d", "actorBorder": "#8b949e", "actorTextColor": "#e6edf3", "actorLineColor": "#8b949e", "signalColor": "#8b949e", "signalTextColor": "#e6edf3", "noteBkgColor": "#373320", "noteBorderColor": "#d4a72c", "noteTextColor": "#f0e6c0", "labelBoxBkgColor": "#21262d", "labelBoxBorderColor": "#8b949e", "labelTextColor": "#e6edf3", "loopTextColor": "#e6edf3", "activationBkgColor": "#30363d", "activationBorderColor": "#8b949e"}}}%%
flowchart TD
    A[Python SDK] --> B["0.1.0 → 0.1.1 ✅ sequential patch"]
    C[TypeScript SDK] --> D["2.0.3 → 2.0.5 ⚠️ skips 2.0.4"]

Loading

_{Reviews (1): Last reviewed commit: "Update version numbers for Python and Ty..." | Re-trigger Greptile}

Greptile also left 1 inline comment on this PR.

[greptile-apps]

Skipped version 2.0.4

The TypeScript SDK jumps from 2.0.3 directly to 2.0.5, skipping 2.0.4. While this may be intentional (e.g., 2.0.4 was already published with an issue and needs to be avoided), it's worth confirming this is deliberate rather than a typo.

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!