Newly changed custom pager setting in config.yml breaks custom pager

[MurtadhaInit]

Describe the bug

So the schema in my config file recently showed me that using the paging key is now deprecated and that I need to change to pagers which is a list of pagers.
So I did, but now lazygit seems to not pick the pager (it's like there is no custom pager). And curiously reverting to the old setting still works.

This is the new (non-working) setting:

git:
  pagers:
      # see: delta --help
    - pager: delta --paging=never --side-by-side
      colorArg: always

And this is the old (still working) setting:

git:
  paging:
      # see: delta --help
    pager: delta --paging=never --side-by-side
    colorArg: always

To Reproduce

Steps to reproduce the behavior:
Updating old config files to use the new format as per the instructions in the docs.

Expected behavior

Custom pagers to work exactly as before, as nothing fundamentally changes except for the format in the config file.

Screenshots

Version info:

commit=, build date=, build source=Homebrew, version=0.55.1, os=darwin, arch=arm64, git version=2.51.0
git version 2.51.0

Additional context

Nothing 😅 it was a simple change.

[stefanhaller]

Not a bug. This is an unfortunate consequence of how the jsonschema store references the master version of our json schema, which already reflects a change that we will make with the next release. This release hasn't happened yet.

You need to keep the old paging config for now, and the best you can do is to ignore the error message in the editor. Once the new version gets released (probably on Nov 1st), your config will be auto-migrated for you, so there will be nothing to do.

[MurtadhaInit]

Not a bug. This is an unfortunate consequence of how the jsonschema store references the master version of our json schema, which already reflects a change that we will make with the next release. This release hasn't happened yet.

You need to keep the old paging config for now, and the best you can do is to ignore the error message in the editor. Once the new version gets released (probably on Nov 1st), your config will be auto-migrated for you, so there will be nothing to do.

Thank you for the quick reply! I was so confused by this and I spent time trying a bunch of things (even re-read the docs a couple of times thinking I must have missed something).

[stefanhaller]

As I said, the situation is unsatisfactory, but I don't really know what we can do to improve it. After all, your editor doesn't know which version of lazygit you are using. For example, if you were running a self-compiled build from current master, then the json schema would totally match that and be correct. Conversely, if you were using an older version of lazygit, the json schema would also not match that, but for other reasons.

[MurtadhaInit]

As I said, the situation is unsatisfactory, but I don't really know what we can do to improve it. After all, your editor doesn't know which version of lazygit you are using. For example, if you were running a self-compiled build from current master, then the json schema would totally match that and be correct. Conversely, if you were using an older version of lazygit, the json schema would also not match that, but for other reasons.

Yes, you're absolutely right. And I also don't see any possible workaround for this.

[SamEdwardes]

To avoid config changes you can pin the yaml schema to your config:

# yaml-language-server: $schema=https://raw.githubusercontent.com/jesseduffield/lazygit/refs/tags/v0.55.1/schema/config.json
git:
  paging:
    colorArg: always
    pager: delta --paging=never