chore(deps): bump versions

pyproject.toml

@@ -5,7 +5,7 @@ build-backend = "hatchling.build"
 
 [project]
 name = "validate-pyproject-schema-store"
-version = "2024.04.29"
+version = "2024.05.13"
 authors = [
   { name = "Henry Schreiner", email = "henryfs@princeton.edu" },
 ]
@@ -69,6 +69,7 @@ scikit-build = "validate_pyproject_schema_store.schema:get_schema"
 poetry = "validate_pyproject_schema_store.schema:get_schema"
 pdm = "validate_pyproject_schema_store.schema:get_schema"
 pyright = "validate_pyproject_schema_store.schema:get_schema"
+uv = "validate_pyproject_schema_store.schema:get_schema"
 
 [project.entry-points."pipx.run"]
 validate-pyproject-schema-store = "validate_pyproject.cli:main"

src/validate_pyproject_schema_store/resources/ruff.schema.json

@@ -1699,7 +1699,7 @@
           }
         },
         "sections": {
-          "description": "A list of mappings from section names to modules.\n\nBy default, imports are categorized according to their type (e.g., `future`, `third-party`, and so on). This setting allows you to group modules into custom sections, to augment or override the built-in sections.\n\nFor example, to group all testing utilities, you could create a `testing` section: ```toml testing = [\"pytest\", \"hypothesis\"] ```\n\nCustom sections should typically be inserted into the `section-order` list to ensure that they're displayed as a standalone group and in the intended order, as in: ```toml section-order = [ \"future\", \"standard-library\", \"third-party\", \"first-party\", \"local-folder\", \"testing\" ] ```\n\nIf a custom section is omitted from `section-order`, imports in that section will be assigned to the `default-section` (which defaults to `third-party`).",
+          "description": "A list of mappings from section names to modules.\n\nBy default, imports are categorized according to their type (e.g., `future`, `third-party`, and so on). This setting allows you to group modules into custom sections, to augment or override the built-in sections.\n\nFor example, to group all testing utilities, you could create a `testing` section: ```toml testing = [\"pytest\", \"hypothesis\"] ```\n\nThe values in the list are treated as glob patterns. For example, to match all packages in the LangChain ecosystem (`langchain-core`, `langchain-openai`, etc.): ```toml langchain = [\"langchain-*\"] ```\n\nCustom sections should typically be inserted into the `section-order` list to ensure that they're displayed as a standalone group and in the intended order, as in: ```toml section-order = [ \"future\", \"standard-library\", \"third-party\", \"first-party\", \"local-folder\", \"testing\" ] ```\n\nIf a custom section is omitted from `section-order`, imports in that section will be assigned to the `default-section` (which defaults to `third-party`).",
           "type": [
             "object",
             "null"
@@ -3048,6 +3048,7 @@
         "FURB11",
         "FURB110",
         "FURB113",
+        "FURB116",
         "FURB118",
         "FURB12",
         "FURB129",
@@ -3573,6 +3574,9 @@
         "PYI055",
         "PYI056",
         "PYI058",
+        "PYI059",
+        "PYI06",
+        "PYI062",
         "Q",
         "Q0",
         "Q00",
@@ -3630,6 +3634,7 @@
         "RUF1",
         "RUF10",
         "RUF100",
+        "RUF101",
         "RUF2",
         "RUF20",
         "RUF200",

src/validate_pyproject_schema_store/resources/tool.json

@@ -8,5 +8,6 @@
   "setuptools": "https://json.schemastore.org/partial-setuptools.json",
   "poetry": "https://json.schemastore.org/partial-poetry.json",
   "pdm": "https://json.schemastore.org/partial-pdm.json",
-  "pyright": "https://json.schemastore.org/partial-pyright.json"
+  "pyright": "https://json.schemastore.org/partial-pyright.json",
+  "uv": "https://json.schemastore.org/uv.json"
 }