v3.43.3

Author: pd93

CHANGELOG.md

@@ -1,6 +1,6 @@
 # Changelog
 
-## Unreleased
+## v3.43.3 - 2025-04-27
 
 Reverted the changes made in #2113 and #2186 that affected the
 `USER_WORKING_DIR` and built-in variables. This fixes #2206, #2195, #2207 and

internal/version/version.txt

@@ -1 +1 @@
-3.43.2
+3.43.3

package-lock.json

@@ -1,6 +1,6 @@
 {
   "name": "@go-task/cli",
-  "version": "3.43.2",
+  "version": "3.43.3",
   "description": "A task runner / simpler Make alternative written in Go",
   "scripts": {
     "postinstall": "go-npm install",

package.json

@@ -5,6 +5,12 @@ sidebar_position: 14
 
 # Changelog
 
+## v3.43.3 - 2025-04-27
+
+Reverted the changes made in #2113 and #2186 that affected the
+`USER_WORKING_DIR` and built-in variables. This fixes #2206, #2195, #2207 and
+#2208.
+
 ## v3.43.2 - 2025-04-21
 
 - Fixed regresion of `CLI_ARGS` being exposed as the wrong type (#2190, #2191 by

website/docs/changelog.mdx

@@ -5,6 +5,12 @@ sidebar_position: 14
 
 # Changelog
 
+## v3.43.3 - 2025-04-27
+
+Reverted the changes made in #2113 and #2186 that affected the
+`USER_WORKING_DIR` and built-in variables. This fixes #2206, #2195, #2207 and
+#2208.
+
 ## v3.43.2 - 2025-04-21
 
 - Fixed regresion of `CLI_ARGS` being exposed as the wrong type (#2190, #2191 by

website/versioned_docs/version-latest/changelog.mdx

@@ -43,12 +43,16 @@ Studio Code][vscode-task].
 ## 2. Making changes
 
 - **Code style** - Try to maintain the existing code style where possible. Go
-  code should be formatted by [`gofumpt`][gofumpt] and linted using
-  [`golangci-lint`][golangci-lint]. Any Markdown or TypeScript files should be
-  formatted and linted by [Prettier][prettier]. This style is enforced by our CI
-  to ensure that we have a consistent style across the project. You can use the
-  `task lint` command to lint the code locally and the `task lint:fix` command
-  to automatically fix any issues that are found.
+  code should be formatted and linted by [`golangci-lint`][golangci-lint]. This
+  wraps the [`gofumpt`][gofumpt] and [`gci`][gci] formatters and a number of
+  linters. We recommend that you take a look at the [golangci-lint
+  docs][golangci-lint-docs] for a guide on how to setup your editor to
+  auto-format your code. Any Markdown or TypeScript files should be formatted
+  and linted by [Prettier][prettier]. This style is enforced by our CI to ensure
+  that we have a consistent style across the project. You can use the `task
+  lint` command to lint the code locally and the `task lint:fix` command to try
+  to automatically fix any issues that are found. You can also use the `task
+  fmt` command to auto-format the files if your editor doesn't do it for you.
 - **Documentation** - Ensure that you add/update any relevant documentation. See
   the [updating documentation](#updating-documentation) section below.
 - **Tests** - Ensure that you add/update any relevant tests and that all tests
@@ -73,8 +77,9 @@ install the extension.
 Task uses [Docusaurus][docusaurus] to host a documentation server. The code for
 this is located in the core Task repository. This can be setup and run locally
 by using `task website` (requires `nodejs` & `yarn`). All content is written in
-Markdown and is located in the `website/docs` directory. All Markdown documents
-should have an 80 character line wrap limit (enforced by Prettier).
+[MDX][mdx] (an extension of Markdown) and is located in the `website/docs`
+directory. All Markdown documents should have an 80 character line wrap limit
+(enforced by Prettier).
 
 When making a change, consider whether a change to the [Usage Guide](/usage) is
 necessary. This document contains descriptions and examples of how to use Task
@@ -154,7 +159,9 @@ If you have questions, feel free to ask them in the `#help` forum channel on our
 [vscode-task]: https://github.com/go-task/vscode-task
 [go]: https://go.dev
 [gofumpt]: https://github.com/mvdan/gofumpt
+[gci]: https://github.com/daixiang0/gci
 [golangci-lint]: https://golangci-lint.run
+[golangci-lint-docs]: https://golangci-lint.run/welcome/integrations/
 [prettier]: https://prettier.io
 [nodejs]: https://nodejs.org/en/
 [yarn]: https://yarnpkg.com/
@@ -166,4 +173,5 @@ If you have questions, feel free to ask them in the `#help` forum channel on our
 [discord-server]: https://discord.gg/6TY36E39UK
 [discussion]: https://github.com/go-task/task/discussions
 [conventional-commits]: https://www.conventionalcommits.org
+[mdx]: https://mdxjs.com/
 {/* prettier-ignore-end */}

website/versioned_docs/version-latest/contributing.mdx

@@ -115,7 +115,7 @@ special variable will be overridden.
 | `TASKFILE`         | The absolute path of the included Taskfile.                                                                                                              |
 | `TASKFILE_DIR`     | The absolute path of the included Taskfile directory.                                                                                                    |
 | `TASK_DIR`         | The absolute path of the directory where the task is executed.                                                                                           |
-| `USER_WORKING_DIR` | The absolute path of the directory `task` was called from, or the value of `--dir` (`-d`) if given.                                                      |
+| `USER_WORKING_DIR` | The absolute path of the directory `task` was called from.                                                                                               |
 | `CHECKSUM`         | The checksum of the files listed in `sources`. Only available within the `status` prop and if method is set to `checksum`.                               |
 | `TIMESTAMP`        | The date object of the greatest timestamp of the files listed in `sources`. Only available within the `status` prop and if method is set to `timestamp`. |
 | `TASK_VERSION`     | The current version of task.                                                                                                                             |

website/versioned_docs/version-latest/reference/templating.mdx

@@ -61,12 +61,6 @@ In this example, we can run `cd <service>` and `task up` and as long as the
 `<service>` directory contains a `docker-compose.yml`, the Docker composition
 will be brought up.
 
-:::info
-
-`.USER_WORKING_DIR` will contain the value of the `--dir` (`-d`) flag, if given.
-
-:::
-
 ### Running a global Taskfile
 
 If you call Task with the `--global` (alias `-g`) flag, it will look for your
@@ -1122,14 +1116,14 @@ tasks:
       MAP:
         map: {A: 1, B: 2, C: 3}
     cmds:
-      - 'echo {{.STRING}}'  # Hello, World!
-      - 'echo {{.BOOL}}'    # true
-      - 'echo {{.INT}}'     # 42
-      - 'echo {{.FLOAT}}'   # 3.14
-      - 'echo {{.ARRAY}}'   # [1 2 3]
-      - 'echo {{.ARRAY.0}}' # 1
-      - 'echo {{.MAP}}'     # map[A:1 B:2 C:3]
-      - 'echo {{.MAP.A}}'   # 1
+      - 'echo {{.STRING}}'        # Hello, World!
+      - 'echo {{.BOOL}}'          # true
+      - 'echo {{.INT}}'           # 42
+      - 'echo {{.FLOAT}}'         # 3.14
+      - 'echo {{.ARRAY}}'         # [1 2 3]
+      - 'echo {{index .ARRAY 0}}' # 1
+      - 'echo {{.MAP}}'           # map[A:1 B:2 C:3]
+      - 'echo {{.MAP.A}}'         # 1
 ```
 
 Variables can be set in many places in a Taskfile. When executing