Thank you for opening a Pull Request! Before submitting your PR, there are a few things you can do to make sure it goes smoothly:

• Make sure to open an issue as a bug/issue before writing your code! That way we can discuss the change, evaluate designs, and agree on the general idea
• Ensure the tests and linter pass
• Code coverage does not decrease (if any source code was changed)
• Appropriate docs were updated (if necessary)

Fixes #<issue_number_goes_here> 🦕

Description

This PR adds a minimal PEP 561-compatible type stub for the google.cloud.storage package to provide better static typing information to editors and type checkers (Pylance / Pyright). The stub exposes the package-level API surface that most callers rely on (Client, Bucket, Blob, Batch, and version) with conservative, correct annotations.

Files changed

• Added: init.pyi

What this contains

• Package-level PEP 561 stub with:
  • version: str
  • Batch class (constructor, finish)
  • Blob class (constructor, common properties and a few methods)
  • Bucket class (constructor, blob/get_blob/create/from_string)
  • Client class (constructor, create_anonymous_client, properties, bucket/batch helpers, get_service_account_email)

Motivation

• Many editor/type-checker complaints originate from dynamic module behavior and lack of top-level type information. Adding a package-level .pyi gives Pylance/Pyright precise signatures for common entry points and reduces false positives for callers importing google.cloud.storage.

Testing / How to validate locally (Windows PowerShell)

• From repository root:
  • Ensure pyright is installed (npm): npm i -g pyright
  • Run pyright on the workspace: pyright
  • Open the repo in VS Code and ensure Pylance picks up the stub (py.typed file).

Checklist

• Add package-level .pyi to expose public API
• (Optional) Add py.typed marker and update packaging