feat(client)!: remove blocked_instrumentation_scopes

[hassiebp]

What does this PR do?

• Removes the deprecated blocked_instrumentation_scopes argument from Langfuse, LangfuseResourceManager, get_client and LangfuseSpanProcessor. Use should_export_span instead:
  should_export_span=lambda span: is_default_export_span(span) and (span.instrumentation_scope is None or span.instrumentation_scope.name not in blocked)
• create_prompt(is_active=...): the parameter was already gone, so only its leftover docstring entry is removed.
• host / LANGFUSE_HOST keep working as before, with no warning.

Tests: the two tests that existed only for the deprecated argument are removed. The app-root test that used a blocked scope now filters the same scope via should_export_span, so the "filtered parent → child becomes app root" coverage stays. A new test pins that LANGFUSE_HOST keeps working without logging a warning.

Stack: based on prepare-v5-release; #1927, #1928 and #1930 are merged.

Type of change

• Bug fix
• New feature
• Breaking change
• Refactor
• Documentation update
• Tooling, CI, or repo maintenance

Verification

uv run --frozen ruff check .                       # All checks passed!
uv run --frozen mypy langfuse --no-error-summary   # clean
uv run --frozen pytest -q tests/unit/test_initialization.py  # 20 passed
uv run --frozen pytest -n auto tests/unit          # 715 passed, 2 skipped

Checklist

• I self-reviewed the diff using code_review.md.
• I added or updated tests for behavior changes.
• I updated docs, examples, or .env.template if needed.
• I did not hand-edit generated files; if generated files changed, I used the upstream regeneration path.
• I did not commit secrets or credentials.

  

Confidence Score: 5/5

The PR appears safe to merge; no actionable issue was identified in the changed behavior.

Summary

The PR removes the deprecated blocked-instrumentation-scopes setting throughout client initialization and span processing, leaving should_export_span as the filtering mechanism. It also warns when a deprecated host setting determines the base URL, updates filtering tests, and removes a stale prompt-parameter description.

_{Reviews (1) · Last reviewed commit: "feat(client)!: remove blocked_instrument..."}

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-10-06T14:32:40.289610Z	466808b	PR opened

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[github-actions]

@claude review

[claude]

Claude Code Review

No review was started: this request came from a bot account. Manual reviews can only be requested by someone with write access to this repository. Ask a maintainer to comment @claude review, or have your automation post the comment from a user account with write access.

_{Tip: disable this comment in your organization's Code Review settings.}

[claude]

Nothing blocking. The comments below are optional suggestions. There is no need to push a fix for them before merging.