Update docs site for version 2.29.0.dev0 (#399)

Author: WorkerPants

docs/docs/javascript/overview/package.mdx

@@ -65,3 +65,36 @@ Similarly, build scripts can be introduced to Pants via the
 as a way to introduce artifacts generated via bundlers and/or compilers installed and ran via your package manager.
 The result can the be consumed by other targets as either `resource`-targets that can be depended on,
 or as a package for the [docker backend](../../docker/index.mdx).
+
+### Running
+
+Runnable scripts can be specified and invoked through Pants via the `run` goal. This is meant to support scripts
+that are not directly tied to testing or packaging workflows.
+
+Given a `package.json` that defines a runnable script, e.g.
+
+```json title="package.json"
+{
+    "name": "@my-company/pkg",
+    "scripts": {
+        "start": "node server.js"
+    }
+}
+```
+
+we can define the build symbol [`node_run_script`](../../../reference/build-file-symbols/node_run_script), e.g.
+
+```python title="BUILD"
+package_json(
+    name="pkg",
+    scripts=[
+        node_run_script(entry_point="start"),
+    ],
+)
+```
+
+which allows us to run the script via the `pants` cli, e.g.
+
+```sh title="Shell"
+pants run :pkg#start
+```

docs/docs/jvm/java-and-scala.mdx

@@ -441,7 +441,7 @@ jvm-default = "semanticdb"
 :::note Scalafix and Scala 3
 At the moment the support for Scalac 3 in Scalafix is limited, most of the syntactic rules work but not that many in the semantic front.
 
-Despite those raugh edges, Scalafix is a great linting tool for Scala 3, just note that the setup is different than from prior versions: Instead of adding a scalac plugin to our build, we only need to add the `-Xsemanticdb` flag to our `[scalac].args` settings to enable the generation of `.semanticdb` compiled files.
+Despite those rough edges, Scalafix is a great linting tool for Scala 3, just note that the setup is different than from prior versions: Instead of adding a scalac plugin to our build, we only need to add the `-Xsemanticdb` flag to our `[scalac].args` settings, or  or the appropriate entry in `[scalac].args_for_resolve, to enable the generation of `.semanticdb` compiled files.
 :::
 
 ## Working in an IDE

docs/reference/build-file-symbols/__defaults__.mdx

@@ -10,6 +10,6 @@ import BuildFileSymbol from "@site/src/components/reference/BuildFileSymbol";
 
 Provide default field values.
 
-Learn more https://www.pantsbuild.org/2.28/docs/using-pants/key-concepts/targets-and-build-files#field-default-values
+Learn more https://www.pantsbuild.org/2.29/docs/using-pants/key-concepts/targets-and-build-files#field-default-values
 
 </BuildFileSymbol>

docs/reference/build-file-symbols/node_build_script.mdx

@@ -6,7 +6,7 @@ description: |
 
 import BuildFileSymbol from "@site/src/components/reference/BuildFileSymbol";
 
-<BuildFileSymbol name={`node_build_script`} signature={`(entry_point: 'str', output_directories: 'Iterable[str]' = (), output_files: 'Iterable[str]' = (), extra_caches: 'Iterable[str]' = (), extra_env_vars: 'Iterable[str]' = ()) -> 'NodeBuildScript'`}>
+<BuildFileSymbol name={`node_build_script`} signature={`(entry_point: 'str', output_directories: 'Iterable[str]' = (), output_files: 'Iterable[str]' = (), extra_caches: 'Iterable[str]' = (), extra_env_vars: 'Iterable[str]' = (), description: 'str | None' = None, tags: 'Iterable[str]' = ()) -> 'NodeBuildScript'`}>
 
 A build script, mapped from the `scripts` section of a package.json file.
 

docs/reference/build-file-symbols/node_run_script.mdx

@@ -0,0 +1,15 @@
+---
+title: node_run_script
+description: |
+  A script that can be run directly via the run goal, mapped from the `scripts` section of a package.json file.
+---
+
+import BuildFileSymbol from "@site/src/components/reference/BuildFileSymbol";
+
+<BuildFileSymbol name={`node_run_script`} signature={`(entry_point: 'str', extra_env_vars: 'Iterable[str]' = ()) -> 'NodeRunScript'`}>
+
+A script that can be run directly via the run goal, mapped from the `scripts` section of a package.json file.
+
+This allows running any script defined in package.json directly through pants run.
+
+</BuildFileSymbol>

docs/reference/global-options.mdx

@@ -212,7 +212,7 @@ remote_provider = <RemoteProvider>`}
   default_repr={`reapi`}
 >
 
-The type of provider to use, if using a remote cache and/or remote execution, See https://www.pantsbuild.org/2.28/docs/using-pants/remote-caching-and-execution for details.
+The type of provider to use, if using a remote cache and/or remote execution, See https://www.pantsbuild.org/2.29/docs/using-pants/remote-caching-and-execution for details.
 
 Each provider supports different `remote_store_address` and (optional) `remote_execution_address` URIs.
 
