Back to Signal Feed
ProductionTracked since May 19, 2026

notebooklm-py 0.5.0 completes phase-1 deprecation cleanup

This change delivers notebooklm-py 0.5.0 as a cleanup-focused API update: deprecated v0.3-era APIs and shims are removed, remaining deprecations for `mime_type` and `poll_interval` are explicitly scheduled for v0.6.0, and version-gate/docs were updated to enforce the migration path.

notebooklm-py0.5.0 releaseAPI deprecationpoll_interval

What Happened

  • This change delivers notebooklm-py 0.5.0 as a cleanup-focused API update: deprecated v0.3-era APIs and shims are removed, remaining deprecations for `mime_type` and `poll_interval` are explicitly scheduled for v0.6.0, and version-gate/docs were updated to enforce the migration path.
  • This change delivers notebooklm-py 0.5.0 as a cleanup-focused API update: deprecated v0.3-era APIs and shims are removed, remaining deprecations for `mime_type` and `poll_interval` are explicitly scheduled for v0.6.0, and version-gate/docs were updated to enforce the migration path.
  • 1 evidence item attached for review.

What is Different

Before

Scattered source updates, isolated context, and manual follow-up across multiple feeds.

Now

Implemented the core deprecation-removal work by stripping legacy methods/properties/shims from the public and CLI API surface and converting the waiting API surface toward `initial_interval`, while retaining permanent aliases for `RPCError.rpc_id` and `RPCError.code` to reduce hard breakage in error handling.

Why Track This

Why It Matters

Applications and integration scripts that still depend on old notebooklm-py calls will start failing immediately after upgrading to 0.5.0 unless they migrate to the new APIs, so teams get an earlier and cleaner signal that their wrappers are no longer aligned with the supported interface. The PR also closes a planned cleanup pass by removing old compatibility baggage and documenting the v0.6.0 deadline for remaining deprecations, so operators should monitor migration failures around `client.notebooks.share()`, removed `Source/Artifact` fields, and any remaining `poll_interval` usage while validating that error-paths behave normally with only the preserved RPC error aliases.

Impact

Applications and integration scripts that still depend on old notebooklm-py calls will start failing immediately after upgrading to 0.5.0 unless they migrate to the new APIs, so teams get an earlier and cleaner signal that their wrappers are no longer aligned with the supported interface. The PR also closes a planned cleanup pass by removing old compatibility baggage and documenting the v0.6.0 deadline for remaining deprecations, so operators should monitor migration failures around `client.notebooks.share()`, removed `Source/Artifact` fields, and any remaining `poll_interval` usage while validating that error-paths behave normally with only the preserved RPC error aliases.

What To Watch Next

  • Watch whether notebooklm-py becomes a repeated pattern.
  • Track follow-up changes around LLMOps.
  • Compare future signals against this evidence trail.
  • Re-check risk flags: removed_share_api_callers_break, poll_interval_waiting_calls_still_present.
Open Topic TimelineOpen Technical EventOpen Original Sourceremoved_share_api_callers_break / poll_interval_waiting_calls_still_present / removed_metadata_properties_in_downstream_clients / migration_window_assumptions_for_v0_6_0

Supporting Evidence

GITHUB PULL REQUESTHigh Trust

teng-lin/notebooklm-py PR #862: feat(release): complete v0.5.0 deprecation removals

PR #862 removes deprecated API surfaces (`client.notebooks.share()`, legacy source/artifact type fields, old storage/shim paths), formalizes v0.6.0 removal for `--mime-type` and `poll_interval`, and updates docs/changelog/version checks while keeping `RPCError.rpc_id` and `RPCError.code` as permanent aliases.