[package]
# 0.2.0 closes two defects that live in the extension's SQL, not in the library:
# TRUNCATE emptied the record (FOR EACH ROW triggers do not fire on it) and two
# concurrent commits of the same proposal both ran it. Copying a new .so does
# NOT apply either of them to a database where the extension already exists, and
# leaving the version at 0.1.0 would mean PostgreSQL had no way to know it should
# update -- the catalog saying one thing while the contents say another, which is
# the exact failure this family of extensions exists to close.
#
# 0.2.1 changes no SQL and still bumps: verify.rs now refuses a CTE that writes (max_rows
# did not see its rows) and set_config() inside a proposal (it moved the context a
# row-level policy reads). Same version, different behaviour, is the same lie.
name = "pg_agent_gate"
version = "0.2.1"

edition = "2021"
description = "Agents propose, PostgreSQL decides: a native gate between LLM agents and the database"
license = "Apache-2.0"

[lib]
crate-type = ["cdylib"]

# PostgreSQL 18 is the floor: dry_run shows the before and after of every row
# with RETURNING old/new, which does not exist earlier.
[features]
default = ["pg19"]
pg18 = ["pgrx/pg18", "pgrx-tests/pg18"]
pg19 = ["pgrx/pg19", "pgrx-tests/pg19"]
pg_test = []

[dependencies]
pgrx = "=0.19.2"
serde_json = "1"

[dev-dependencies]
pgrx-tests = "=0.19.2"

[profile.dev]
panic = "unwind"

[profile.release]
panic = "unwind"
opt-level = 3
lto = "fat"
codegen-units = 1