> For the complete documentation index, see [llms.txt](https://docs.linuxfoundation.org/lfx/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.linuxfoundation.org/lfx/security/release-notes/lfx-security-v2.0.33-release.md).

# LFX Security V2.0.33 Release

Release Date 08/April/2022

## New Features and Bug Fixes

This sections provides you with list of new features and bug fixes for this release.

* Added Datalake Provider Interface - Abstracted Vendor vs Datalake queries
* Updated BB Vendor Repo Scan Status Queries -> migrated from GET to POST with payload to support larger queries
* Updated GitHub Webhook validation logic - tested/validated webhook secrets
* Added Redis Caching on a number of API calls to increase query performance (local, vendor, and datalake sources). Added cache invalidation logic
* Added Query Logic support for Global query on the v2 UX (search by project, CVE, CWE, GHSA, Language)
* Expanded queries on the vulnerabilities page to support filtering for issue type/title, severity, CVE, CWE, GHSA, state (fixed/not fixed)
* Updated API for BB non-inclusive language notifications (added logic to work with vendor and datalake, track notifications locally)

## Bug Fixes

NA

## Known Issues

**NA**


---

# 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.linuxfoundation.org/lfx/security/release-notes/lfx-security-v2.0.33-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.