feat(spider-py): Bump version for release v0.2.0.

[sitaowang1998]

Description

This PR bumps version number to 0.2.0.

The release includes the following changes.

Breaking changes

• feat(spider-py)!: Use tuple for single value return. #246 Use tuple for single value return.

Bug fixes

• fix(spider-py): Enforce type checking in task input/output serialization. #240: Enforce type checking in task input/output serialization.
• feat(spider-py): Add support for deserializing output type names from bytes. #242: Add support for deserializing output type names from bytes.

Checklist

• The PR satisfies the contribution guidelines.
• This is a breaking change and that has been indicated in the PR title, OR this isn't a
  breaking change.
• Necessary docs have been updated, OR no docs need to be updated.

Validation performed

• Clp compression works end-to-end with the two patches.
• Package published to Pypi.

Summary by CodeRabbit

• Chores
  • Version bump: Updated project version from 0.1.0 to 0.2.0.

[coderabbitai]

Walkthrough

Project version in python/spider-py/pyproject.toml is bumped from 0.1.0 to 0.2.0. No other fields, dependencies, configuration, or code changes are present.

Changes

Cohort / File(s)	Summary
Version Bump python/spider-py/pyproject.toml	Version property updated from "0.1.0" to "0.2.0"

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Pre-merge checks and finishing touches

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Title Check	⚠️ Warning	The pull request title states "Bump version for release v0.2.0," which matches the actual version change documented in the raw summary (bumping from 0.1.0 to 0.2.0). However, there is a significant discrepancy: the PR objectives explicitly state that the intent is to increment the version to 0.1.1 to publish two patches (#240 and #242), not to 0.2.0. This creates a conflict where the title accurately describes the code change but contradicts the stated purpose and objectives of the pull request, making the title misleading about what the PR is intended to accomplish.	The title and the actual version change should be aligned with the stated PR objective. Either the version should be corrected to 0.1.1 (as indicated in the objectives), or the PR objectives should be updated to reflect a 0.2.0 release. The author should clarify whether this is intended to be a minor version bump (0.2.0) or a patch version bump (0.1.1), and ensure all documentation reflects the correct version.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between da957f1 and 7b700b0.

⛔ Files ignored due to path filters (1)

• python/spider-py/uv.lock is excluded by !**/*.lock

📒 Files selected for processing (1)

• python/spider-py/pyproject.toml (1 hunks)