Back to Signal Feed
CodeTracked since May 19, 2026

notebooklm-py 0.5.0 completes deprecation removals

Version 0.5.0 of notebooklm-py completed the phase-1 deprecation audit by removing remaining v0.3-era deprecated APIs and fields (including old sharing call, legacy type properties, and deprecated source/CLI params), while updating docs, changelogs, and version gates to schedule the removals for v0.6.0 and keeping `RPCError.rpc_id` and `RPCError.code` as permanent aliases.

notebooklm-pyversion 0.5.0client.notebooks.share()poll_interval

What Happened

  • Version 0.5.0 of notebooklm-py completed the phase-1 deprecation audit by removing remaining v0.3-era deprecated APIs and fields (including old sharing call, legacy type properties, and deprecated source/CLI params), while updating docs, changelogs, and version gates to schedule the removals for v0.6.0 and keeping `RPCError.rpc_id` and `RPCError.code` as permanent aliases.
  • Version 0.5.0 of notebooklm-py completed the phase-1 deprecation audit by removing remaining v0.3-era deprecated APIs and fields (including old sharing call, legacy type properties, and deprecated source/CLI params), while updating docs, changelogs, and version gates to schedule the removals for v0.6.0 and keeping `RPCError.rpc_id` and `RPCError.code` as permanent aliases.
  • 1 evidence item attached for review.

What is Different

Before

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

Now

Executed a concrete API lifecycle cleanup: removed deprecated methods/fields and compatibility shims, switched waiting API usage away from `poll_interval` to `initial_interval`, and synchronized docs/version-gate coverage so the deprecation contract is explicit, with only two explicit error-field aliases preserved.

Why Track This

Why It Matters

Developers maintaining integrations with notebooklm-py now need to migrate callsites that still use removed APIs (for example old sharing calls, `mime_type`/`poll_interval`-style parameters, and legacy source/artifact type fields), because those paths will break when deprecations are enforced at v0.6.0, while existing code reading `RPCError.rpc_id` or `RPCError.code` should continue to work. This reduces long-term API ambiguity but shifts migration work to consumers, so the key follow-up is to monitor CI and downstream clients for hidden breakages in polling, file-source, and sharing flows before the next release.

Impact

Developers maintaining integrations with notebooklm-py now need to migrate callsites that still use removed APIs (for example old sharing calls, `mime_type`/`poll_interval`-style parameters, and legacy source/artifact type fields), because those paths will break when deprecations are enforced at v0.6.0, while existing code reading `RPCError.rpc_id` or `RPCError.code` should continue to work. This reduces long-term API ambiguity but shifts migration work to consumers, so the key follow-up is to monitor CI and downstream clients for hidden breakages in polling, file-source, and sharing flows before the next release.

What To Watch Next

  • Watch whether notebooklm-py becomes a repeated pattern.
  • Track follow-up changes around AI IDE.
  • Compare future signals against this evidence trail.
  • Re-check risk flags: downstream_integrations_still_calling_removed_apis, migration_incomplete_for_polling_code_paths.
Open Topic TimelineOpen Technical EventOpen Original Sourcedownstream_integrations_still_calling_removed_apis / migration_incomplete_for_polling_code_paths / third_party_clients_not_updated_before_v0_6 / release_docs_version_gate_mismatch

Supporting Evidence

GITHUB PULL REQUESTHigh Trust

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

PR #862 implements release 0.5.0 deprecation cleanup: obsolete API members are removed or migrated, removal timelines are documented, and two RPCError identifiers remain as stable aliases.