Skip to content
Closed
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions Cargo.toml
Original file line number Diff line number Diff line change
Expand Up @@ -255,12 +255,12 @@ lettre = { version = "0.11.23", default-features = false, features = ["builder",
# Every default feature stays off here; each member enables only the features
# its own templates need, and states why in its manifest.
minijinja = { version = "2.24", default-features = false }
miniz_oxide = "=0.8.5"
miniz_oxide = "=0.9.1"
napi = { version = "3.12.0", features = ["async", "serde-json"] }
napi-build = { version = "2.4.0" }
napi-derive = { version = "3.6.2" }
p256 = { version = "0.14", features = ["ecdsa"] }
pg_query = { version = "=6.2.1", default-features = false }
pg_query = { version = "=18.1.0", default-features = false }

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Commit the root lockfile for these version bumps

The root Cargo.lock still resolves pg_query 6.2.1, miniz_oxide 0.8.5, and saphyr-parser 0.1.0, while this commit changes their exact requirements and refreshes only the nested WASM SDK lockfile. Cargo defines --locked as asserting that Cargo.lock remains unchanged, so the root workspace's documented locked check and test commands cannot resolve this manifest and fail before compiling; regenerate and commit the root lockfile as part of the bump.

AGENTS.md reference: AGENTS.md:L292-L300

Useful? React with 👍 / 👎.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Keep reviewed SQL valid on PostgreSQL 17

Once the lockfile/build issues are corrected, this switches offline SQL validation to PostgreSQL 18.6 grammar even though BReg still supports PostgreSQL 17. validate_alter_table accepts AtAddConstraint without inspecting the new constraint options, so a reviewed step such as ALTER TABLE ... ADD CONSTRAINT ... CHECK (...) NOT ENFORCED can pass tooling validation and then fail with a syntax error during activation on a supported PostgreSQL 17 deployment. Pin validation to PostgreSQL 17 grammar or explicitly reject PostgreSQL 18-only options and add a PostgreSQL 17 migration test before taking this bump.

AGENTS.md reference: products/breg/AGENTS.md:L200-L208

Useful? React with 👍 / 👎.

pkcs1 = { version = "0.7", features = ["alloc"] }
pkcs8 = { version = "0.10" }
proptest = { version = "1" }
Expand Down Expand Up @@ -297,7 +297,7 @@ russh = { version = "=0.65.0", default-features = false, features = ["aws-lc-rs"
russh-sftp = { version = "=3.0.1" }
rustls-native-certs = { version = "0.8.4" }
ryu-js = { version = "=1.0.3" }
saphyr-parser = { version = "=0.1.0" }
saphyr-parser = { version = "=0.3.3" }

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Refresh the YAML parser vetting for 0.3.3

The maintained crates/registry-platform-yaml/README.md:427-439 still says this dependency is pinned exactly to 0.1.0 and presents version-specific unsafe-code, source-size, dependency, event-suite, and cargo deny evidence for that release. Moving the parser trust boundary to 0.3.3 without updating this section leaves the current dependency described by evidence gathered for different source and makes the documented pin false; re-vet 0.3.3 and update the parser-choice evidence alongside the bump.

AGENTS.md reference: products/platform/AGENTS.md:L14-L17

Useful? React with 👍 / 👎.

serde = { version = "1", features = ["derive"] }
serde_json = { version = "1" }
schemars = { version = "=1.2.3" }
Expand Down
28 changes: 14 additions & 14 deletions products/breg/wasm-handler-sdk/Cargo.lock

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

Loading