Doc mismatch: Update trace's release using `span.update_trace` is not possible

[camfarineau]

Hi 👋 ,

Fyi according to the doc, it is possible to update the trace's release directly in a span: https://github.com/langfuse/langfuse-docs/blame/7902579eaf4b446d8911ca7db65ea5487378522f/pages/docs/tracing-features/releases-and-versioning.mdx#L66C15-L66C15

But it does not appears to be the case in the code as of version 3.0.3 of python SDK: https://github.com/langfuse/langfuse-python/blob/42e38c68e0e303bca6ee7500fdc4f6c968456b51/langfuse/_client/span.py#L177

[dosubot[bot]]

You're right—there's a mismatch between the docs and the Python SDK v3.0.3. The documentation claims you can update a trace's release directly in a span using span.update_trace(release="...") see here, but the SDK code at that version doesn't actually support this functionality. The .update_trace() method does exist for updating some trace attributes (like input, output, user_id, session_id, tags, metadata, and version), but not release specifically example. So, the docs are currently misleading for this use case.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}   

[hassiebp]

Thanks for raising this, we will take a look!