Skip to content
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: NpgsqlRest/NpgsqlRest
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: 272d02d
Choose a base ref
...
head repository: NpgsqlRest/NpgsqlRest
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: 2ed0199
Choose a head ref
  • 1 commit
  • 9 files changed
  • 2 contributors

Commits on May 11, 2026

  1. fix: v3.15.1 — config-key validator honors mode + named-scheme typing 

    Two bug fixes around `ValidateConfigKeys`:

- `Auth:Schemes:<name>` is now validated by the scheme's `Type` field
  (Cookies / BearerToken / Jwt), not by name. Documented example names
  (short_session / api_token / admin_jwt) no longer constrain validation
  to the partial example schema, so every per-type override key validates
  cleanly under any scheme name.
- `--config` and `--validate` CLI paths now honor `Config:ValidateConfigKeys`
  mode. Previously both treated any warning as fatal regardless of mode,
  diverging from the runtime startup path. `--validate --json` gains a
  `warningsAreFatal` field.

Co-Authored-By: Claude Opus 4.7 (1M context) <[email protected]>
    @vbilopav @claude
    vbilopav and claude committed May 11, 2026
    Configuration menu
    Copy the full SHA
    2ed0199 View commit details
    Browse the repository at this point in the history
Loading