diesel-rs/diesel

Use the pinned manifests and affected crate implementation as the starting context, because the supplied inventory contains simplified version and backend information. Tests and CI were inspected, not executed, and this brief covers a bounded set of source paths. Future implementation work should preserve backend gates and use dedicated test databases before authorizing execution. Public API changes, generated diagnostics, schema snapshots, and embedded migration rebuilds require special attention.

• Read Cargo.toml and the affected crate manifest first: Rust 1.88.0/edition 2024, Diesel 2.3.13, four backend features, and target-specific SQLite dependencies are concrete constraints in this revision.
  Cargo.toml#L40-L43diesel/Cargo.toml#L1-L13diesel/Cargo.toml#L54-L58diesel/Cargo.toml#L89-L110
• For query-runtime changes, follow RunQueryDsl::load, LoadQuery::internal_load, backend LoadConnection, statement preparation, and row decoding before choosing an edit boundary.
  diesel/src/query_dsl/mod.rs#L1702-L1706diesel/src/query_dsl/load_dsl.rs#L62-L71diesel/src/pg/connection/mod.rs#L255-L289diesel/src/query_dsl/load_dsl.rs#L128-L148
• For CLI/schema work, read cli.rs, main.rs, config.rs, and print_schema.rs together; configuration overrides, relative paths, multi-schema context, patches, and locked-file handling all affect observable output.
  diesel_cli/src/cli.rs#L20-L44diesel_cli/src/config.rs#L29-L58diesel_cli/src/print_schema.rs#L330-L359diesel_cli/src/main.rs#L294-L325
• The inspected test sources and workflow declarations describe intended checks, not execution results: review CLI schema snapshots/compilation, migration assertions, compile-failure diagnostics, and CI configuration before planning validation.
  diesel_cli/tests/print_schema.rs#L717-L749diesel_cli/tests/migration_run.rs#L7-L32diesel_compile_tests/tests/trybuild.rs#L96-L102.github/workflows/ci.yml#L352-L375
• In authorized implementation work, start with the affected backend/test and use cargo xtask run-tests for broader checks; xtask resolves backend-specific database variables, runs migrations first, and invokes nextest with coordinated crate features.
  CONTRIBUTING.md#L124-L128xtask/src/tests/mod.rs#L186-L220xtask/src/tests/mod.rs#L224-L256
• Preserve compile-error and snapshot expectations deliberately: BLESS presence rewrites ui_test outputs, while CONTRIBUTING.md calls for reviewing insta changes; tidy and semver-checks are existing tooling entrypoints.
  diesel_compile_tests/tests/trybuild.rs#L96-L102CONTRIBUTING.md#L194-L208xtask/src/main.rs#L19-L30
• Embedded migrations have a documented rebuild trap: changes only to migration files may not rerun the procedural macro, and consuming applications should use build.rs rerun-if-changed declarations.
  diesel_migrations/migrations_macros/src/lib.rs#L105-L120
• Contribution conventions require minimal, reviewed, verified changes and AI-use disclosure; the guide reserves mentoring/good-first-issue work from AI use and asks authors to write their own PR descriptions.
  CONTRIBUTING.md#L155-L171