> For the complete documentation index, see [llms.txt](https://staylime.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://staylime.com/docs/volume-themes/changelog/volume-release-notes/volume-5.1.0.md). # Volume 5.1.0 Volume 5.1.0 release notes — fixes for breadcrumbs, collection filters, the sticky cart, the free shipping bar, and product media thumbnails. #### Released December 8, 2025 ### Fixed * Corrected an issue where breadcrumbs showed an incorrect parent category. * Fixed improper behavior of both vertical and horizontal filters on collection pages. * Hid the sticky cart Change button when no visible variant picker is available on the product page. * Resolved Liquid syntax errors. * Ensured the Free shipping bar remains hidden when the minimum threshold is set as the string "0". * Fixed the thumbnail rail not auto-scrolling to the active thumbnail when product media changed. * Restored missing link styling inside pop-up blocks. * Fixed an issue that prevented media from appearing inside the info card. * Other minor bug fixes. --- # 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://staylime.com/docs/volume-themes/changelog/volume-release-notes/volume-5.1.0.md?ask=&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.