> For the complete documentation index, see [llms.txt](https://docs.bindplane.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bindplane.com/changelog/october-2024/2024-10-09-release.md).

# 2024-10-09-Release

Version 1.76.0 • OCT 09, 2024

## Upgrade Notes

### Agent Version Support

{% hint style="warning" %}
**IMPORTANT**

[Couchbase source](https://github.com/observIQ/bindplane-docs/blob/main/integrations/sources/couchbase.md) need to take care when upgrading their Bindplane Collector. This is due to changes to the [OpenTelemetry Transformation Language](https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/pkg/ottl/README.md) (OTTL) which impact the Couchbase source.
{% endhint %}

BindPlane v1.76.0 is required for Bindplane Collector v1.63.0 or newer. Users with BindPlane agent version v1.60.0 or older must upgrade to v1.61.0 or v1.62.0 before upgrading to v1.63.0.

If you are not using the [Couchbase source](https://github.com/observIQ/bindplane-docs/blob/main/integrations/sources/couchbase.md), you can ignore Agent Version Support upgrade notes.

## New Features

* [Honeycomb Refinery Destination](https://github.com/observIQ/bindplane-docs/blob/main/integrations/destinations/honeycomb-refinery.md)
* Configurable [minimum TLS version](#minimum-tls-version)

## Minimum TLS Version

When using TLS, BindPlane defaults to a minimum TLS version of `1.3`. Users can opt into TLS 1.2\
for supporting client devices that do not support TLS 1.3.

To configured TLS 1.2, update `network.tlsMinVersion` string value to `"1.2"`.

```yaml
network:
  tlsMinVersion: '1.2'
```


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.bindplane.com/changelog/october-2024/2024-10-09-release.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.