<feed xmlns='http://www.w3.org/2005/Atom'>
<title>nvim-lspconfig/lua/lspconfig/configs/yamlls.lua, branch v2.3.0</title>
<subtitle>[no description]</subtitle>
<id>http://git.sudomsg.com/mirror/nvim-lspconfig/atom/lua/lspconfig/configs/yamlls.lua?h=v2.3.0</id>
<link rel='self' href='http://git.sudomsg.com/mirror/nvim-lspconfig/atom/lua/lspconfig/configs/yamlls.lua?h=v2.3.0'/>
<link rel='alternate' type='text/html' href='http://git.sudomsg.com/mirror/nvim-lspconfig/'/>
<updated>2025-06-08T01:20:55Z</updated>
<entry>
<title>fix(helm_ls,yamlls): support custom filetype for helm-ls #3893</title>
<updated>2025-06-08T01:20:55Z</updated>
<author>
<name>qvalentin</name>
<email>36446499+qvalentin@users.noreply.github.com</email>
</author>
<published>2025-06-08T01:20:55Z</published>
<link rel='alternate' type='text/html' href='http://git.sudomsg.com/mirror/nvim-lspconfig/commit/?id=cd864ac0d4f253602fb176772389a4eeb16f8a57'/>
<id>urn:sha1:cd864ac0d4f253602fb176772389a4eeb16f8a57</id>
<content type='text'>
</content>
</entry>
<entry>
<title>docs: use a maintained fork for `kubernetes-json-schema` in the example (#3572)</title>
<updated>2025-01-21T11:21:22Z</updated>
<author>
<name>Ferenc Géczi</name>
<email>Ferenc-@users.noreply.github.com</email>
</author>
<published>2025-01-21T11:21:22Z</published>
<link rel='alternate' type='text/html' href='http://git.sudomsg.com/mirror/nvim-lspconfig/commit/?id=32c9817cf0b507ca18dd49ee11db9f804a99e341'/>
<id>urn:sha1:32c9817cf0b507ca18dd49ee11db9f804a99e341</id>
<content type='text'>
The `instrumenta/kubernetes-json-schema` repo is apparently dead:
https://github.com/instrumenta/kubernetes-json-schema/issues/32#issuecomment-1021133568
And nobody has the credentials anymore to archive it:
https://github.com/instrumenta/kubeval/issues/268#issuecomment-1376490498
The recommended migration from instrumenta is to https://github.com/yannh/kubeconform,
see (https://github.com/instrumenta/kubernetes-json-schema/issues/32#issuecomment-1021133568)
and the recommended `kubernetes-json-schema` fork is also from the same new maintainer:
https://github.com/yannh/kubernetes-json-schema/

Signed-off-by: Ferenc Géczi &lt;ferenc.gm@gmail.com&gt;</content>
</entry>
<entry>
<title>refactor: deprecate util.find_git_ancestor</title>
<updated>2024-12-14T16:24:12Z</updated>
<author>
<name>dundargoc</name>
<email>gocdundar@gmail.com</email>
</author>
<published>2024-12-13T13:53:08Z</published>
<link rel='alternate' type='text/html' href='http://git.sudomsg.com/mirror/nvim-lspconfig/commit/?id=12d163c5c2b05e85431f2deef5d9d59a8fd8dfc2'/>
<id>urn:sha1:12d163c5c2b05e85431f2deef5d9d59a8fd8dfc2</id>
<content type='text'>
Work on https://github.com/neovim/nvim-lspconfig/issues/2079.
</content>
</entry>
<entry>
<title>refactor(docs): drop redundant default_config #3398</title>
<updated>2024-10-24T16:36:22Z</updated>
<author>
<name>Justin M. Keyes</name>
<email>justinkz@gmail.com</email>
</author>
<published>2024-10-24T16:36:22Z</published>
<link rel='alternate' type='text/html' href='http://git.sudomsg.com/mirror/nvim-lspconfig/commit/?id=5fd8b5608121d29919830e42a00ccddd9f31dadd'/>
<id>urn:sha1:5fd8b5608121d29919830e42a00ccddd9f31dadd</id>
<content type='text'>
Problem:
default_config duplicated in `docs` items.

Solution:
delete it. docgen autogenerates this now.</content>
</entry>
<entry>
<title>refactor: rename "server_configurations" =&gt; "configs" #3330</title>
<updated>2024-10-01T12:39:12Z</updated>
<author>
<name>Justin M. Keyes</name>
<email>justinkz@gmail.com</email>
</author>
<published>2024-10-01T12:39:12Z</published>
<link rel='alternate' type='text/html' href='http://git.sudomsg.com/mirror/nvim-lspconfig/commit/?id=bedb2a0df105f68a624a49b867f269b6d55a2c89'/>
<id>urn:sha1:bedb2a0df105f68a624a49b867f269b6d55a2c89</id>
<content type='text'>
Problem:
The name `server_configurations` is extremely verbose and irritatingly
formal and dogmatic. This overlong name is a constant nuisance when
reading, writing, and coding.

It's also not even correct: these configurations are just as much
"client" configurations as they are "server" configurations.

Solution:
- Rename to a shorter name.
- Leave placeholder files for any old URLs that link to the old
  location.</content>
</entry>
</feed>
