# 1.Shebang

```yaml
#!/SBUILD ver @v1.0.0
_disabled: false
_rolling: false
```

## Fields

### `#!/SBUILD ver @${VERSION}`

Version assertion for the linter/runner. (**TYPE**: <mark style="color:green;">**`RECOMMENDED`**</mark>)

### `_disabled`

Disable the script. (**TYPE**: <mark style="color:red;">**`ENFORCED`**</mark>)

* `false` - Script is enabled (default)
* `true` - Script is disabled

When disabled, specify a reason:

```yaml
_disabled: true
_disabled_reason:
  abandoned:
    - date: "2024-12-31"
      reason: "No longer maintained"
```

Reason types: `abandoned`, `broken`, `deprecated`, `dmca`, `insecure`, `replaced`

### `_rolling`

Mark as rolling release for periodic rebuilds. (**TYPE**: <mark style="color:blue;">**`NON_ENFORCED`**</mark>)

```yaml
_rolling: true
x_exec:
  pkgver: |
    echo "nightly-$(date +%Y%m%d)"
```

Used for packages without versioned releases (nightly builds, git HEAD, etc.).


---

# Agent Instructions: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.pkgforge.dev/sbuild/specification/1.shebang.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.