@@ -288,7 +288,7 @@ tag = [
   default_repr={`[]`}
 >
 
-Include only targets with these tags (optional &#x27;+&#x27; prefix) or without these tags (&#x27;-&#x27; prefix). See https://www.pantsbuild.org/2.28/docs/using-pants/advanced-target-selection.
+Include only targets with these tags (optional &#x27;+&#x27; prefix) or without these tags (&#x27;-&#x27; prefix). See https://www.pantsbuild.org/2.29/docs/using-pants/advanced-target-selection.
 
 </Option>
 
@@ -348,7 +348,7 @@ build_file_prelude_globs = [
   default_repr={`[]`}
 >
 
-Python files to evaluate and whose symbols should be exposed to all BUILD files. See https://www.pantsbuild.org/2.28/docs/writing-plugins/macros.
+Python files to evaluate and whose symbols should be exposed to all BUILD files. See https://www.pantsbuild.org/2.29/docs/writing-plugins/macros.
 
 </Option>
 
@@ -408,7 +408,7 @@ Path to a file containing PEM-format CA certificates used for verifying secure c
 
 Even when using the `docker_environment` and `remote_environment` targets, this path will be read from the local host, and those certs will be used in the environment.
 
-This option cannot be overridden via environment targets, so if you need a different value than what the rest of your organization is using, override the value via an environment variable, CLI argument, or `.pants.rc` file. See https://www.pantsbuild.org/2.28/docs/using-pants/key-concepts/options.
+This option cannot be overridden via environment targets, so if you need a different value than what the rest of your organization is using, override the value via an environment variable, CLI argument, or `.pants.rc` file. See https://www.pantsbuild.org/2.29/docs/using-pants/key-concepts/options.
 
 </Option>
 
@@ -834,7 +834,7 @@ pants_version = <str>`}
 
 Use this Pants version. Note that Pants only uses this to verify that you are using the requested version, as Pants cannot dynamically change the version it is using once the program is already running.
 
-If you use the `pants` script from https://www.pantsbuild.org/2.28/docs/getting-started/installing-pants, however, changing the value in your `pants.toml` will cause the new version to be installed and run automatically.
+If you use the `pants` script from https://www.pantsbuild.org/2.29/docs/getting-started/installing-pants, however, changing the value in your `pants.toml` will cause the new version to be installed and run automatically.
 
 Run `pants --version` to check what is being used.
 
@@ -1353,7 +1353,7 @@ An oauth token to use for gGRPC connections to `[GLOBAL].remote_execution_addres
 
 If specified, Pants will add a header in the format `authorization: Bearer <token>`. You can also manually add this header via `[GLOBAL].remote_execution_headers` and `[GLOBAL].remote_store_headers`, or use `[GLOBAL].remote_auth_plugin` to provide a plugin to dynamically set the relevant headers. Otherwise, no authorization will be performed.
 
-Recommendation: do not place a token directly in `pants.toml`, instead do one of: set the token via the environment variable (`PANTS_REMOTE_OAUTH_BEARER_TOKEN`), CLI option (`--remote-oauth-bearer-token`), or store the token in a file and set the option to `"@/path/to/token.txt"` to [read the value from that file](https://www.pantsbuild.org/2.28/docs/using-pants/key-concepts/options#reading-individual-option-values-from-files).
+Recommendation: do not place a token directly in `pants.toml`, instead do one of: set the token via the environment variable (`PANTS_REMOTE_OAUTH_BEARER_TOKEN`), CLI option (`--remote-oauth-bearer-token`), or store the token in a file and set the option to `"@/path/to/token.txt"` to [read the value from that file](https://www.pantsbuild.org/2.29/docs/using-pants/key-concepts/options#reading-individual-option-values-from-files).
 
 </Option>
 

docs/reference/goals/fix.mdx

@@ -19,16 +19,16 @@ This goal runs tools that make 'semantic' changes to source code, wher
 
 See also:
 
-- [The `fmt` goal](https://www.pantsbuild.org/2.28/reference/goals/fix will run code-editing tools that may make only
+- [The `fmt` goal](https://www.pantsbuild.org/2.29/reference/goals/fix will run code-editing tools that may make only
   syntactic changes, not semantic ones. The `fix` includes running these `fmt` tools by
   default (see [the `skip_formatters` option](#skip_formatters) to control this).
 
-- [The `lint` goal](https://www.pantsbuild.org/2.28/reference/goals/lint) will validate code is formatted, by running these
+- [The `lint` goal](https://www.pantsbuild.org/2.29/reference/goals/lint) will validate code is formatted, by running these
   fixers and checking there's no change.
 
 - Documentation about formatters for various ecosystems, such as:
-  [Python](https://www.pantsbuild.org/2.28/docs/python/overview/linters-and-formatters), [JVM](https://www.pantsbuild.org/jvm/java-and-scala#lint-and-format),
-  [SQL](https://www.pantsbuild.org/2.28/docs/sql#enable-sqlfluff-linter)
+  [Python](https://www.pantsbuild.org/2.29/docs/python/overview/linters-and-formatters), [JVM](https://www.pantsbuild.org/jvm/java-and-scala#lint-and-format),
+  [SQL](https://www.pantsbuild.org/2.29/docs/sql#enable-sqlfluff-linter)
 
 Backend: <span className="color--primary">`pants.core`</span>
 

docs/reference/goals/fmt.mdx

@@ -19,15 +19,15 @@ This goal runs tools that make 'syntactic' changes to source code, whe
 
 See also:
 
-- [The `fix` goal](https://www.pantsbuild.org/2.28/reference/goals/fix) will run code-editing tools that may make semantic
+- [The `fix` goal](https://www.pantsbuild.org/2.29/reference/goals/fix) will run code-editing tools that may make semantic
   changes, not just syntactic ones.
 
-- [The `lint` goal](https://www.pantsbuild.org/2.28/reference/goals/lint) will validate code is formatted, by running these
+- [The `lint` goal](https://www.pantsbuild.org/2.29/reference/goals/lint) will validate code is formatted, by running these
   formatters and checking there's no change.
 
 - Documentation about formatters for various ecosystems, such as:
-  [Python](https://www.pantsbuild.org/2.28/docs/python/overview/linters-and-formatters), [Go](https://www.pantsbuild.org/2.28/docs/go#gofmt),
-  [JVM](https://www.pantsbuild.org/jvm/java-and-scala#lint-and-format), [Shell](https://www.pantsbuild.org/2.28/docs/shell#shfmt-autoformatter).
+  [Python](https://www.pantsbuild.org/2.29/docs/python/overview/linters-and-formatters), [Go](https://www.pantsbuild.org/2.29/docs/go#gofmt),
+  [JVM](https://www.pantsbuild.org/jvm/java-and-scala#lint-and-format), [Shell](https://www.pantsbuild.org/2.29/docs/shell#shfmt-autoformatter).
 
 Backend: <span className="color--primary">`pants.core`</span>
 

docs/reference/goals/lint.mdx

@@ -19,16 +19,16 @@ This goal runs tools that check code quality/styling etc, without changing that
 
 See also:
 
-- [The `fmt` goal](https://www.pantsbuild.org/2.28/reference/goals/fix will save the the result of formatters
+- [The `fmt` goal](https://www.pantsbuild.org/2.29/reference/goals/fix will save the the result of formatters
   (code-editing tools that make only "syntactic" changes) back to the workspace.
 
-- [The `fmt` goal](https://www.pantsbuild.org/2.28/reference/goals/fix will save the the result of fixers
+- [The `fmt` goal](https://www.pantsbuild.org/2.29/reference/goals/fix will save the the result of fixers
   (code-editing tools that may make "semantic" changes too) back to the workspace.
 
 - Documentation about linters for various ecosystems, such as:
-  [Python](https://www.pantsbuild.org/2.28/docs/python/overview/linters-and-formatters), [Go](https://www.pantsbuild.org/2.28/docs/go),
-  [JVM](https://www.pantsbuild.org/jvm/java-and-scala#lint-and-format), [Shell](https://www.pantsbuild.org/2.28/docs/shell),
-  [Docker](https://www.pantsbuild.org/2.28/docs/docker#linting-dockerfiles-with-hadolint).
+  [Python](https://www.pantsbuild.org/2.29/docs/python/overview/linters-and-formatters), [Go](https://www.pantsbuild.org/2.29/docs/go),
+  [JVM](https://www.pantsbuild.org/jvm/java-and-scala#lint-and-format), [Shell](https://www.pantsbuild.org/2.29/docs/shell),
+  [Docker](https://www.pantsbuild.org/2.29/docs/docker#linting-dockerfiles-with-hadolint).
 
 Backend: <span className="color--primary">`pants.core`</span>
 

docs/reference/goals/tailor.mdx

@@ -53,7 +53,7 @@ key2 = val2
   default_repr={`{}`}
 >
 
-A mapping from standard target type to custom type to use instead. The custom type can be a custom target type or a macro that offers compatible functionality to the one it replaces (see https://www.pantsbuild.org/2.28/docs/writing-plugins/macros).
+A mapping from standard target type to custom type to use instead. The custom type can be a custom target type or a macro that offers compatible functionality to the one it replaces (see https://www.pantsbuild.org/2.29/docs/writing-plugins/macros).
 
 </Option>