> For the complete documentation index, see [llms.txt](https://cloakedkeys.gitbook.io/ofsc/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cloakedkeys.gitbook.io/ofsc/installation/release-info.md).

# Release Info

This page provides an overview of the different release types, versioning, and file formats for OF-Scraper.

## Release Types

OF-Scraper uses distinct release types to indicate stability and origin.

### Continuous Development Builds (Snapshot Releases)

These releases are generated directly from recent commits on development branches (like `main`). They represent the absolute latest state of the codebase and typically include a commit hash in their name.

* Naming Convention: Often includes a branch name, a short commit hash, and the **date of the associated commit for chronological sorting** (e.g., 3.13.dev8-a70aca3e)
* **Stability:** These are bleeding-edge versions and may contain new features, bug fixes, or unresolved issues. They are primarily for testing and development.
* **Example Tag:** `main-9e54ed3-1749940070`

### Pre-release Versions (e.g., `X.Y.Z.devN`)

These releases are designated as "semi-stable" and are pushed for broader testing before a full stable release. They typically follow a `major.minor.patch.devN` numbering scheme.

* **Naming Convention:** Follows the format `major.minor.patch.devN` (e.g., `3.7.0.dev0`).
* **Stability:** More stable than continuous development builds, but still undergoing testing.
* **Example Version:** `3.7.0.dev0`

### Stable Releases (Numbered)

These are production-ready versions of OF-Scraper, thoroughly tested and considered stable for general use. They mark a specific commit as a reliable release point.

* **Naming Convention:** Standard semantic versioning (e.g., `X.Y.Z`, like `3.6.0`).
* **Stability:** Highly stable and recommended for most users.
* **Example Version:** `3.6.0`

***

## Release Distributions

### Python Package

This fork is published to PyPI as **`ofscraper-community`**, starting with 3.16.2. The command is still `ofscraper`. The `ofscraper` package there is upstream's last release (3.14.7). See [UV Install](/ofsc/installation/uv-install.md).

<https://pypi.org/project/ofscraper-community/>

### Docker Images

Multi-arch Docker images are hosted on **GitHub Container Registry**

<https://github.com/cloakedkeys/OF-Scraper-Community/pkgs/container/of-scraper-community>

### Binaries

Each release has binaries on **GitHub** for Windows, macOS, and Linux

<https://github.com/cloakedkeys/OF-Scraper-Community/releases>

#### Release Files

Binaries include various file types **compatible with different platforms**

#### Example Files

Below is an illustrative list of files you might find in a release, with common naming patterns.

* `ofscraper_windows_3_16_1.exe` (Windows executable) and `ofscraper_windows_3_16_1.zip` (Windows zip)
* `ofscraper_linux_3_16_1` and `ofscraper_linux_3_16_1.zip` (Linux)
* `ofscraper_macos_3_16_1` and `ofscraper_macos_3_16_1.zip` (macOS)


---

# 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://cloakedkeys.gitbook.io/ofsc/installation/release-info.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.