Yuri Astrakhan

The currently used 1.75 is a bit dated (December 2023). There has been quiet a few improvements since then - most are fairly small but together adding up. For example,...

@rsheeter there are two issues: * for dependencies, your "real" current MSRV is actually 1.82 because `backtrace` 0.3.75 requires it: ```bash $ cargo msrv find --all-features --ignore-lockfile --min 1.75 Result:...

codegen just happened to determine the latest msrv. Without it, MSRV is still 1.82 because `fauntlet` uses `iter_repeat_n` feature. Without both, MSRV is 1.77 because of `klippa`. So in short...

@eeeebbbbrrrr I agree it doesn't do everything - but we should start somewhere, right? :) Let's start from some documentation, e.g. something like my YAML above can be added to...

P.S. I have used this approach for MSRV reuse before -- perhaps we can adapt it for PRGX version copying too? This code uses regex to get `rust-version` from Cargo.toml,...

@workingjubilee I am mostly concerned for the users of pgrx, not pgrx repo itself (although I am sure it can also benefit from it by reducing the CI run time)....

@workingjubilee thx, does `cargo pgrx init` take into account the current state of the `$PGRX_HOME`? I.e. would it skip download/uncompress/compile/install steps if everything is already up to date? If not,...

I tried running `cargo pgrx init` twice in a row locally, and it re-downloaded and re-compiled all PG versions. So it seems the ideal case would be to add some...

note that this might be part of our effort to introduce "treat warnings as errors" -- a mode in which any startup warning cause the app to quit. This is...

can we simply re-target `assert_compact_json_snapshot` to use this new renderer? P.S. the fewer settings we have in insta, the better - conventions over configuration :)