v3.35.1

* fix: taskfile directory

* tests: add tests for special vars when running from a subdirectory

.github/ISSUE_TEMPLATE/config.yml

@@ -4,7 +4,7 @@ contact_links:
     url: https://github.com/go-task/vscode-task
     about: Issues related to the Visual Studio Code extension should be opened here.
   - name: Help forum on Discord
-    url: https://discord.com/channels/974121106208354339/1025054680289660989
+    url: https://discord.gg/6TY36E39UK
     about: 'The Discord #help channel is the best way to get help from the community.'
   - name: Questions, Ideas and General Discussions
     url: https://github.com/go-task/task/discussions

.github/workflows/issue-experiment.yml

@@ -17,7 +17,7 @@ jobs:
               issue_number: context.issue.number,
               owner: context.repo.owner,
               repo: context.repo.repo,
-              body: 'This issue has been marked as an experiment proposal! :test_tube: It will now enter a period of consultation during which we encourage the community to provide feedback on the proposed design. Please see the [experiment workflow documentation](https://taskfile.dev/experiments/workflow) for more information on how we release experiments.'
+              body: 'This issue has been marked as an experiment proposal! :test_tube: It will now enter a period of consultation during which we encourage the community to provide feedback on the proposed design. Please see the [experiment workflow documentation](https://taskfile.dev/experiments#workflow) for more information on how we release experiments.'
             })
   issue-experiment-draft:
     if: github.event.label.name == format('experiment{0} draft', ':')
@@ -31,7 +31,7 @@ jobs:
               issue_number: context.issue.number,
               owner: context.repo.owner,
               repo: context.repo.repo,
-              body: 'This experiment has been marked as a draft! :sparkles: This means that an initial implementation has been added to the latest release of Task! You can find information about this experiment and how to enable it in our [experiments documentation](https://taskfile.dev/experiments). Please see the [experiment workflow documentation](https://taskfile.dev/experiments/workflow) for more information on how we release experiments.'
+              body: 'This experiment has been marked as a draft! :sparkles: This means that an initial implementation has been added to the latest release of Task! You can find information about this experiment and how to enable it in our [experiments documentation](https://taskfile.dev/experiments). Please see the [experiment workflow documentation](https://taskfile.dev/experiments#workflow) for more information on how we release experiments.'
             })
   issue-experiment-candidate:
     if: github.event.label.name == format('experiment{0} candidate', ':')
@@ -45,7 +45,7 @@ jobs:
               issue_number: context.issue.number,
               owner: context.repo.owner,
               repo: context.repo.repo,
-              body: 'This experiment has been marked as a candidate! :fire: This means that the  implementation is nearing completion and we are entering a period for final comments and feedback! You can find information about this experiment and how to enable it in our [experiments documentation](https://taskfile.dev/experiments). Please see the [experiment workflow documentation](https://taskfile.dev/experiments/workflow) for more information on how we release experiments.'
+              body: 'This experiment has been marked as a candidate! :fire: This means that the  implementation is nearing completion and we are entering a period for final comments and feedback! You can find information about this experiment and how to enable it in our [experiments documentation](https://taskfile.dev/experiments). Please see the [experiment workflow documentation](https://taskfile.dev/experiments#workflow) for more information on how we release experiments.'
             })
   issue-experiment-stable:
     if: github.event.label.name == format('experiment{0} stable', ':')
@@ -59,7 +59,7 @@ jobs:
               issue_number: context.issue.number,
               owner: context.repo.owner,
               repo: context.repo.repo,
-              body: 'This experiment has been marked as stable! :metal: This means that the  implementation is now final and ready to be released. No more changes will be made and the experiment is safe to use in production! You can find information about this experiment and how to enable it in our [experiments documentation](https://taskfile.dev/experiments). Please see the [experiment workflow documentation](https://taskfile.dev/experiments/workflow) for more information on how we release experiments.'
+              body: 'This experiment has been marked as stable! :metal: This means that the  implementation is now final and ready to be released. No more changes will be made and the experiment is safe to use in production! You can find information about this experiment and how to enable it in our [experiments documentation](https://taskfile.dev/experiments). Please see the [experiment workflow documentation](https://taskfile.dev/experiments#workflow) for more information on how we release experiments.'
             })
   issue-experiment-released:
     if: github.event.label.name == format('experiment{0} released', ':')
@@ -73,7 +73,7 @@ jobs:
               issue_number: context.issue.number,
               owner: context.repo.owner,
               repo: context.repo.repo,
-              body: 'This experiment has been released! :rocket: This means that it is no longer an experiment and is available in the latest major version of Task. Please see the [experiment workflow documentation](https://taskfile.dev/experiments/workflow) for more information on how we release experiments.'
+              body: 'This experiment has been released! :rocket: This means that it is no longer an experiment and is available in the latest major version of Task. Please see the [experiment workflow documentation](https://taskfile.dev/experiments#workflow) for more information on how we release experiments.'
             })
             github.rest.issues.update({
               issue_number: context.issue.number,
@@ -93,7 +93,7 @@ jobs:
               issue_number: context.issue.number,
               owner: context.repo.owner,
               repo: context.repo.repo,
-              body: 'This experiment has been abandoned. :disappointed: This means that this feature will not be added to Task and any experimental functionality will be removed. Please see the [experiment workflow documentation](https://taskfile.dev/experiments/workflow) for more information on how we release experiments.'
+              body: 'This experiment has been abandoned. :disappointed: This means that this feature will not be added to Task and any experimental functionality will be removed. Please see the [experiment workflow documentation](https://taskfile.dev/experiments#workflow) for more information on how we release experiments.'
             })
             github.rest.issues.update({
               issue_number: context.issue.number,
@@ -113,7 +113,7 @@ jobs:
               issue_number: context.issue.number,
               owner: context.repo.owner,
               repo: context.repo.repo,
-              body: 'This experiment has been superseded. :seedling: This means that another experiment has replaced this one. Please see the [experiment workflow documentation](https://taskfile.dev/experiments/workflow) for more information on how we release experiments.'
+              body: 'This experiment has been superseded. :seedling: This means that another experiment has replaced this one. Please see the [experiment workflow documentation](https://taskfile.dev/experiments#workflow) for more information on how we release experiments.'
             })
             github.rest.issues.update({
               issue_number: context.issue.number,

.github/workflows/lint.yml

@@ -10,15 +10,34 @@ on:
 
 jobs:
   lint:
+    name: Lint
+    strategy:
+      matrix:
+        go-version: [1.21.x, 1.22.x]
     runs-on: ubuntu-latest
     steps:
       - uses: actions/setup-go@v3
         with:
-          go-version: 1.20.x
+          go-version: ${{matrix.go-version}}
 
       - uses: actions/checkout@v3
 
       - name: golangci-lint
         uses: golangci/golangci-lint-action@v3
         with:
-          version: v1.51.1
+          version: v1.55.2
+
+  lint-jsonschema:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/setup-python@v5
+        with:
+          python-version: 3.12
+
+      - uses: actions/checkout@v3
+
+      - name: install check-jsonschema
+        run: python -m pip install 'check-jsonschema==0.27.3'
+
+      - name: check-jsonschema (metaschema)
+        run: check-jsonschema --check-metaschema docs/static/schema.json

.github/workflows/release.yml

@@ -3,7 +3,7 @@ name: goreleaser
 on:
   push:
     tags:
-      - '*'
+      - 'v*'
 
 jobs:
   goreleaser:
@@ -15,12 +15,12 @@ jobs:
       - name: Set up Go
         uses: actions/setup-go@v3
         with:
-          go-version: 1.20.x
+          go-version: 1.21.x
 
       - name: Run GoReleaser
         uses: goreleaser/goreleaser-action@v2
         with:
           version: latest
-          args: release --rm-dist
+          args: release --clean
         env:
           GITHUB_TOKEN: ${{secrets.GH_PAT}}

.github/workflows/test.yml

@@ -13,7 +13,7 @@ jobs:
     name: Test
     strategy:
       matrix:
-        go-version: [1.19.x, 1.20.x]
+        go-version: [1.21.x, 1.22.x]
         platform: [ubuntu-latest, macos-latest, windows-latest]
     runs-on: ${{matrix.platform}}
     steps:

.github/workflows/upload-source-documents.yml

@@ -16,7 +16,7 @@ jobs:
 
       - name: Verify changed files
         id: changed-files
-        uses: tj-actions/changed-files@v35
+        uses: tj-actions/changed-files@v41
         with:
           files: |
             docs/docs

.gitignore

@@ -21,7 +21,8 @@ dist/
 
 # editors
 .idea/
-.vscode/
+.vscode/*
+!.vscode/*-sample.json
 .fleet/
 
 # exuberant ctags

.goreleaser.yml

@@ -1,28 +1,28 @@
-build:
-  binary: task
-  main: ./cmd/task
-  goos:
-    - windows
-    - darwin
-    - linux
-    - freebsd
-  goarch:
-    - '386'
-    - amd64
-    - arm
-    - arm64
-  goarm:
-    - '6'
-  ignore:
-    - goos: darwin
-      goarch: '386'
-  env:
-    - CGO_ENABLED=0
-  mod_timestamp: '{{ .CommitTimestamp }}'
-  flags:
-    - -trimpath
-  ldflags:
-    - -s -w # Don't set main.version.
+builds:
+  - binary: task
+    main: ./cmd/task
+    goos:
+      - windows
+      - darwin
+      - linux
+      - freebsd
+    goarch:
+      - '386'
+      - amd64
+      - arm
+      - arm64
+    goarm:
+      - '6'
+    ignore:
+      - goos: darwin
+        goarch: '386'
+    env:
+      - CGO_ENABLED=0
+    mod_timestamp: '{{ .CommitTimestamp }}'
+    flags:
+      - -trimpath
+    ldflags:
+      - -s -w # Don't set main.version.
 
 gomod:
   proxy: true
@@ -72,7 +72,7 @@ brews:
     license: MIT
     homepage: https://taskfile.dev
     folder: Formula
-    tap:
+    repository:
       owner: go-task
       name: homebrew-tap
     test:
@@ -85,3 +85,41 @@ brews:
     commit_author:
       name: task-bot
       email: 106601941+task-bot@users.noreply.github.com
+
+winget:
+  - name: Task
+    publisher: Task
+    short_description: A task runner / simpler Make alternative written in Go
+    description: Task is a task runner / build tool that aims to be simpler and easier to use than, for example, GNU Make.
+    license: MIT
+    homepage: https://taskfile.dev/
+    publisher_url: https://taskfile.dev/
+    publisher_support_url: https://github.com/go-task/task/issues
+    package_identifier: Task.Task
+    commit_author:
+      name: task-bot
+      email: 106601941+task-bot@users.noreply.github.com
+    commit_msg_template: "chore: bump {{.PackageIdentifier}} to {{.Tag}}"
+    release_notes_url: https://github.com/go-task/task/releases/tag/{{.Tag}}
+    tags:
+      - build
+      - build-tool
+      - devops
+      - go
+      - make
+      - makefile
+      - runner
+      - task
+      - task-runner
+      - taskfile
+      - tool
+    skip_upload: true
+    repository:
+      owner: microsoft
+      name: winget-pkgs
+      pull_request:
+        enabled: true
+        base:
+          owner: go-task
+          name: winget-pkgs
+          branch: "bump-task-to-{{.Tag}}"

.prettierignore

@@ -1 +0,0 @@
-docs/docs/changelog.md

.vscode/settings-sample.json

@@ -0,0 +1,5 @@
+{
+  "yaml.schemas": {
+    "./docs/static/schema.json": "Taskfile.yml"
+  }
+}

CHANGELOG.md

@@ -1,5 +1,151 @@
 # Changelog
 
+## v3.35.1 - 2024-03-04
+
+- Fixed a bug where the `TASKFILE_DIR` variable was sometimes incorrect (#1522,
+  #1523 by @pd93).
+- Added a new `TASKFILE` special variable that holds the root Taskfile path
+  (#1523 by @pd93).
+- Fixed various issues related to running a Taskfile from a subdirectory (#1529,
+  #1530 by @pd93).
+
+## v3.35.0 - 2024-02-28
+
+- Added support for
+  [wildcards in task names](https://taskfile.dev/usage/#wildcard-arguments)
+  (#836, #1489 by @pd93).
+- Added the ability to
+  [run Taskfiles via stdin](https://taskfile.dev/usage/#reading-a-taskfile-from-stdin)
+  (#655, #1483 by @pd93).
+- Bumped minimum Go version to 1.21 (#1500 by @pd93).
+- Fixed bug related to the `--list` flag (#1509, #1512 by @pd93, #1514, #1520 by
+  @pd93).
+- Add mention on the documentation to the fact that the variable declaration
+  order is respected (#1510 by @kirkrodrigues).
+- Improved style guide docs (#1495 by @iwittkau).
+- Removed duplicated entry for `requires` on the API docs (#1491 by
+  @teatimeguest).
+
+## v3.34.1 - 2024-01-27
+
+- Fixed prompt regression on
+  [Remote Taskfiles experiment](https://taskfile.dev/experiments/remote-taskfiles/)
+  (#1486, #1487 by @pd93).
+
+## v3.34.0 - 2024-01-25
+
+- Removed support for `version: 2` schemas. See the
+  [deprecation notice on our website](https://taskfile.dev/deprecations/version-2-schema)
+  (#1197, #1447 by @pd93).
+- Fixed a couple of issues in the JSON Schema + added a CI step to ensure it's
+  correct (#1471, #1474, #1476 by @sirosen).
+- Added
+  [Any Variables experiment proposal 2](https://taskfile.dev/experiments/any-variables/?proposal=2)
+  (#1415, #1444 by @pd93).
+- Updated the experiments and deprecations documentation format (#1445 by
+  @pd93).
+- Added new template function: `spew`, which can be used to print variables for
+  debugging purposes (#1452 by @pd93).
+- Added new template function: `merge`, which can be used to merge any number of
+  map variables (#1438, #1464 by @pd93).
+- Small change on the API when using as a library: `call.Direct` became
+  `call.Indirect` (#1459 by @pd93).
+- Refactored the public `read` and `taskfile` packages and introduced
+  `taskfile/ast` (#1450 by @pd93).
+- `ast.IncludedTaskfiles` renamed to `ast.Includes` and `orderedmap` package
+  renamed to `omap` plus some internal refactor work (#1456 by @pd93).
+- Fix zsh completion script to allow lowercase `taskfile` file names (#1482 by
+  @xontab).
+- Improvements on how we check the Taskfile version (#1465 by @pd93).
+- Added a new `ROOT_TASKFILE` special variable (#1468, #1469 by @pd93).
+- Fix experiment flags in `.env` when the `--dir` or `--taskfile` flags were
+  used (#1478 by @pd93).
+
+## v3.33.1 - 2023-12-21
+
+- Added support for looping over map variables with the
+  [Any Variables experiment](https://taskfile.dev/experiments/any-variables)
+  enabled (#1435, #1437 by @pd93).
+- Fixed a bug where dynamic variables were causing errors during fast
+  compilation (#1435, #1437 by @pd93)
+
+## v3.33.0 - 2023-12-20
+
+- Added
+  [Any Variables experiment](https://taskfile.dev/experiments/any-variables)
+  (#1415, #1421 by @pd93).
+- Updated Docusaurus to v3 (#1432 by @pd93).
+- Added `aliases` to `--json` flag output (#1430, #1431 by @pd93).
+- Added new `CLI_FORCE` special variable containing whether the `--force` or
+  `--force-all` flags were set (#1412, #1434 by @pd93).
+
+## v3.32.0 - 2023-11-29
+
+- Added ability to exclude some files from `sources:` by using `exclude:` (#225,
+  #1324 by @pd93 and @andreynering).
+- The
+  [Remote Taskfiles experiment](https://taskfile.dev/experiments/remote-taskfiles)
+  now prefers remote files over cached ones by default (#1317, #1345 by @pd93).
+- Added `--timeout` flag to the
+  [Remote Taskfiles experiment](https://taskfile.dev/experiments/remote-taskfiles)
+  (#1317, #1345 by @pd93).
+- Fix bug where dynamic `vars:` and `env:` were being executed when they should
+  actually be skipped by `platforms:` (#1273, #1377 by @andreynering).
+- Fix `schema.json` to make `silent` valid in `cmds` that use `for` (#1385,
+  #1386 by @iainvm).
+- Add new `--no-status` flag to skip expensive status checks when running
+  `task --list --json` (#1348, #1368 by @amancevice).
+
+## v3.31.0 - 2023-10-07
+
+- Enabled the `--yes` flag for the
+  [Remote Taskfiles experiment](https://taskfile.dev/experiments/remote-taskfiles)
+  (#1317, #1344 by @pd93).
+- Add ability to set `watch: true` in a task to automatically run it in watch
+  mode (#231, #1361 by @andreynering).
+- Fixed a bug on the watch mode where paths that contained `.git` (like
+  `.github`), for example, were also being ignored (#1356 by @butuzov).
+- Fixed a nil pointer error when running a Taskfile with no contents (#1341,
+  #1342 by @pd93).
+- Added a new [exit code](https://taskfile.dev/api/#exit-codes) (107) for when a
+  Taskfile does not contain a schema version (#1342 by @pd93).
+- Increased limit of maximum task calls from 100 to 1000 for now, as some people
+  have been reaching this limit organically now that we have loops. This check
+  exists to detect recursive calls, but will be removed in favor of a better
+  algorithm soon (#1321, #1332).
+- Fixed templating on descriptions on `task --list` (#1343 by @blackjid).
+- Fixed a bug where precondition errors were incorrectly being printed when task
+  execution was aborted (#1337, #1338 by @sylv-io).
+
+## v3.30.1 - 2023-09-14
+
+- Fixed a regression where some special variables weren't being set correctly
+  (#1331, #1334 by @pd93).
+
+## v3.30.0 - 2023-09-13
+
+- Prep work for Remote Taskfiles (#1316 by @pd93).
+- Added the
+  [Remote Taskfiles experiment](https://taskfile.dev/experiments/remote-taskfiles)
+  as a draft (#1152, #1317 by @pd93).
+- Improve performance of content checksuming on `sources:` by replacing md5 with
+  [XXH3](https://xxhash.com/) which is much faster. This is a soft breaking
+  change because checksums will be invalidated when upgrading to this release
+  (#1325 by @ReillyBrogan).
+
+## v3.29.1 - 2023-08-26
+
+- Update to Go 1.21 (bump minimum version to 1.20) (#1302 by @pd93)
+- Fix a missing a line break on log when using `--watch` mode (#1285, #1297 by
+  @FilipSolich).
+- Fix `defer` on JSON Schema (#1288 by @calvinmclean and @andreynering).
+- Fix bug in usage of special variables like `{{.USER_WORKING_DIR}}` in
+  combination with `includes` (#1046, #1205, #1250, #1293, #1312, #1274 by
+  @andarto, #1309 by @andreynering).
+- Fix bug on `--status` flag. Running this flag should not have side-effects: it
+  should not update the checksum on `.task`, only report its status (#1305,
+  #1307 by @visciang, #1313 by @andreynering).
+
 ## v3.28.0 - 2023-07-24
 
 - Added the ability to
@@ -25,7 +171,8 @@
 - Bug fixes were made to the
   [npm installation method](https://taskfile.dev/installation/#npm). (#1190, by
   @sounisi5011).
-- Added the [gentle force experiment](https://taskfile.dev/experiments) as a
+- Added the
+  [gentle force experiment](https://taskfile.dev/experiments/gentle-force) as a
   draft (#1200, #1216 by @pd93).
 - Added an `--experiments` flag to allow you to see which experiments are
   enabled (#1242 by @pd93).
@@ -454,8 +601,8 @@ it a go and let us know what you think via a
 
 - On `v3`, all CLI variables will be considered global variables (#336, #341)
 - Add support to `.env` like files (#324, #356).
-- Add `label:` to task so you can override the task name in the logs
-  ([#321](https://github.com/go-task/task/issues/321]), #337).
+- Add `label:` to task so you can override the task name in the logs (#321,
+  #337).
 - Refactor how variables work on version 3 (#311).
 - Disallow `expansions` on v3 since it has no effect.
 - `Taskvars.yml` is not automatically included anymore.

README.md

@@ -13,17 +13,3 @@
     <a href="https://taskfile.dev/installation/">Installation</a> | <a href="https://taskfile.dev/usage/">Documentation</a> | <a href="https://twitter.com/taskfiledev">Twitter</a> | <a href="https://fosstodon.org/@task">Mastodon</a> | <a href="https://discord.gg/6TY36E39UK">Discord</a>
   </p>
 </div>
-
-## Gold Sponsors
-
-<div align="center">
-
-| [Appwrite][appwrite]                                   |
-| ------------------------------------------------------ |
-| [![Appwrite](/docs/static/img/appwrite.svg)][appwrite] |
-
-</div>
-
-<!-- prettier-ignore-start -->
-[appwrite]: https://appwrite.io/?utm_source=task_github&utm_medium=social&utm_campaign=task_oss_fund
-<!-- prettier-ignore-end -->

Taskfile.yml

@@ -113,10 +113,15 @@ tasks:
       GO_PACKAGES:
         sh: go list ./...
 
-  test-release:
+  goreleaser:test:
     desc: Tests release process without publishing
     cmds:
-      - goreleaser --snapshot --rm-dist
+      - goreleaser --snapshot --clean
+
+  goreleaser:install:
+    desc: Installs goreleaser
+    cmds:
+      - go install github.com/goreleaser/goreleaser@latest
 
   release:
     desc: Prepare the project for a new release

args/args.go

@@ -3,56 +3,22 @@ package args
 import (
 	"strings"
 
-	"github.com/go-task/task/v3/taskfile"
+	"github.com/go-task/task/v3/taskfile/ast"
 )
 
-// ParseV3 parses command line argument: tasks and global variables
-func ParseV3(args ...string) ([]taskfile.Call, *taskfile.Vars) {
-	var calls []taskfile.Call
-	globals := &taskfile.Vars{}
+// Parse parses command line argument: tasks and global variables
+func Parse(args ...string) ([]*ast.Call, *ast.Vars) {
+	calls := []*ast.Call{}
+	globals := &ast.Vars{}
 
 	for _, arg := range args {
 		if !strings.Contains(arg, "=") {
-			calls = append(calls, taskfile.Call{Task: arg, Direct: true})
+			calls = append(calls, &ast.Call{Task: arg})
 			continue
 		}
 
 		name, value := splitVar(arg)
-		globals.Set(name, taskfile.Var{Static: value})
-	}
-
-	if len(calls) == 0 {
-		calls = append(calls, taskfile.Call{Task: "default", Direct: true})
-	}
-
-	return calls, globals
-}
-
-// ParseV2 parses command line argument: tasks and vars of each task
-func ParseV2(args ...string) ([]taskfile.Call, *taskfile.Vars) {
-	var calls []taskfile.Call
-	globals := &taskfile.Vars{}
-
-	for _, arg := range args {
-		if !strings.Contains(arg, "=") {
-			calls = append(calls, taskfile.Call{Task: arg, Direct: true})
-			continue
-		}
-
-		if len(calls) < 1 {
-			name, value := splitVar(arg)
-			globals.Set(name, taskfile.Var{Static: value})
-		} else {
-			if calls[len(calls)-1].Vars == nil {
-				calls[len(calls)-1].Vars = &taskfile.Vars{}
-			}
-			name, value := splitVar(arg)
-			calls[len(calls)-1].Vars.Set(name, taskfile.Var{Static: value})
-		}
-	}
-
-	if len(calls) == 0 {
-		calls = append(calls, taskfile.Call{Task: "default", Direct: true})
+		globals.Set(name, ast.Var{Value: value})
 	}
 
 	return calls, globals

args/args_test.go

@@ -7,37 +7,37 @@ import (
 	"github.com/stretchr/testify/assert"
 
 	"github.com/go-task/task/v3/args"
-	"github.com/go-task/task/v3/internal/orderedmap"
-	"github.com/go-task/task/v3/taskfile"
+	"github.com/go-task/task/v3/internal/omap"
+	"github.com/go-task/task/v3/taskfile/ast"
 )
 
-func TestArgsV3(t *testing.T) {
+func TestArgs(t *testing.T) {
 	tests := []struct {
 		Args            []string
-		ExpectedCalls   []taskfile.Call
-		ExpectedGlobals *taskfile.Vars
+		ExpectedCalls   []*ast.Call
+		ExpectedGlobals *ast.Vars
 	}{
 		{
 			Args: []string{"task-a", "task-b", "task-c"},
-			ExpectedCalls: []taskfile.Call{
-				{Task: "task-a", Direct: true},
-				{Task: "task-b", Direct: true},
-				{Task: "task-c", Direct: true},
+			ExpectedCalls: []*ast.Call{
+				{Task: "task-a"},
+				{Task: "task-b"},
+				{Task: "task-c"},
 			},
 		},
 		{
 			Args: []string{"task-a", "FOO=bar", "task-b", "task-c", "BAR=baz", "BAZ=foo"},
-			ExpectedCalls: []taskfile.Call{
-				{Task: "task-a", Direct: true},
-				{Task: "task-b", Direct: true},
-				{Task: "task-c", Direct: true},
+			ExpectedCalls: []*ast.Call{
+				{Task: "task-a"},
+				{Task: "task-b"},
+				{Task: "task-c"},
 			},
-			ExpectedGlobals: &taskfile.Vars{
-				OrderedMap: orderedmap.FromMapWithOrder(
-					map[string]taskfile.Var{
-						"FOO": {Static: "bar"},
-						"BAR": {Static: "baz"},
-						"BAZ": {Static: "foo"},
+			ExpectedGlobals: &ast.Vars{
+				OrderedMap: omap.FromMapWithOrder(
+					map[string]ast.Var{
+						"FOO": {Value: "bar"},
+						"BAR": {Value: "baz"},
+						"BAZ": {Value: "foo"},
 					},
 					[]string{"FOO", "BAR", "BAZ"},
 				),
@@ -45,13 +45,13 @@ func TestArgsV3(t *testing.T) {
 		},
 		{
 			Args: []string{"task-a", "CONTENT=with some spaces"},
-			ExpectedCalls: []taskfile.Call{
-				{Task: "task-a", Direct: true},
+			ExpectedCalls: []*ast.Call{
+				{Task: "task-a"},
 			},
-			ExpectedGlobals: &taskfile.Vars{
-				OrderedMap: orderedmap.FromMapWithOrder(
-					map[string]taskfile.Var{
-						"CONTENT": {Static: "with some spaces"},
+			ExpectedGlobals: &ast.Vars{
+				OrderedMap: omap.FromMapWithOrder(
+					map[string]ast.Var{
+						"CONTENT": {Value: "with some spaces"},
 					},
 					[]string{"CONTENT"},
 				),
@@ -59,41 +59,35 @@ func TestArgsV3(t *testing.T) {
 		},
 		{
 			Args: []string{"FOO=bar", "task-a", "task-b"},
-			ExpectedCalls: []taskfile.Call{
-				{Task: "task-a", Direct: true},
-				{Task: "task-b", Direct: true},
+			ExpectedCalls: []*ast.Call{
+				{Task: "task-a"},
+				{Task: "task-b"},
 			},
-			ExpectedGlobals: &taskfile.Vars{
-				OrderedMap: orderedmap.FromMapWithOrder(
-					map[string]taskfile.Var{
-						"FOO": {Static: "bar"},
+			ExpectedGlobals: &ast.Vars{
+				OrderedMap: omap.FromMapWithOrder(
+					map[string]ast.Var{
+						"FOO": {Value: "bar"},
 					},
 					[]string{"FOO"},
 				),
 			},
 		},
 		{
-			Args: nil,
-			ExpectedCalls: []taskfile.Call{
-				{Task: "default", Direct: true},
-			},
+			Args:          nil,
+			ExpectedCalls: []*ast.Call{},
 		},
 		{
-			Args: []string{},
-			ExpectedCalls: []taskfile.Call{
-				{Task: "default", Direct: true},
-			},
+			Args:          []string{},
+			ExpectedCalls: []*ast.Call{},
 		},
 		{
-			Args: []string{"FOO=bar", "BAR=baz"},
-			ExpectedCalls: []taskfile.Call{
-				{Task: "default", Direct: true},
-			},
-			ExpectedGlobals: &taskfile.Vars{
-				OrderedMap: orderedmap.FromMapWithOrder(
-					map[string]taskfile.Var{
-						"FOO": {Static: "bar"},
-						"BAR": {Static: "baz"},
+			Args:          []string{"FOO=bar", "BAR=baz"},
+			ExpectedCalls: []*ast.Call{},
+			ExpectedGlobals: &ast.Vars{
+				OrderedMap: omap.FromMapWithOrder(
+					map[string]ast.Var{
+						"FOO": {Value: "bar"},
+						"BAR": {Value: "baz"},
 					},
 					[]string{"FOO", "BAR"},
 				),
@@ -103,7 +97,7 @@ func TestArgsV3(t *testing.T) {
 
 	for i, test := range tests {
 		t.Run(fmt.Sprintf("TestArgs%d", i+1), func(t *testing.T) {
-			calls, globals := args.ParseV3(test.Args...)
+			calls, globals := args.Parse(test.Args...)
 			assert.Equal(t, test.ExpectedCalls, calls)
 			if test.ExpectedGlobals.Len() > 0 || globals.Len() > 0 {
 				assert.Equal(t, test.ExpectedGlobals.Keys(), globals.Keys())
@@ -112,120 +106,3 @@ func TestArgsV3(t *testing.T) {
 		})
 	}
 }
-
-func TestArgsV2(t *testing.T) {
-	tests := []struct {
-		Args            []string
-		ExpectedCalls   []taskfile.Call
-		ExpectedGlobals *taskfile.Vars
-	}{
-		{
-			Args: []string{"task-a", "task-b", "task-c"},
-			ExpectedCalls: []taskfile.Call{
-				{Task: "task-a", Direct: true},
-				{Task: "task-b", Direct: true},
-				{Task: "task-c", Direct: true},
-			},
-		},
-		{
-			Args: []string{"task-a", "FOO=bar", "task-b", "task-c", "BAR=baz", "BAZ=foo"},
-			ExpectedCalls: []taskfile.Call{
-				{
-					Task:   "task-a",
-					Direct: true,
-					Vars: &taskfile.Vars{
-						OrderedMap: orderedmap.FromMapWithOrder(
-							map[string]taskfile.Var{
-								"FOO": {Static: "bar"},
-							},
-							[]string{"FOO"},
-						),
-					},
-				},
-				{Task: "task-b", Direct: true},
-				{
-					Task:   "task-c",
-					Direct: true,
-					Vars: &taskfile.Vars{
-						OrderedMap: orderedmap.FromMapWithOrder(
-							map[string]taskfile.Var{
-								"BAR": {Static: "baz"},
-								"BAZ": {Static: "foo"},
-							},
-							[]string{"BAR", "BAZ"},
-						),
-					},
-				},
-			},
-		},
-		{
-			Args: []string{"task-a", "CONTENT=with some spaces"},
-			ExpectedCalls: []taskfile.Call{
-				{
-					Task:   "task-a",
-					Direct: true,
-					Vars: &taskfile.Vars{
-						OrderedMap: orderedmap.FromMapWithOrder(
-							map[string]taskfile.Var{
-								"CONTENT": {Static: "with some spaces"},
-							},
-							[]string{"CONTENT"},
-						),
-					},
-				},
-			},
-		},
-		{
-			Args: []string{"FOO=bar", "task-a", "task-b"},
-			ExpectedCalls: []taskfile.Call{
-				{Task: "task-a", Direct: true},
-				{Task: "task-b", Direct: true},
-			},
-			ExpectedGlobals: &taskfile.Vars{
-				OrderedMap: orderedmap.FromMapWithOrder(
-					map[string]taskfile.Var{
-						"FOO": {Static: "bar"},
-					},
-					[]string{"FOO"},
-				),
-			},
-		},
-		{
-			Args: nil,
-			ExpectedCalls: []taskfile.Call{
-				{Task: "default", Direct: true},
-			},
-		},
-		{
-			Args: []string{},
-			ExpectedCalls: []taskfile.Call{
-				{Task: "default", Direct: true},
-			},
-		},
-		{
-			Args: []string{"FOO=bar", "BAR=baz"},
-			ExpectedCalls: []taskfile.Call{
-				{Task: "default", Direct: true},
-			},
-			ExpectedGlobals: &taskfile.Vars{
-				OrderedMap: orderedmap.FromMapWithOrder(
-					map[string]taskfile.Var{
-						"FOO": {Static: "bar"},
-						"BAR": {Static: "baz"},
-					},
-					[]string{"FOO", "BAR"},
-				),
-			},
-		},
-	}
-
-	for i, test := range tests {
-		t.Run(fmt.Sprintf("TestArgs%d", i+1), func(t *testing.T) {
-			calls, globals := args.ParseV2(test.Args...)
-			assert.Equal(t, test.ExpectedCalls, calls)
-			if test.ExpectedGlobals.Len() > 0 || globals.Len() > 0 {
-				assert.Equal(t, test.ExpectedGlobals, globals)
-			}
-		})
-	}
-}

cmd/release/main.go

@@ -17,15 +17,8 @@ const (
 	changelogTarget = "docs/docs/changelog.md"
 )
 
-const changelogTemplate = `---
-slug: /changelog/
-sidebar_position: 9
----`
-
 var (
 	changelogReleaseRegex = regexp.MustCompile(`## Unreleased`)
-	changelogUserRegex    = regexp.MustCompile(`@(\w+)`)
-	changelogIssueRegex   = regexp.MustCompile(`#(\d+)`)
 	versionRegex          = regexp.MustCompile(`(?m)^  "version": "\d+\.\d+\.\d+",$`)
 )
 
@@ -92,8 +85,22 @@ func bumpVersion(version *semver.Version, verb string) error {
 }
 
 func changelog(version *semver.Version) error {
+	// Open changelog target file
+	b, err := os.ReadFile(changelogTarget)
+	if err != nil {
+		return err
+	}
+
+	// Get the current frontmatter
+	currentChangelog := string(b)
+	sections := strings.SplitN(currentChangelog, "---", 3)
+	if len(sections) != 3 {
+		return errors.New("error: invalid frontmatter")
+	}
+	frontmatter := strings.TrimSpace(sections[1])
+
 	// Open changelog source file
-	b, err := os.ReadFile(changelogSource)
+	b, err = os.ReadFile(changelogSource)
 	if err != nil {
 		return err
 	}
@@ -109,11 +116,7 @@ func changelog(version *semver.Version) error {
 	}
 
 	// Add the frontmatter to the changelog
-	changelog = fmt.Sprintf("%s\n\n%s", changelogTemplate, changelog)
-
-	// Replace @user and #issue with full links
-	changelog = changelogUserRegex.ReplaceAllString(changelog, "[@$1](https://github.com/$1)")
-	changelog = changelogIssueRegex.ReplaceAllString(changelog, "[#$1](https://github.com/go-task/task/issues/$1)")
+	changelog = fmt.Sprintf("---\n%s\n---\n\n%s", frontmatter, changelog)
 
 	// Write the changelog to the target file
 	return os.WriteFile(changelogTarget, []byte(changelog), 0o644)

cmd/task/task.go

@@ -7,7 +7,6 @@ import (
 	"os"
 	"path/filepath"
 	"strings"
-	"time"
 
 	"github.com/spf13/pflag"
 	"mvdan.cc/sh/v3/syntax"
@@ -16,72 +15,22 @@ import (
 	"github.com/go-task/task/v3/args"
 	"github.com/go-task/task/v3/errors"
 	"github.com/go-task/task/v3/internal/experiments"
+	"github.com/go-task/task/v3/internal/flags"
 	"github.com/go-task/task/v3/internal/logger"
 	"github.com/go-task/task/v3/internal/sort"
 	ver "github.com/go-task/task/v3/internal/version"
-	"github.com/go-task/task/v3/taskfile"
+	"github.com/go-task/task/v3/taskfile/ast"
 )
 
-const usage = `Usage: task [flags...] [task...]
-
-Runs the specified task(s). Falls back to the "default" task if no task name
-was specified, or lists all tasks if an unknown task name was specified.
-
-Example: 'task hello' with the following 'Taskfile.yml' file will generate an
-'output.txt' file with the content "hello".
-
-'''
-version: '3'
-tasks:
-  hello:
-    cmds:
-      - echo "I am going to write a file named 'output.txt' now."
-      - echo "hello" > output.txt
-    generates:
-      - output.txt
-'''
-
-Options:
-`
-
-var flags struct {
-	version     bool
-	help        bool
-	init        bool
-	list        bool
-	listAll     bool
-	listJson    bool
-	taskSort    string
-	status      bool
-	force       bool
-	forceAll    bool
-	watch       bool
-	verbose     bool
-	silent      bool
-	assumeYes   bool
-	dry         bool
-	summary     bool
-	exitCode    bool
-	parallel    bool
-	concurrency int
-	dir         string
-	entrypoint  string
-	output      taskfile.Output
-	color       bool
-	interval    time.Duration
-	global      bool
-	experiments bool
-}
-
 func main() {
 	if err := run(); err != nil {
 		l := &logger.Logger{
 			Stdout:  os.Stdout,
 			Stderr:  os.Stderr,
-			Verbose: flags.verbose,
-			Color:   flags.color,
+			Verbose: flags.Verbose,
+			Color:   flags.Color,
 		}
-		if err, ok := err.(*errors.TaskRunError); ok && flags.exitCode {
+		if err, ok := err.(*errors.TaskRunError); ok && flags.ExitCode {
 			l.Errf(logger.Red, "%v\n", err)
 			os.Exit(err.TaskExitCode())
 		}
@@ -99,70 +48,34 @@ func run() error {
 	log.SetFlags(0)
 	log.SetOutput(os.Stderr)
 
-	pflag.Usage = func() {
-		log.Print(usage)
-		pflag.PrintDefaults()
+	if err := flags.Validate(); err != nil {
+		return err
 	}
 
-	pflag.BoolVar(&flags.version, "version", false, "Show Task version.")
-	pflag.BoolVarP(&flags.help, "help", "h", false, "Shows Task usage.")
-	pflag.BoolVarP(&flags.init, "init", "i", false, "Creates a new Taskfile.yml in the current folder.")
-	pflag.BoolVarP(&flags.list, "list", "l", false, "Lists tasks with description of current Taskfile.")
-	pflag.BoolVarP(&flags.listAll, "list-all", "a", false, "Lists tasks with or without a description.")
-	pflag.BoolVarP(&flags.listJson, "json", "j", false, "Formats task list as JSON.")
-	pflag.StringVar(&flags.taskSort, "sort", "", "Changes the order of the tasks when listed. [default|alphanumeric|none].")
-	pflag.BoolVar(&flags.status, "status", false, "Exits with non-zero exit code if any of the given tasks is not up-to-date.")
-	pflag.BoolVarP(&flags.watch, "watch", "w", false, "Enables watch of the given task.")
-	pflag.BoolVarP(&flags.verbose, "verbose", "v", false, "Enables verbose mode.")
-	pflag.BoolVarP(&flags.silent, "silent", "s", false, "Disables echoing.")
-	pflag.BoolVarP(&flags.assumeYes, "yes", "y", false, "Assume \"yes\" as answer to all prompts.")
-	pflag.BoolVarP(&flags.parallel, "parallel", "p", false, "Executes tasks provided on command line in parallel.")
-	pflag.BoolVarP(&flags.dry, "dry", "n", false, "Compiles and prints tasks in the order that they would be run, without executing them.")
-	pflag.BoolVar(&flags.summary, "summary", false, "Show summary about a task.")
-	pflag.BoolVarP(&flags.exitCode, "exit-code", "x", false, "Pass-through the exit code of the task command.")
-	pflag.StringVarP(&flags.dir, "dir", "d", "", "Sets directory of execution.")
-	pflag.StringVarP(&flags.entrypoint, "taskfile", "t", "", `Choose which Taskfile to run. Defaults to "Taskfile.yml".`)
-	pflag.StringVarP(&flags.output.Name, "output", "o", "", "Sets output style: [interleaved|group|prefixed].")
-	pflag.StringVar(&flags.output.Group.Begin, "output-group-begin", "", "Message template to print before a task's grouped output.")
-	pflag.StringVar(&flags.output.Group.End, "output-group-end", "", "Message template to print after a task's grouped output.")
-	pflag.BoolVar(&flags.output.Group.ErrorOnly, "output-group-error-only", false, "Swallow output from successful tasks.")
-	pflag.BoolVarP(&flags.color, "color", "c", true, "Colored output. Enabled by default. Set flag to false or use NO_COLOR=1 to disable.")
-	pflag.IntVarP(&flags.concurrency, "concurrency", "C", 0, "Limit number tasks to run concurrently.")
-	pflag.DurationVarP(&flags.interval, "interval", "I", 0, "Interval to watch for changes.")
-	pflag.BoolVarP(&flags.global, "global", "g", false, "Runs global Taskfile, from $HOME/{T,t}askfile.{yml,yaml}.")
-	pflag.BoolVar(&flags.experiments, "experiments", false, "Lists all the available experiments and whether or not they are enabled.")
+	dir := flags.Dir
+	entrypoint := flags.Entrypoint
 
-	// Gentle force experiment will override the force flag and add a new force-all flag
-	if experiments.GentleForce {
-		pflag.BoolVarP(&flags.force, "force", "f", false, "Forces execution of the directly called task.")
-		pflag.BoolVar(&flags.forceAll, "force-all", false, "Forces execution of the called task and all its dependant tasks.")
-	} else {
-		pflag.BoolVarP(&flags.forceAll, "force", "f", false, "Forces execution even when the task is up-to-date.")
-	}
-
-	pflag.Parse()
-
-	if flags.version {
+	if flags.Version {
 		fmt.Printf("Task version: %s\n", ver.GetVersion())
 		return nil
 	}
 
-	if flags.help {
+	if flags.Help {
 		pflag.Usage()
 		return nil
 	}
 
-	if flags.experiments {
+	if flags.Experiments {
 		l := &logger.Logger{
 			Stdout:  os.Stdout,
 			Stderr:  os.Stderr,
-			Verbose: flags.verbose,
-			Color:   flags.color,
+			Verbose: flags.Verbose,
+			Color:   flags.Color,
 		}
 		return experiments.List(l)
 	}
 
-	if flags.init {
+	if flags.Init {
 		wd, err := os.Getwd()
 		if err != nil {
 			log.Fatal(err)
@@ -173,40 +86,21 @@ func run() error {
 		return nil
 	}
 
-	if flags.global && flags.dir != "" {
-		log.Fatal("task: You can't set both --global and --dir")
-		return nil
-	}
-	if flags.global {
+	if flags.Global {
 		home, err := os.UserHomeDir()
 		if err != nil {
 			return fmt.Errorf("task: Failed to get user home directory: %w", err)
 		}
-		flags.dir = home
+		dir = home
 	}
 
-	if flags.dir != "" && flags.entrypoint != "" {
-		return errors.New("task: You can't set both --dir and --taskfile")
-	}
-	if flags.entrypoint != "" {
-		flags.dir = filepath.Dir(flags.entrypoint)
-		flags.entrypoint = filepath.Base(flags.entrypoint)
-	}
-
-	if flags.output.Name != "group" {
-		if flags.output.Group.Begin != "" {
-			return errors.New("task: You can't set --output-group-begin without --output=group")
-		}
-		if flags.output.Group.End != "" {
-			return errors.New("task: You can't set --output-group-end without --output=group")
-		}
-		if flags.output.Group.ErrorOnly {
-			return errors.New("task: You can't set --output-group-error-only without --output=group")
-		}
+	if entrypoint != "" {
+		dir = filepath.Dir(entrypoint)
+		entrypoint = filepath.Base(entrypoint)
 	}
 
 	var taskSorter sort.TaskSorter
-	switch flags.taskSort {
+	switch flags.TaskSort {
 	case "none":
 		taskSorter = &sort.Noop{}
 	case "alphanumeric":
@@ -214,41 +108,50 @@ func run() error {
 	}
 
 	e := task.Executor{
-		Force:       flags.force,
-		ForceAll:    flags.forceAll,
-		Watch:       flags.watch,
-		Verbose:     flags.verbose,
-		Silent:      flags.silent,
-		AssumeYes:   flags.assumeYes,
-		Dir:         flags.dir,
-		Dry:         flags.dry,
-		Entrypoint:  flags.entrypoint,
-		Summary:     flags.summary,
-		Parallel:    flags.parallel,
-		Color:       flags.color,
-		Concurrency: flags.concurrency,
-		Interval:    flags.interval,
+		Dir:         dir,
+		Entrypoint:  entrypoint,
+		Force:       flags.Force,
+		ForceAll:    flags.ForceAll,
+		Insecure:    flags.Insecure,
+		Download:    flags.Download,
+		Offline:     flags.Offline,
+		Timeout:     flags.Timeout,
+		Watch:       flags.Watch,
+		Verbose:     flags.Verbose,
+		Silent:      flags.Silent,
+		AssumeYes:   flags.AssumeYes,
+		Dry:         flags.Dry || flags.Status,
+		Summary:     flags.Summary,
+		Parallel:    flags.Parallel,
+		Color:       flags.Color,
+		Concurrency: flags.Concurrency,
+		Interval:    flags.Interval,
 
 		Stdin:  os.Stdin,
 		Stdout: os.Stdout,
 		Stderr: os.Stderr,
 
-		OutputStyle: flags.output,
+		OutputStyle: flags.Output,
 		TaskSorter:  taskSorter,
 	}
 
-	listOptions := task.NewListOptions(flags.list, flags.listAll, flags.listJson)
+	listOptions := task.NewListOptions(flags.List, flags.ListAll, flags.ListJson, flags.NoStatus)
 	if err := listOptions.Validate(); err != nil {
 		return err
 	}
 
-	if (listOptions.ShouldListTasks()) && flags.silent {
-		e.ListTaskNames(flags.listAll)
+	if err := e.Setup(); err != nil {
+		return err
+	}
+
+	// If the download flag is specified, we should stop execution as soon as
+	// taskfile is downloaded
+	if flags.Download {
 		return nil
 	}
 
-	if err := e.Setup(); err != nil {
-		return err
+	if (listOptions.ShouldListTasks()) && flags.Silent {
+		return e.ListTaskNames(flags.ListAll)
 	}
 
 	if listOptions.ShouldListTasks() {
@@ -263,8 +166,8 @@ func run() error {
 	}
 
 	var (
-		calls   []taskfile.Call
-		globals *taskfile.Vars
+		calls   []*ast.Call
+		globals *ast.Vars
 	)
 
 	tasksAndVars, cliArgs, err := getArgs()
@@ -272,22 +175,24 @@ func run() error {
 		return err
 	}
 
-	if e.Taskfile.Version.Compare(taskfile.V3) >= 0 {
-		calls, globals = args.ParseV3(tasksAndVars...)
-	} else {
-		calls, globals = args.ParseV2(tasksAndVars...)
+	calls, globals = args.Parse(tasksAndVars...)
+
+	// If there are no calls, run the default task instead
+	if len(calls) == 0 {
+		calls = append(calls, &ast.Call{Task: "default"})
 	}
 
-	globals.Set("CLI_ARGS", taskfile.Var{Static: cliArgs})
+	globals.Set("CLI_ARGS", ast.Var{Value: cliArgs})
+	globals.Set("CLI_FORCE", ast.Var{Value: flags.Force || flags.ForceAll})
 	e.Taskfile.Vars.Merge(globals)
 
-	if !flags.watch {
+	if !flags.Watch {
 		e.InterceptInterruptSignals()
 	}
 
 	ctx := context.Background()
 
-	if flags.status {
+	if flags.Status {
 		return e.Status(ctx, calls...)
 	}
 

completion/zsh/_task

@@ -18,7 +18,7 @@ function __task_list() {
         enabled=1
         cmd+=(--taskfile "$taskfile")
     else
-        for taskfile in Taskfile{,.dist}.{yaml,yml}; do
+        for taskfile in {T,t}askfile{,.dist}.{yaml,yml}; do
             if [[ -f "$taskfile" ]]; then
                 enabled=1
                 break

docs/.prettierignore

@@ -1 +0,0 @@
-docs/changelog.md

docs/babel.config.js

@@ -1,3 +0,0 @@
-module.exports = {
-  presets: [require.resolve('@docusaurus/core/lib/babel/preset')],
-};

docs/babel.config.ts

@@ -0,0 +1,3 @@
+export default {
+  presets: ['@docusaurus/core/lib/babel/preset'],
+};

docs/blog/2023-09-02-introducing-experiments.md

@@ -0,0 +1,142 @@
+---
+title: Introducing Experiments
+description:
+  A look at where task is, where it's going and how we're going to get there.
+slug: task-in-2023
+authors: [pd93]
+tags: [experiments, breaking-changes, roadmap, v4]
+image: https://i.imgur.com/mErPwqL.png
+hide_table_of_contents: false
+---
+
+Lately, Task has been growing extremely quickly and I've found myself thinking a
+lot about the future of the project and how we continue to evolve and grow. I'm
+not much of a writer, but I think one of the things we could do better is to
+communicate these kinds of thoughts to the community. So, with that in mind,
+this is the first (hopefully of many) blog posts talking about Task and what
+we're up to.
+
+<!--truncate-->
+
+## :calendar: So, what have we been up to?
+
+Over the past 12 months or so, [@andreynering] (Author and maintainer of the
+project) and I ([@pd93]) have been working in our spare time to maintain and
+improve v3 of Task and we've made some amazing progress. Here are just some of
+the things we've released in that time:
+
+- An official [extension for VS Code][vscode-task].
+- Internal Tasks ([#818](https://github.com/go-task/task/pull/818)).
+- Task aliases ([#879](https://github.com/go-task/task/pull/879)).
+- Looping over tasks ([#1220](https://github.com/go-task/task/pull/1200)).
+- A series of refactors to the core codebase to make it more maintainable and
+  extensible.
+- Loads of bug fixes and improvements.
+- An integration with [Crowdin][crowdin]. Work is in progress on making our docs
+  available in **7 new languages** (Special thanks to all our translators for
+  the huge help with this!).
+- And much, much more! :sparkles:
+
+We're also working on adding some really exciting and highly requested features
+to Task such as having the ability to run remote Taskfiles
+([#1317](https://github.com/go-task/task/issues/1317)).
+
+None of this would have been possible without the [150 or so (and growing)
+contributors][contributors] to the project, numerous sponsors and a passionate
+community of users. Together we have more than doubled the number of GitHub
+stars to over 8400 :star: since the beginning of 2022 and this continues to
+accelerate. We can't thank you all enough for your help and support! :rocket:
+
+[![Star History Chart](https://api.star-history.com/svg?repos=go-task/task&type=Date)](https://star-history.com/#go-task/task&Date)
+
+## What's next? :thinking:
+
+It's extremely motivating to see so many people using and loving Task. However,
+in this time we've also seen an increase in the number of issues and feature
+requests. In particular, issues that require some kind of breaking change to
+Task. This isn't a bad thing, but as we grow we need to be more responsible
+about how we address these changes in a way that ensures stability and
+compatibility for existing users and their Taskfiles.
+
+At this point you're probably thinking something like:
+
+> "But you use [semantic versioning][semver] - Just release a new major version
+> with your breaking changes."
+
+And you'd be right... sort of. In theory, this sounds great, but the reality is
+that we don't have the time to commit to a major overhaul of Task in one big
+bang release. This would require a colossal amount of time and coordination and
+with full time jobs and personal lives to tend to, this is a difficult
+commitment to make. Smaller, more frequent major releases are also a significant
+inconvenience for users as they have to constantly keep up-to-date with our
+breaking changes. Fortunately, there is a better way.
+
+## What's going to change? :monocle:
+
+Going forwards, breaking changes will be allowed into _minor_ versions of Task
+as "experimental features". To access these features users will need opt-in by
+enabling feature flags. This will allow us to release new features slowly and
+gather feedback from the community before making them the default behavior in a
+future major release.
+
+To prepare users for the next major release, we will maintain a list of
+[deprecated features][deprecations] and [experiments][experiments] on our docs
+website and publish information on how to migrate to the new behavior.
+
+You can read the [full breaking change proposal][breaking-change-proposal] and
+view all the [current experiments and their status][experiments-project] on
+GitHub including the [Gentle Force][gentle-force-experiment] and [Remote
+Taskfiles][remote-taskfiles-experiment] experiments.
+
+## What will happen to v2/v3 features?
+
+v2 has been [officially deprecated][deprecate-version-2-schema]. If you're still
+using a Taskfile with `version: "2"` at the top we _strongly recommend_ that you
+upgrade as soon as possible. Removing v2 will allow us to tidy up the codebase
+and focus on new functionality instead.
+
+When v4 is released, we will continue to support v3 for a period of time (bug
+fixes etc). However, since we are moving from a backward-compatibility model to
+a forwards-compatibility model, **v4 itself will not be backwards compatible
+with v3**.
+
+## v4 When? :eyes:
+
+:man_shrugging: When it's ready.
+
+In all seriousness, we don't have a timeline for this yet. We'll be working on
+the most serious deficiencies of the v3 API first and regularly evaluating the
+state of the project. When we feel its in a good, stable place and we have a
+clear upgrade path for users and a number of stable experiments, we'll start to
+think about v4.
+
+## :wave: Final thoughts
+
+Task is growing fast and we're excited to see where it goes next. We hope that
+the steps we're taking to improve the project and our process will help us to
+continue to grow. As always, if you have any questions or feedback, we encourage
+you to comment on or open [issues][issues] and [discussions][discussions] on
+GitHub. Alternatively, you can join us on [Discord][discord].
+
+I plan to write more of these blog posts in the future on a variety of
+Task-related topics, so make sure to check in occasionally and see what we're up
+to!
+
+<!-- prettier-ignore-start -->
+[vscode-task]: https://github.com/go-task/vscode-task
+[crowdin]: https://crowdin.com
+[contributors]: https://github.com/go-task/task/graphs/contributors
+[semver]: https://semver.org
+[breaking-change-proposal]: https://github.com/go-task/task/discussions/1191
+[@andreynering]: https://github.com/andreynering
+[@pd93]: https://github.com/pd93
+[experiments]: https://taskfile.dev/experiments
+[deprecations]: https://taskfile.dev/deprecations
+[deprecate-version-2-schema]: https://github.com/go-task/task/issues/1197
+[issues]: https://github.com/go-task/task/issues
+[discussions]: https://github.com/go-task/task/discussions
+[discord]: https://discord.gg/6TY36E39UK
+[experiments-project]: https://github.com/orgs/go-task/projects/1
+[gentle-force-experiment]: https://github.com/go-task/task/issues/1200
+[remote-taskfiles-experiment]: https://github.com/go-task/task/issues/1317
+<!-- prettier-ignore-end -->

docs/blog/authors.yml

@@ -3,3 +3,8 @@ andreynering:
   title: Maintainer of Task
   url: https://github.com/andreynering
   image_url: https://github.com/andreynering.png
+pd93:
+  name: Pete Davison
+  title: Maintainer of Task
+  url: https://github.com/pd93
+  image_url: https://github.com/pd93.png

docs/constants.js

@@ -1,11 +0,0 @@
-const GITHUB_URL = 'https://github.com/go-task/task';
-const TWITTER_URL = 'https://twitter.com/taskfiledev';
-const MASTODON_URL = 'https://fosstodon.org/@task';
-const DISCORD_URL = 'https://discord.gg/6TY36E39UK';
-
-module.exports = {
-  DISCORD_URL,
-  GITHUB_URL,
-  MASTODON_URL,
-  TWITTER_URL
-};

docs/constants.ts

@@ -0,0 +1,4 @@
+export const GITHUB_URL = 'https://github.com/go-task/task';
+export const TWITTER_URL = 'https://twitter.com/taskfiledev';
+export const MASTODON_URL = 'https://fosstodon.org/@task';
+export const DISCORD_URL = 'https://discord.gg/6TY36E39UK';

docs/docs/api_reference.md

@@ -11,13 +11,13 @@ toc_max_heading_level: 5
 
 Task command line tool has the following syntax:
 
-```bash
+```shell
 task [--flags] [tasks...] [-- CLI_ARGS...]
 ```
 
 :::tip
 
-If `--` is given, all remaning arguments will be assigned to a special
+If `--` is given, all remaining arguments will be assigned to a special
 `CLI_ARGS` variable
 
 :::
@@ -70,6 +70,11 @@ A full list of the exit codes and their descriptions can be found below:
 | 100  | No Taskfile was found                                        |
 | 101  | A Taskfile already exists when trying to initialize one      |
 | 102  | The Taskfile is invalid or cannot be parsed                  |
+| 103  | A remote Taskfile could not be downloaded                    |
+| 104  | A remote Taskfile was not trusted by the user                |
+| 105  | A remote Taskfile was could not be fetched securely          |
+| 106  | No cache was found for a remote Taskfile in offline mode     |
+| 107  | No schema version was defined in the Taskfile                |
 | 200  | The specified task could not be found                        |
 | 201  | An error occurred while executing a command inside of a task |
 | 202  | The user tried to invoke a task that is internal             |
@@ -121,14 +126,17 @@ There are some special variables that is available on the templating system:
 | Var                | Description                                                                                                                                              |
 | ------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------- |
 | `CLI_ARGS`         | Contain all extra arguments passed after `--` when calling Task through the CLI.                                                                         |
+| `CLI_FORCE`        | A boolean containing whether the `--force` or `--force-all` flags were set.                                                                              |
 | `TASK`             | The name of the current task.                                                                                                                            |
-| `ROOT_DIR`         | The absolute path of the root Taskfile.                                                                                                                  |
-| `TASKFILE_DIR`     | The absolute path of the included Taskfile.                                                                                                              |
+| `ROOT_TASKFILE`    | The absolute path of the root Taskfile.                                                                                                                  |
+| `ROOT_DIR`         | The absolute path of the root Taskfile directory.                                                                                                        |
+| `TASKFILE`         | The absolute path of the included Taskfile.                                                                                                              |
+| `TASKFILE_DIR`     | The absolute path of the included Taskfile directory.                                                                                                    |
 | `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.                                                                                                                             |
-| `ITEM`             | The value of the current iteration when using the `for` property. Can be changed to a different variable name using `as:`.                                                                                        |
+| `ITEM`             | The value of the current iteration when using the `for` property. Can be changed to a different variable name using `as:`.                               |
 
 ## ENV
 
@@ -152,12 +160,12 @@ Some environment variables can be overridden to adjust Task behavior.
 | ---------- | ---------------------------------- | ------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
 | `version`  | `string`                           |               | Version of the Taskfile. The current version is `3`.                                                                                                                   |
 | `output`   | `string`                           | `interleaved` | Output mode. Available options: `interleaved`, `group` and `prefixed`.                                                                                                 |
-| `method`   | `string`                           | `checksum`    | Default method in this Taskfile. Can be overriden in a task by task basis. Available options: `checksum`, `timestamp` and `none`.                                      |
+| `method`   | `string`                           | `checksum`    | Default method in this Taskfile. Can be overridden in a task by task basis. Available options: `checksum`, `timestamp` and `none`.                                     |
 | `includes` | [`map[string]Include`](#include)   |               | Additional Taskfiles to be included.                                                                                                                                   |
 | `vars`     | [`map[string]Variable`](#variable) |               | A set of global variables.                                                                                                                                             |
 | `env`      | [`map[string]Variable`](#variable) |               | A set of global environment variables.                                                                                                                                 |
 | `tasks`    | [`map[string]Task`](#task)         |               | A set of task definitions.                                                                                                                                             |
-| `silent`   | `bool`                             | `false`       | Default 'silent' options for this Taskfile. If `false`, can be overidden with `true` in a task by task basis.                                                          |
+| `silent`   | `bool`                             | `false`       | Default 'silent' options for this Taskfile. If `false`, can be overridden with `true` in a task by task basis.                                                         |
 | `dotenv`   | `[]string`                         |               | A list of `.env` file paths to be parsed.                                                                                                                              |
 | `run`      | `string`                           | `always`      | Default 'run' option for this Taskfile. Available options: `always`, `once` and `when_changed`.                                                                        |
 | `interval` | `string`                           | `5s`          | Sets a different watch interval when using `--watch`, the default being 5 seconds. This string should be a valid [Go Duration](https://pkg.go.dev/time#ParseDuration). |
@@ -207,6 +215,19 @@ vars:
 
 :::
 
+:::info
+
+In a variables map, variables defined later may reference variables defined
+earlier (declaration order is respected):
+
+```yaml
+vars:
+  FIRST_VAR: "hello"
+  SECOND_VAR: "{{.FIRST_VAR}} world"
+```
+
+:::
+
 ### Task
 
 | Attribute       | Type                               | Default                                               | Description                                                                                                                                                                                                                                                                                              |
@@ -221,7 +242,6 @@ vars:
 | `sources`       | `[]string`                         |                                                       | A list of sources to check before running this task. Relevant for `checksum` and `timestamp` methods. Can be file paths or star globs.                                                                                                                                                                   |
 | `generates`     | `[]string`                         |                                                       | A list of files meant to be generated by this task. Relevant for `timestamp` method. Can be file paths or star globs.                                                                                                                                                                                    |
 | `status`        | `[]string`                         |                                                       | A list of commands to check if this task should run. The task is skipped otherwise. This overrides `method`, `sources` and `generates`.                                                                                                                                                                  |
-| `requires`      | `[]string`                         |                                                       | A list of variables which should be set if this task is to run, if any of these variables are unset the task will error and not run.                                                                                                                                                                     |
 | `preconditions` | [`[]Precondition`](#precondition)  |                                                       | A list of commands to check if this task should run. If a condition is not met, the task will error.                                                                                                                                                                                                     |
 | `requires`      | [`Requires`](#requires)            |                                                       | A list of required variables which should be set if this task is to run, if any variables listed are unset the task will error and not run.                                                                                                                                                              |
 | `dir`           | `string`                           |                                                       | The directory in which this task should run. Defaults to the current working directory.                                                                                                                                                                                                                  |

docs/docs/community.md

@@ -1,6 +1,6 @@
 ---
 slug: /community/
-sidebar_position: 10
+sidebar_position: 9
 ---
 
 # Community
@@ -11,7 +11,8 @@ thankful for everyone that helps me to improve the overall experience.
 
 ## Translations
 
-We use [Crowdin](https://crowdin.com/project/taskfile) to translate our document.
+We use [Crowdin](https://crowdin.com/project/taskfile) to translate our
+document.
 
 ## Integrations
 
@@ -23,10 +24,8 @@ can view the full list of community integrations
 
 Some installation methods are maintained by third party:
 
-- [GitHub Actions](https://github.com/arduino/setup-task) by
-  [@arduino](https://github.com/arduino)
-- [AUR](https://aur.archlinux.org/packages/go-task-bin) by
-  [@carlsmedstad](https://github.com/carlsmedstad)
+- [GitHub Actions](https://github.com/arduino/setup-task) by @arduino
+- [AUR](https://aur.archlinux.org/packages/go-task-bin) by @carlsmedstad
 - [Scoop](https://github.com/ScoopInstaller/Main/blob/master/bucket/task.json)
 - [Fedora](https://packages.fedoraproject.org/pkgs/golang-github-task/go-task/)
 - [NixOS](https://github.com/NixOS/nixpkgs/blob/master/pkgs/development/tools/go-task/default.nix)

docs/docs/contributing.md

@@ -76,15 +76,15 @@ by using `task docs` (requires `nodejs` & `yarn`). All content is written in
 Markdown and is located in the `docs/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.md)
-is necessary. This document contains descriptions and examples of how to use
-Task features. If you're adding a new feature, try to find an appropriate place
-to add a new section. If you're updating an existing feature, ensure that the
-documentation and any examples are up-to-date. Ensure that any examples follow
-the [Taskfile Styleguide](./styleguide.md).
+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 features. If you're adding a new feature, try to
+find an appropriate place to add a new section. If you're updating an existing
+feature, ensure that the documentation and any examples are up-to-date. Ensure
+that any examples follow the [Taskfile Styleguide](/styleguide).
 
 If you added a new field, command or flag, ensure that you add it to the
-[API Reference](./api_reference.md). New fields also need to be added to the
+[API Reference](/api). New fields also need to be added to the
 [JSON Schema][json-schema]. The descriptions for fields in the API reference and
 the schema should match.
 
@@ -138,7 +138,7 @@ contributions.
 
 All kinds of contributions are welcome, whether its a typo fix or a shiny new
 feature. You can also contribute by upvoting/commenting on issues, helping to
-answer questions or contributing to other [community projects](./community.md).
+answer questions or contributing to other [community projects](/community).
 
 > I'm stuck, where can I get help?
 

docs/docs/deprecations/deprecations.md

@@ -0,0 +1,19 @@
+---
+slug: /deprecations/
+sidebar_position: 7
+---
+
+# Deprecations
+
+As Task evolves, it occasionally outgrows some of its functionality. This can be
+because they are no longer useful, because another feature has replaced it or
+because of a change in the way that Task works internally.
+
+When this happens, we mark the functionality as deprecated. This means that it
+will be removed in a future version of Task. This functionality will continue to
+work until that time, but we strongly recommend that you do not implement this
+functionality in new Taskfiles and make a plan to migrate away from it as soon
+as possible.
+
+You can view a full list of active deprecations in the "Deprecations" section of
+the sidebar.

docs/docs/deprecations/template.md

@@ -0,0 +1,23 @@
+---
+# This is a template for an experiments documentation
+# Copy this page and fill in the details as necessary
+title: '--- Template ---'
+sidebar_position: -1 # Always push to the top
+draft: true # Hide in production
+---
+
+# \{Name of Deprecated Feature\} (#\{Issue\})
+
+:::warning
+
+This deprecation breaks the following functionality:
+
+- \{list any existing functionality that will be broken by this deprecation\}
+- \{if there are no breaking changes, remove this admonition\}
+
+:::
+
+\{Short description of the feature/behavior and why it is being deprecated\}
+
+\{Short explanation of any replacement features/behaviors and how users should
+migrate to it\}

docs/docs/deprecations/version_2_schema.md

@@ -0,0 +1,33 @@
+---
+slug: /deprecations/version-2-schema/
+---
+
+# Version 2 Schema (#1197)
+
+:::warning
+
+This deprecation breaks the following functionality:
+
+- Any Taskfiles that use the version 2 schema
+- `Taskvar.yml` files
+
+:::
+
+The Taskfile version 2 schema was introduced in March 2018 and replaced by
+version 3 in August 2019. In May 2023 [we published a deprecation
+notice][deprecation-notice] for the version 2 schema on the basis that the vast
+majority of users had already upgraded to version 3 and removing support for
+version 2 would allow us to tidy up the codebase and focus on new functionality
+instead.
+
+In December 2023, the final version of Task that supports the version 2 schema
+([v3.33.0][v3.33.0]) was published and all legacy code was removed from Task's
+main branch. To use a more recent version of Task, you will need to ensure that
+your Taskfile uses the version 3 schema instead. A list of changes between
+version 2 and version 3 are available in the [Task v3 Release Notes][v3.0.0].
+
+<!-- prettier-ignore-start -->
+[v3.0.0]: https://github.com/go-task/task/releases/tag/v3.0.0
+[v3.33.0]: https://github.com/go-task/task/releases/tag/v3.33.0
+[deprecation-notice]: https://github.com/go-task/task/issues/1197
+<!-- prettier-ignore-end -->

docs/docs/donate.md

@@ -1,6 +1,6 @@
 ---
 slug: /donate/
-sidebar_position: 15
+sidebar_position: 16
 ---
 
 # Donate
@@ -19,7 +19,8 @@ the website homepage and on the GitHub repository README. Make contact with
 ## GitHub Sponsors
 
 The preferred way to donate to the maintainers is via GitHub Sponsors. Just use
-the following links to do your donation:
+the following links to do your donation. We suggest a 50/50 split to each
+maintainer of the total amount you plan to donate to the project.
 
 - [@andreynering](https://github.com/sponsors/andreynering)
 - [@pd93](https://github.com/sponsors/pd93)

docs/docs/experiments/any_variables.mdx

@@ -0,0 +1,346 @@
+---
+slug: /experiments/any-variables/
+---
+
+import Tabs from '@theme/Tabs';
+import TabItem from '@theme/TabItem';
+
+# Any Variables (#1415)
+
+:::caution
+
+All experimental features are subject to breaking changes and/or removal _at any
+time_. We strongly recommend that you do not use these features in a production
+environment. They are intended for testing and feedback only.
+
+:::
+
+Currently, Task only supports string variables. This experiment allows you to
+specify and use the following variable types:
+
+- `string`
+- `bool`
+- `int`
+- `float`
+- `array`
+- `map`
+
+This allows you to have a lot more flexibility in how you use variables in
+Task's templating engine. There are two active proposals for this experiment.
+Click on the tabs below to switch between them.
+
+<Tabs defaultValue="1" queryString="proposal"
+  values={[
+    {label: 'Proposal 1', value: '1'},
+    {label: 'Proposal 2', value: '2'}
+  ]}>
+
+<TabItem value="1">
+
+:::warning
+
+This experiment proposal breaks the following functionality:
+
+- Dynamically defined variables (using the `sh` keyword)
+
+:::
+
+:::info
+
+To enable this experiment, set the environment variable:
+`TASK_X_ANY_VARIABLES=1`. Check out [our guide to enabling experiments
+][enabling-experiments] for more information.
+
+:::
+
+## Maps
+
+This proposal removes support for the `sh` keyword in favour of a new syntax for
+dynamically defined variables, This allows you to define a map directly as you
+would for any other type:
+
+```yaml
+version: 3
+
+tasks:
+  foo:
+    vars:
+      FOO: {a: 1, b: 2, c: 3} # <-- Directly defined map on the `FOO` key
+    cmds:
+      - 'echo {{.FOO.a}}'
+```
+
+## Migration
+
+Taskfiles with dynamically defined variables via the `sh` subkey will no longer
+work with this experiment enabled. In order to keep using dynamically defined
+variables, you will need to migrate your Taskfile to use the new syntax.
+
+Previously, you might have defined a dynamic variable like this:
+
+```yaml
+version: 3
+
+tasks:
+  foo:
+    vars:
+      CALCULATED_VAR:
+        sh: 'echo hello'
+    cmds:
+      - 'echo {{.CALCULATED_VAR}}'
+```
+
+With this experiment enabled, you will need to remove the `sh` subkey and define
+your command as a string that begins with a `$`. This will instruct Task to
+interpret the string as a command instead of a literal value and the variable
+will be populated with the output of the command. For example:
+
+```yaml
+version: 3
+
+tasks:
+  foo:
+    vars:
+      CALCULATED_VAR: '$echo hello'
+    cmds:
+      - 'echo {{.CALCULATED_VAR}}'
+```
+
+If your current Taskfile contains a string variable that begins with a `$`, you
+will now need to escape the `$` with a backslash (`\`) to stop Task from
+executing it as a command.
+
+</TabItem>
+
+<TabItem value="2">
+
+:::info
+
+To enable this experiment, set the environment variable:
+`TASK_X_ANY_VARIABLES=2`. Check out [our guide to enabling experiments
+][enabling-experiments] for more information.
+
+:::
+
+## Maps
+
+This proposal maintains backwards-compatibility and the `sh` subkey and adds
+another new `map` subkey for defining map variables:
+
+```yaml
+version: 3
+
+tasks:
+  foo:
+    vars:
+      FOO:
+        map: {a: 1, b: 2, c: 3} # <-- Defined using the `map' subkey instead of directly on 'FOO'
+      BAR: true # <-- Other types of variables are still defined directly on the key
+      BAZ:
+        sh: 'echo Hello Task' # <-- The `sh` subkey is still supported
+    cmds:
+      - 'echo {{.FOO.a}}'
+```
+
+## Parsing JSON and YAML
+
+In addition to the new `map` keyword, this proposal also adds support for the
+`json` and `yaml` keywords for parsing JSON and YAML strings into real
+objects/arrays. This is similar to the `fromJSON` template function, but means
+that you only have to parse the JSON/YAML once when you declare the variable,
+instead of every time you want to access a value.
+
+Before:
+
+```yaml
+version: 3
+
+tasks:
+  foo:
+    vars:
+      FOO: '{"a": 1, "b": 2, "c": 3}' # <-- JSON string
+    cmds:
+      - 'echo {{(fromJSON .FOO).a}}' # <-- Parse JSON string every time you want to access a value
+      - 'echo {{(fromJSON .FOO).b}}'
+```
+
+After:
+
+```yaml
+version: 3
+
+tasks:
+  foo:
+    vars:
+      FOO:
+        json: '{"a": 1, "b": 2, "c": 3}' # <-- JSON string parsed once
+    cmds:
+      - 'echo {{.FOO.a}}' # <-- Access values directly
+      - 'echo {{.FOO.b}}'
+```
+
+## Variables by reference
+
+Lastly, this proposal adds support for defining and passing variables by
+reference. This is really important now that variables can be types other than a
+string. Previously, to send a variable from one task to another, you would have
+to use the templating system to pass it:
+
+```yaml
+version: 3
+
+tasks:
+  foo:
+    vars:
+      FOO: [A, B, C] # <-- FOO is defined as an array
+    cmds:
+      - task: bar
+        vars:
+          FOO: '{{.FOO}}' # <-- FOO gets converted to a string when passed to bar
+  bar:
+    cmds:
+      - 'echo {{index .FOO 0}}' # <-- FOO is a string so the task outputs '91' which is the ASCII code for '[' instead of the expected 'A'
+```
+
+Unfortunately, this results in the value always being passed as a string as this
+is the output type of the templater and operations on the passed variable may
+not behave as expected. With this proposal, you can now pass variables by
+reference using the `ref` subkey:
+
+```yaml
+version: 3
+
+tasks:
+  foo:
+    vars:
+      FOO: [A, B, C] # <-- FOO is defined as an array
+    cmds:
+      - task: bar
+        vars:
+          FOO:
+            ref: FOO # <-- FOO gets passed by reference to bar and maintains its type
+  bar:
+    cmds:
+      - 'echo {{index .FOO 0}}' # <-- FOO is still a map so the task outputs 'A' as expected
+```
+
+This means that the type of the variable is maintained when it is passed to
+another Task. This also works the same way when calling `deps` and when defining
+a variable and can be used in any combination:
+
+```yaml
+version: 3
+
+tasks:
+  foo:
+    vars:
+      FOO: [A, B, C] # <-- FOO is defined as an array
+      BAR:
+        ref: FOO # <-- BAR is defined as a reference to FOO
+    deps:
+      - task: bar
+        vars:
+          BAR:
+            ref: BAR # <-- BAR gets passed by reference to bar and maintains its type
+  bar:
+    cmds:
+      - 'echo {{index .BAR 0}}' # <-- BAR still refers to FOO so the task outputs 'A'
+```
+
+</TabItem></Tabs>
+
+---
+
+## Common to both proposals
+
+Both proposals add support for all other variable types by directly defining
+them in the Taskfile. For example:
+
+### Evaluating booleans
+
+```yaml
+version: 3
+
+tasks:
+  foo:
+    vars:
+      BOOL: false
+    cmds:
+      - '{{if .BOOL}}echo foo{{end}}'
+```
+
+### Arithmetic
+
+```yaml
+version: 3
+
+tasks:
+  foo:
+    vars:
+      INT: 10
+      FLOAT: 3.14159
+    cmds:
+      - 'echo {{add .INT .FLOAT}}'
+```
+
+### Ranging
+
+```yaml
+version: 3
+
+tasks:
+  foo:
+    vars:
+      ARRAY: [1, 2, 3]
+    cmds:
+      - 'echo {{range .ARRAY}}{{.}}{{end}}'
+```
+
+There are many more templating functions which can be used with the new types of
+variables. For a full list, see the [slim-sprig][slim-sprig] documentation.
+
+## Looping over variables
+
+Previously, you would have to use a delimiter separated string to loop over an
+arbitrary list of items in a variable and split them by using the `split` subkey
+to specify the delimiter:
+
+```yaml
+version: 3
+
+tasks:
+  foo:
+    vars:
+      LIST: 'foo,bar,baz'
+    cmds:
+      - for:
+          var: LIST
+          split: ','
+        cmd: echo {{.ITEM}}
+```
+
+Both of these proposals add support for looping over "collection-type" variables
+using the `for` keyword, so now you are able to loop over a map/array variable
+directly:
+
+```yaml
+version: 3
+
+tasks:
+  foo:
+    vars:
+      LIST: [foo, bar, baz]
+    cmds:
+      - for:
+          var: LIST
+        cmd: echo {{.ITEM}}
+```
+
+When looping over a map we also make an additional `{{.KEY}}` variable availabe
+that holds the string value of the map key. Remember that maps are unordered, so
+the order in which the items are looped over is random.
+
+<!-- prettier-ignore-start -->
+[enabling-experiments]: /experiments/#enabling-experiments
+[slim-sprig]: https://go-task.github.io/slim-sprig/
+<!-- prettier-ignore-end -->

docs/docs/experiments/experiments.md

@@ -1,6 +1,6 @@
 ---
 slug: /experiments/
-sidebar_position: 5
+sidebar_position: 6
 ---
 
 # Experiments
@@ -13,88 +13,119 @@ environment. They are intended for testing and feedback only.
 
 :::
 
-In order to allow Task to evolve quickly, we roll out breaking changes to minor
-versions behind experimental flags. This allows us to gather feedback on
-breaking changes before committing to a major release. This document describes
-the current set of experimental features and the deprecated feature that they
-are intended to replace.
+In order to allow Task to evolve quickly, we sometimes roll out breaking changes
+to minor versions behind experimental flags. This allows us to gather feedback
+on breaking changes before committing to a major release. This process can also
+be used to gather feedback on important non-breaking features before their
+design is completed. This document describes the
+[experiment workflow](#workflow) and how you can get involved.
 
-You can enable an experimental feature by:
+You can view the full list of active experiments in the sidebar submenu to the
+left of the page and click on each one to find out more about it.
 
-1. Using the relevant environment variable in front of a task command. For
+## Enabling Experiments
+
+Task uses environment variables to detect whether or not an experiment is
+enabled. All of the experiment variables will begin with the same `TASK_X_`
+prefix followed by the name of the experiment. You can find the exact name for
+each experiment on their respective pages in the sidebar. If the variable is set
+`=1` then it will be enabled. Some experiments may have multiple proposals, in
+which case, you will need to set the variable equal to the number of the
+proposal that you want to enable (`=2`, `=3` etc).
+
+There are three main ways to set the environment variables for an experiment.
+Which method you use depends on how you intend to use the experiment:
+
+1. Prefixing your task commands with the relevant environment variable(s). For
    example, `TASK_X_{FEATURE}=1 task {my-task}`. This is intended for one-off
    invocations of Task to test out experimental features.
-1. Using the relevant environment variable in your "dotfiles" (e.g. `.bashrc`,
-   `.zshrc` etc.). This is intended for permanently enabling experimental
-   features in your environment.
+1. Adding the relevant environment variable(s) in your "dotfiles" (e.g.
+   `.bashrc`, `.zshrc` etc.). This will permanently enable experimental features
+   for your personal environment.
+
+   ```shell title="~/.bashrc"
+   export TASK_X_FEATURE=1
+   ```
+
 1. Creating a `.env` file in the same directory as your root Taskfile that
-   contains the relevant environment variables. e.g.
+   contains the relevant environment variable(s). This allows you to enable an
+   experimental feature at a project level. If you commit the `.env` file to
+   source control then other users of your project will also have these
+   experiments enabled.
 
-```shell
-# .env
-TASK_X_FEATURE=1
-```
+   ```shell title=".env"
+   TASK_X_FEATURE=1
+   ```
 
-## Current Experimental Features and Deprecations
+## Workflow
 
-Each section below details an experiment or deprecation and explains what the
-flags/environment variables to enable the experiment are and how the feature's
-behavior will change. It will also explain what you need to do to migrate any
-existing Taskfiles to the new behavior.
+Experiments are a way for us to test out new features in Task before committing
+to them in a major release. Because this concept is built around the idea of
+feedback from our community, we have built a workflow for the process of
+introducing these changes. This ensures that experiments are given the attention
+and time that they need and that we are getting the best possible results out of
+them.
 
-<!-- EXPERIMENT TEMPLATE - Include sections as necessary...
+The sections below describe the various stages that an experiment must go
+through from its proposal all the way to being released in a major version of
+Task.
 
-### ![experiment] {Feature} ([#{issue}](https://github.com/go-task/task/issues/{issue})), ...)
+### 1. Proposal
 
-- Environment variable: `TASK_X_{feature}`
-- Deprecates: {list any existing functionality that will be deprecated by this experiment}
-- Breaks: {list any existing functionality that will be broken by this experiment}
+All experimental features start with a proposal in the form of a GitHub issue.
+If the maintainers decide that an issue has enough support and is a breaking
+change or is complex/controversial enough to require user feedback, then the
+issue will be marked with the `experiment: proposal` label. At this point, the
+issue becomes a proposal and a period of consultation begins. During this
+period, we request that users provide feedback on the proposal and how it might
+effect their use of Task. It is up to the discretion of the maintainers to
+decide how long this period lasts.
 
-{Short description of the feature}
+### 2. Draft
 
-{Short explanation of how users should migrate to the new behavior}
+Once a proposal's consultation ends, a contributor may pick up the work and
+begin the initial implementation. Once a PR is opened, the maintainers will
+ensure that it meets the requirements for an experimental feature (i.e. flags
+are in the right format etc) and merge the feature. Once this code is released,
+the status will be updated via the `experiment: draft` label. This indicates
+that an implementation is now available for use in a release and the experiment
+is open for feedback.
 
--->
+:::note
 
-### ![deprecated] Version 2 Schema ([#1197][deprecate-version-2-schema])
+During the draft period, major changes to the implementation may be made based
+on the feedback received from users. There are _no stability guarantees_ and
+experimental features may be abandoned _at any time_.
 
-The Taskfile v2 schema was introduced in March 2018 and replaced by version 3 in
-August the following year. Users have had a long time to update and so we feel
-that it is time to tidy up the codebase and focus on new functionality instead.
+:::
 
-This notice does not mean that we are immediately removing support for version 2
-schemas. However, support will not be extended to future major releases and we
-_strongly recommend_ that anybody still using a version 2 schema upgrades to
-version 3 as soon as possible.
+### 3. Candidate
 
-A list of changes between version 2 and version 3 are available in the [Task v3
-Release Notes][version-3-release-notes].
+Once an acceptable level of consensus has been reached by the community and
+feedback/changes are less frequent/significant, the status may be updated via
+the `experiment: candidate` label. This indicates that a proposal is _likely_ to
+accepted and will enter a period for final comments and minor changes.
 
-### ![experiment] Gentle Force ([#1200](https://github.com/go-task/task/issues/1200))
+### 4. Stable
 
-- Environment variable: `TASK_X_FORCE=1`
-- Breaks: `--force` flag
+Once a suitable amount of time has passed with no changes or feedback, an
+experiment will be given the `experiment: stable` label. At this point, the
+functionality will be treated like any other feature in Task and any changes
+_must_ be backward compatible. This allows users to migrate to the new
+functionality without having to worry about anything breaking in future
+releases. This provides the best experience for users migrating to a new major
+version.
 
-The `--force` flag currently forces _all_ tasks to run regardless of the status
-checks. This can be useful, but we have found that most of the time users only
-expect the direct task they are calling to be forced and _not_ all of its
-dependant tasks.
+### 5. Released
 
-This experiment changes the `--force` flag to only force the directly called
-task. All dependant tasks will have their statuses checked as normal and will
-only run if Task considers them to be out of date. A new `--force-all` flag will
-also be added to maintain the current behavior for users that need this
-functionality.
+When making a new major release of Task, all experiments marked as
+`experiment: stable` will move to `experiment: released` and their behaviors
+will become the new default in Task. Experiments in an earlier stage (i.e. not
+stable) cannot be released and so will continue to be experiments in the new
+version.
 
-If you want to migrate, but continue to force all dependant tasks to run, you
-should replace all uses of the `--force` flag with `--force-all`. Alternatively,
-if you want to adopt the new behavior, you can continue to use the `--force`
-flag as you do now!
+### Abandoned / Superseded
 
-<!-- prettier-ignore-start -->
-[breaking-change-proposal]: https://github.com/go-task/task/discussions/1191
-[deprecate-version-2-schema]: https://github.com/go-task/task/issues/1197
-[version-3-release-notes]: https://github.com/go-task/task/releases/tag/v3.0.0
-[deprecated]: https://img.shields.io/badge/deprecated-red
-[experiment]: https://img.shields.io/badge/experiment-yellow
-<!-- prettier-ignore-end -->
+If an experiment is unsuccessful at any point then it will be given the
+`experiment: abandoned` or `experiment: superseded` labels depending on which is
+more suitable. These experiments will be removed from Task.

docs/docs/experiments/gentle_force.md

@@ -0,0 +1,49 @@
+---
+slug: /experiments/gentle-force/
+---
+
+# Gentle Force (#1200)
+
+:::caution
+
+All experimental features are subject to breaking changes and/or removal _at any
+time_. We strongly recommend that you do not use these features in a production
+environment. They are intended for testing and feedback only.
+
+:::
+
+:::warning
+
+This experiment breaks the following functionality:
+
+- The `--force` flag
+
+:::
+
+:::info
+
+To enable this experiment, set the environment variable: `TASK_X_FORCE=1`. Check
+out [our guide to enabling experiments ][enabling-experiments] for more
+information.
+
+:::
+
+The `--force` flag currently forces _all_ tasks to run regardless of the status
+checks. This can be useful, but we have found that most of the time users only
+expect the direct task they are calling to be forced and _not_ all of its
+dependant tasks.
+
+This experiment changes the `--force` flag to only force the directly called
+task. All dependant tasks will have their statuses checked as normal and will
+only run if Task considers them to be out of date. A new `--force-all` flag will
+also be added to maintain the current behavior for users that need this
+functionality.
+
+If you want to migrate, but continue to force all dependant tasks to run, you
+should replace all uses of the `--force` flag with `--force-all`. Alternatively,
+if you want to adopt the new behavior, you can continue to use the `--force`
+flag as you do now!
+
+<!-- prettier-ignore-start -->
+[enabling-experiments]: /experiments/#enabling-experiments
+<!-- prettier-ignore-end -->

docs/docs/experiments/remote_taskfiles.md

@@ -0,0 +1,105 @@
+---
+slug: /experiments/remote-taskfiles/
+---
+
+# Remote Taskfiles (#1317)
+
+:::caution
+
+All experimental features are subject to breaking changes and/or removal _at any
+time_. We strongly recommend that you do not use these features in a production
+environment. They are intended for testing and feedback only.
+
+:::
+
+:::info
+
+To enable this experiment, set the environment variable:
+`TASK_X_REMOTE_TASKFILES=1`. Check out [our guide to enabling experiments
+][enabling-experiments] for more information.
+
+:::
+
+This experiment allows you to specify a remote Taskfile URL when including a
+Taskfile. For example:
+
+```yaml
+version: '3'
+
+includes:
+  my-remote-namespace: https://raw.githubusercontent.com/my-org/my-repo/main/Taskfile.yml
+```
+
+This works exactly the same way that including a local file does. Any tasks in
+the remote Taskfile will be available to run from your main Taskfile via the
+namespace `my-remote-namespace`. For example, if the remote file contains the
+following:
+
+```yaml
+version: '3'
+
+tasks:
+  hello:
+    silent: true
+    cmds:
+      - echo "Hello from the remote Taskfile!"
+```
+
+and you run `task my-remote-namespace:hello`, it will print the text: "Hello
+from the remote Taskfile!" to your console.
+
+## Security
+
+Running commands from sources that you do not control is always a potential
+security risk. For this reason, we have added some checks when using remote
+Taskfiles:
+
+1. When running a task from a remote Taskfile for the first time, Task will
+   print a warning to the console asking you to check that you are sure that you
+   trust the source of the Taskfile. If you do not accept the prompt, then Task
+   will exit with code `104` (not trusted) and nothing will run. If you accept
+   the prompt, the remote Taskfile will run and further calls to the remote
+   Taskfile will not prompt you again.
+2. Whenever you run a remote Taskfile, Task will create and store a checksum of
+   the file that you are running. If the checksum changes, then Task will print
+   another warning to the console to inform you that the contents of the remote
+   file has changed. If you do not accept the prompt, then Task will exit with
+   code `104` (not trusted) and nothing will run. If you accept the prompt, the
+   checksum will be updated and the remote Taskfile will run.
+
+Sometimes you need to run Task in an environment that does not have an
+interactive terminal, so you are not able to accept a prompt. In these cases you
+are able to tell task to accept these prompts automatically by using the `--yes`
+flag. Before enabling this flag, you should:
+
+1. Be sure that you trust the source and contents of the remote Taskfile.
+2. Consider using a pinned version of the remote Taskfile (e.g. A link
+   containing a commit hash) to prevent Task from automatically accepting a
+   prompt that says a remote Taskfile has changed.
+
+Task currently supports both `http` and `https` URLs. However, the `http`
+requests will not execute by default unless you run the task with the
+`--insecure` flag. This is to protect you from accidentally running a remote
+Taskfile that is hosted on and unencrypted connection. Sources that are not
+protected by TLS are vulnerable to [man-in-the-middle
+attacks][man-in-the-middle-attacks] and should be avoided unless you know what
+you are doing.
+
+## Caching & Running Offline
+
+Whenever you run a remote Taskfile, the latest copy will be downloaded from the
+internet and cached locally. If for whatever reason, you lose access to the
+internet, you will still be able to run your tasks by specifying the `--offline`
+flag. This will tell Task to use the latest cached version of the file instead
+of trying to download it. You are able to use the `--download` flag to update
+the cached version of the remote files without running any tasks.
+
+By default, Task will timeout requests to download remote files after 10 seconds
+and look for a cached copy instead. This timeout can be configured by setting
+the `--timeout` flag and specifying a duration. For example, `--timeout 5s` will
+set the timeout to 5 seconds.
+
+<!-- prettier-ignore-start -->
+[enabling-experiments]: /experiments/#enabling-experiments
+[man-in-the-middle-attacks]: https://en.wikipedia.org/wiki/Man-in-the-middle_attack
+<!-- prettier-ignore-end -->

docs/docs/experiments/template.md

@@ -0,0 +1,42 @@
+---
+# This is a template for an experiments documentation
+# Copy this page and fill in the details as necessary
+title: '--- Template ---'
+sidebar_position: -1 # Always push to the top
+draft: true # Hide in production
+---
+
+# \{Name of Experiment\} (#\{Issue\})
+
+:::caution
+
+All experimental features are subject to breaking changes and/or removal _at any
+time_. We strongly recommend that you do not use these features in a production
+environment. They are intended for testing and feedback only.
+
+:::
+
+:::warning
+
+This experiment breaks the following functionality:
+
+- \{list any existing functionality that will be broken by this experiment\}
+- \{if there are no breaking changes, remove this admonition\}
+
+:::
+
+:::info
+
+To enable this experiment, set the environment variable: `TASK_X_{feature}=1`.
+Check out [our guide to enabling experiments ][enabling-experiments] for more
+information.
+
+:::
+
+\{Short description of the feature\}
+
+\{Short explanation of how users should migrate to the new behavior\}
+
+<!-- prettier-ignore-start -->
+[enabling-experiments]: /experiments/#enabling-experiments
+<!-- prettier-ignore-end -->

docs/docs/experiments/workflow.md

@@ -1,84 +0,0 @@
----
-slug: /experiments/workflow/
----
-
-# Workflow
-
-Experiments are a way for us to test out new features in Task before committing
-to them in a major release. Because this concept is built around the idea of
-feedback from our community, we have built a workflow for the process of
-introducing these changes. This ensures that experiments are given the attention
-and time that they need and that we are getting the best possible results out of
-them.
-
-The sections below describe the various stages that an experiment must go
-through from its proposal all the way to being released in a major version of
-Task.
-
-## 1. Proposal
-
-All experimental features start with a proposal in the form of a GitHub issue.
-If the maintainers decide that an issue has enough support and is a breaking
-change or is complex/controversial enough to require user feedback, then the
-issue will be marked with the ![proposal] label. At this point, the issue
-becomes a proposal and a period of consultation begins. During this period, we
-request that users provide feedback on the proposal and how it might effect
-their use of Task. It is up to the discretion of the maintainers to decide how
-long this period lasts.
-
-## 2. Draft
-
-Once a proposal's consultation ends, a contributor may pick up the work and
-begin the initial implementation. Once a PR is opened, the maintainers will
-ensure that it meets the requirements for an experimental feature (i.e. flags
-are in the right format etc) and merge the feature. Once this code is released,
-the status will be updated via the ![draft] label. This indicates that an
-implementation is now available for use in a release and the experiment is open
-for feedback.
-
-:::note
-
-During the draft period, major changes to the implementation may be made based
-on the feedback received from users. There are _no stability guarantees_ and
-experimental features may be abandoned _at any time_.
-
-:::
-
-## 3. Candidate
-
-Once an acceptable level of consensus has been reached by the community and
-feedback/changes are less frequent/significant, the status may be updated via
-the ![candidate] label. This indicates that a proposal is _likely_ to accepted
-and will enter a period for final comments and minor changes.
-
-## 4. Stable
-
-Once a suitable amount of time has passed with no changes or feedback, an
-experiment will be given the ![stable] label. At this point, the functionality
-will be treated like any other feature in Task and any changes _must_ be
-backward compatible. This allows users to migrate to the new functionality
-without having to worry about anything breaking in future releases. This
-provides the best experience for users migrating to a new major version.
-
-## 5. Released
-
-When making a new major release of Task, all experiments marked as ![stable]
-will move to ![released] and their behaviors will become the new default in
-Task. Experiments in an earlier stage (i.e. not stable) cannot be released and
-so will continue to be experiments in the new version.
-
-## Abandoned / Superseded
-
-If an experiment is unsuccessful at any point then it will be given the
-![abandoned] or ![superseded] labels depending on which is more suitable. These
-experiments will be removed from Task.
-
-<!-- prettier-ignore-start -->
-[proposal]: https://img.shields.io/badge/experiment:%20proposal-purple
-[draft]: https://img.shields.io/badge/experiment:%20draft-purple
-[candidate]: https://img.shields.io/badge/experiment:%20candidate-purple
-[stable]: https://img.shields.io/badge/experiment:%20stable-purple
-[released]: https://img.shields.io/badge/experiment:%20released-purple
-[abandoned]: https://img.shields.io/badge/experiment:%20abandoned-purple
-[superseded]: https://img.shields.io/badge/experiment:%20superseded-purple
-<!-- prettier-ignore-end -->

docs/docs/faq.md

@@ -1,6 +1,6 @@
 ---
 slug: /faq/
-sidebar_position: 7
+sidebar_position: 15
 ---
 
 # FAQ
@@ -69,7 +69,7 @@ tasks:
       - ./foo-printer.bash
 ```
 
-```bash
+```shell
 #!/bin/bash
 a=foo
 echo $a
@@ -91,7 +91,7 @@ around this limitation using one of the following methods:
 We want to make improvements to this part of Task and the issues below track
 this work. Constructive comments and contributions are very welcome!
 
-- [#197](https://github.com/go-task/task/issues/197)
+- #197
 - [mvdan/sh#93](https://github.com/mvdan/sh/issues/93)
 - [mvdan/sh#97](https://github.com/mvdan/sh/issues/97)
 

docs/docs/installation.md

@@ -14,35 +14,36 @@ Task offers many installation methods. Check out the available methods below.
 If you're on macOS or Linux and have [Homebrew][homebrew] installed, getting
 Task is as simple as running:
 
-```bash
+```shell
 brew install go-task/tap/go-task
 ```
 
 The above Formula is
-[maintained by ourselves](https://github.com/go-task/homebrew-tap/blob/master/Formula/go-task.rb).
+[maintained by ourselves](https://github.com/go-task/homebrew-tap/blob/main/Formula/go-task.rb).
 
 Recently, Task was also made available
 [on the official Homebrew repository](https://formulae.brew.sh/formula/go-task),
 so you also have that option if you prefer:
 
-```bash
+```shell
 brew install go-task
 ```
 
 ### Tea
 
-If you're on macOS or Linux and have [tea][tea] installed, getting
-Task is as simple as running:
+If you're on macOS or Linux and have [tea][tea] installed, getting Task is as
+simple as running:
 
-```bash
+```shell
 tea task
 ```
 
 or, if you have tea’s magic enabled:
 
-```bash
+```shell
 task
 ```
+
 This installation method is community owned. After a new release of Task, they
 are automatically released by tea in a minimum of time.
 
@@ -51,7 +52,7 @@ are automatically released by tea in a minimum of time.
 Task is available in [Snapcraft][snapcraft], but keep in mind that your Linux
 distribution should allow classic confinement for Snaps to Task work right:
 
-```bash
+```shell
 sudo snap install task --classic
 ```
 
@@ -60,7 +61,7 @@ sudo snap install task --classic
 If you're on Windows and have [Chocolatey][choco] installed, getting Task is as
 simple as running:
 
-```bash
+```shell
 choco install go-task
 ```
 
@@ -71,7 +72,7 @@ This installation method is community owned.
 If you're on Windows and have [Scoop][scoop] installed, getting Task is as
 simple as running:
 
-```cmd
+```shell
 scoop install task
 ```
 
@@ -84,7 +85,7 @@ If you're on Arch Linux you can install Task from
 [AUR](https://aur.archlinux.org/packages/go-task-bin) using your favorite
 package manager such as `yay`, `pacaur` or `yaourt`:
 
-```cmd
+```shell
 yay -S go-task-bin
 ```
 
@@ -93,7 +94,7 @@ Alternatively, there's
 the source code instead of downloading the binary from the
 [releases page](https://github.com/go-task/task/releases):
 
-```cmd
+```shell
 yay -S go-task
 ```
 
@@ -105,7 +106,7 @@ If you're on Fedora Linux you can install Task from the official
 [Fedora](https://packages.fedoraproject.org/pkgs/golang-github-task/go-task/)
 repository using `dnf`:
 
-```cmd
+```shell
 sudo dnf install go-task
 ```
 
@@ -118,7 +119,7 @@ take some time until it's available in
 If you're on NixOS or have Nix installed you can install Task from
 [nixpkgs](https://github.com/NixOS/nixpkgs):
 
-```cmd
+```shell
 nix-env -iA nixpkgs.go-task
 ```
 
@@ -131,7 +132,7 @@ take some time until it's available in
 You can also use Node and npm to install Task by installing
 [this package](https://www.npmjs.com/package/@go-task/cli).
 
-```bash
+```shell
 npm install -g @go-task/cli
 ```
 
@@ -141,7 +142,7 @@ If you are using Windows and installed the
 [winget](https://github.com/microsoft/winget-cli) package management tool, you
 can install Task from [winget-pkgs](https://github.com/microsoft/winget-pkgs).
 
-```bash
+```shell
 winget install Task.Task
 ```
 
@@ -165,7 +166,7 @@ easy generation of this script.
 By default, it installs on the `./bin` directory relative to the working
 directory:
 
-```bash
+```shell
 sh -c "$(curl --location https://taskfile.dev/install.sh)" -- -d
 ```
 
@@ -173,7 +174,7 @@ It is possible to override the installation directory with the `-b` parameter.
 On Linux, common choices are `~/.local/bin` and `~/bin` to install for the
 current user or `/usr/local/bin` to install for all users:
 
-```bash
+```shell
 sh -c "$(curl --location https://taskfile.dev/install.sh)" -- -d -b ~/.local/bin
 ```
 
@@ -209,13 +210,13 @@ setup. You can find the minimum required version of Go in the
 
 You can then install the latest release globally by running:
 
-```bash
+```shell
 go install github.com/go-task/task/v3/cmd/task@latest
 ```
 
 Or you can install into another directory:
 
-```bash
+```shell
 env GOBIN=/bin go install github.com/go-task/task/v3/cmd/task@latest
 ```
 
@@ -239,7 +240,7 @@ First, ensure that you installed bash-completion using your package manager.
 
 Make the completion file executable:
 
-```
+```shell
 chmod +x path/to/task.bash
 ```
 
@@ -278,7 +279,7 @@ mv path/to/task.fish ~/.config/fish/completions/task.fish
 
 Open your profile script with:
 
-```
+```powershell
 mkdir -Path (Split-Path -Parent $profile) -ErrorAction SilentlyContinue
 notepad $profile
 ```

docs/docs/integrations.md

@@ -1,6 +1,6 @@
 ---
 slug: /integrations/
-sidebar_position: 6
+sidebar_position: 8
 ---
 
 # Integrations
@@ -29,7 +29,7 @@ To get autocompletion and validation for your Taskfile, see the
 
 ## Schema
 
-This was initially created by [@KROSF](https://github.com/KROSF) in
+This was initially created by @KROSF in
 [this Gist](https://gist.github.com/KROSF/c5435acf590acd632f71bb720f685895) and
 is now officially maintained in
 [this file](https://github.com/go-task/task/blob/main/docs/static/schema.json)
@@ -74,11 +74,9 @@ In addition to our official integrations, there is an amazing community of
 developers who have created their own integrations for Task:
 
 - [Sublime Text Plugin](https://packagecontrol.io/packages/Taskfile)
-  [[source](https://github.com/biozz/sublime-taskfile)] by
-  [@biozz](https://github.com/biozz)
+  [[source](https://github.com/biozz/sublime-taskfile)] by @biozz
 - [IntelliJ Plugin](https://plugins.jetbrains.com/plugin/17058-taskfile)
-  [[source](https://github.com/lechuckroh/task-intellij-plugin)] by
-  [@lechuckroh](https://github.com/lechuckroh)
+  [[source](https://github.com/lechuckroh/task-intellij-plugin)] by @lechuckroh
 - [mk](https://github.com/pycontribs/mk) command line tool recognizes Taskfiles
   natively.
 

docs/docs/intro.md

@@ -17,7 +17,7 @@ Since it's written in [Go][go], Task is just a single binary and has no other
 dependencies, which means you don't need to mess with any complicated install
 setups just to use a build tool.
 
-Once [installed](installation.md), you just need to describe your build tasks
+Once [installed](/installation), you just need to describe your build tasks
 using a simple [YAML][yaml] schema in a file called `Taskfile.yml`:
 
 ```yaml title="Taskfile.yml"
@@ -37,11 +37,11 @@ guide to check the full schema documentation and Task features.
 
 ## Features
 
-- [Easy installation](installation.md): just download a single binary, add to
+- [Easy installation](/installation): just download a single binary, add to
   `$PATH` and you're done! Or you can also install using [Homebrew][homebrew],
   [Snapcraft][snapcraft], or [Scoop][scoop] if you want.
 - Available on CIs: by adding
-  [this simple command](installation.md#install-script) to install on your CI
+  [this simple command](/installation#install-script) to install on your CI
   script and you're ready to use Task as part of your CI pipeline;
 - Truly cross-platform: while most build tools only work well on Linux or macOS,
   Task also supports Windows thanks to [this shell interpreter for Go][sh].
@@ -50,16 +50,6 @@ guide to check the full schema documentation and Task features.
   of files haven't changed since last run (based either on its timestamp or
   content).
 
-## Gold Sponsors
-
-<div class="gold-sponsors">
-
-| [Appwrite](https://appwrite.io/?utm_source=taskfile.dev&utm_medium=website&utm_campaign=task_oss_fund)                       |
-| ---------------------------------------------------------------------------------------------------------------------------- |
-| [![Appwrite](/img/appwrite.svg)](https://appwrite.io/?utm_source=taskfile.dev&utm_medium=website&utm_campaign=task_oss_fund) |
-
-</div>
-
 <!-- prettier-ignore-start -->
 [make]: https://www.gnu.org/software/make/
 [go]: https://go.dev/

docs/docs/releasing.md

@@ -37,6 +37,15 @@ version:
 - Moving both `amd64`, `armhf` and `arm64` new artifacts to the stable channel
   on the [Snapcraft dashboard][snapcraftdashboard].
 
+# winget
+
+winget also requires manual steps to be completed. By running
+`task goreleaser:test` locally, manifest files will be generated on
+`dist/winget/manifests/t/Task/Task/v{version}`.
+[Upload the manifest directory into this fork](https://github.com/go-task/winget-pkgs/tree/master/manifests/t/Task/Task)
+and open a pull request into
+[this repository](https://github.com/microsoft/winget-pkgs).
+
 # Scoop
 
 Scoop is a command-line package manager for the Windows operating system. Scoop
@@ -55,9 +64,9 @@ If you think its Task version is outdated, open an issue to let us know.
 <!-- prettier-ignore-start -->
 [goreleaser]: https://goreleaser.com/
 [homebrewtap]: https://github.com/go-task/homebrew-tap
-[gotaskrb]: https://github.com/go-task/homebrew-tap/blob/master/Formula/go-task.rb
+[gotaskrb]: https://github.com/go-task/homebrew-tap/blob/main/Formula/go-task.rb
 [packagejson]: https://github.com/go-task/task/blob/main/package.json#L3
 [snappackage]: https://github.com/go-task/snap
-[snapcraftyaml]: https://github.com/go-task/snap/blob/master/snap/snapcraft.yaml#L2
+[snapcraftyaml]: https://github.com/go-task/snap/blob/main/snap/snapcraft.yaml#L2
 [snapcraftdashboard]: https://snapcraft.io/task/releases
 <!-- prettier-ignore-end -->

docs/docs/styleguide.md

@@ -1,44 +1,30 @@
 ---
 slug: /styleguide/
-sidebar_position: 8
+sidebar_position: 10
 ---
 
-# Styleguide
+# Style guide
 
-This is the official Task styleguide for `Taskfile.yml` files. This guide
-contains some basic instructions to keep your Taskfile clean and familiar to
-other users.
+This is the official style guide for `Taskfile.yml` files. It provides basic
+instructions for keeping your Taskfiles clean and familiar to other users.
 
-This contains general guidelines, but they don't necessarily need to be strictly
-followed. Feel free to disagree and proceed differently at some point if you
-need or want to. Also, feel free to open issues or pull requests with
-improvements to this guide.
+This guide contains general guidelines, but they do not necessarily need to be
+followed strictly. Feel free to disagree and do things differently if you need
+or want to. Any improvements to this guide are welcome! Please open an issue or
+create a pull request to contribute.
 
-## Use `Taskfile.yml` and not `taskfile.yml`
+## Use the suggested ordering of the main sections
 
 ```yaml
-# bad
-taskfile.yml
-
-
-# good
-Taskfile.yml
+version:
+includes:
+# optional configurations (output, silent, method, run, etc.)
+vars:
+env: # followed or replaced by dotenv
+tasks:
 ```
 
-This is important especially for Linux users. Windows and macOS have case
-insensitive filesystems, so `taskfile.yml` will end up working, even that not
-officially supported. On Linux, only `Taskfile.yml` will work, though.
-
-## Use the correct order of keywords
-
-- `version:`
-- `includes:`
-- Configuration ones, like `output:`, `silent:`, `method:` and `run:`
-- `vars:`
-- `env:`, `dotenv:`
-- `tasks:`
-
-## Use 2 spaces for indentation
+## Use two spaces for indentation
 
 This is the most common convention for YAML files, and Task follows it.
 
@@ -57,7 +43,7 @@ tasks:
       - echo 'foo'
 ```
 
-## Separate with spaces the mains sections
+## Separate the main sections with empty lines
 
 ```yaml
 # bad
@@ -91,7 +77,7 @@ tasks:
   # ...
 ```
 
-## Add spaces between tasks
+## Separate tasks with empty lines
 
 ```yaml
 # bad
@@ -126,7 +112,7 @@ tasks:
       - echo 'baz'
 ```
 
-## Use upper-case variable names
+## Use only uppercase letters for variable names
 
 ```yaml
 # bad
@@ -153,7 +139,7 @@ tasks:
       - go build -o {{.BINARY_NAME}} .
 ```
 
-## Don't wrap vars in spaces when templating
+## Avoid using whitespace when templating variables
 
 ```yaml
 # bad
@@ -174,9 +160,10 @@ tasks:
       - echo '{{.MESSAGE}}'
 ```
 
-This convention is also used by most people for any Go templating.
+This convention is also commonly used in templates for the Go programming
+language.
 
-## Separate task name words with a dash
+## Use kebab case for task names
 
 ```yaml
 # bad
@@ -197,7 +184,7 @@ tasks:
       - echo 'Do something'
 ```
 
-## Use colon for task namespacing
+## Use a colon to separate the task namespace and name
 
 ```yaml
 # good
@@ -215,7 +202,7 @@ tasks:
 
 This is also done automatically when using included Taskfiles.
 
-## Prefer external scripts over complex multi-line commands
+## Prefer using external scripts instead of multi-line commands
 
 ```yaml
 # bad

docs/docs/taskfile_versions.md

@@ -1,6 +1,6 @@
 ---
 slug: /taskfile-versions/
-sidebar_position: 14
+sidebar_position: 5
 ---
 
 # Taskfile Versions
@@ -29,7 +29,7 @@ These are some major changes done on `v3`:
 - A global `method:` was added to allow setting the default method, and Task's
   default changed to `checksum`
 - Two magic variables were added when using `status:`: `CHECKSUM` and
-  `TIMESTAMP` which contains, respectively, the md5 checksum and greatest
+  `TIMESTAMP` which contains, respectively, the XXH3 checksum and greatest
   modification timestamp of the files listed on `sources:`
 - Also, the `TASK` variable is always available with the current task name
 - CLI variables are always treated as global variables
@@ -82,8 +82,8 @@ tasks:
 
 :::caution
 
-v2 schema support is [deprecated][deprecate-version-2-schema] and will be
-removed in a future release.
+v2 schemas are [no longer supported by the latest version of
+Task][deprecate-version-2-schema].
 
 :::
 
@@ -102,16 +102,12 @@ tasks:
 
 Please check the [documentation][includes]
 
-[output]: usage.md#output-syntax
-[ignore_errors]: usage.md#ignore-errors
-[includes]: usage.md#including-other-taskfiles
-
 ## Version 2.2
 
 :::caution
 
-v2 schema support is [deprecated][deprecate-version-2-schema] and will be
-removed in a future release.
+v2 schemas are [no longer supported by the latest version of
+Task][deprecate-version-2-schema].
 
 :::
 
@@ -129,8 +125,8 @@ includes:
 
 :::caution
 
-v2 schema support is [deprecated][deprecate-version-2-schema] and will be
-removed in a future release.
+v2 schemas are [no longer supported by the latest version of
+Task][deprecate-version-2-schema].
 
 :::
 
@@ -174,8 +170,8 @@ tasks:
 
 :::caution
 
-v2 schema support is [deprecated][deprecate-version-2-schema] and will be
-removed in a future release.
+v2 schemas are [no longer supported by the latest version of
+Task][deprecate-version-2-schema].
 
 :::
 
@@ -260,5 +256,8 @@ The variable priority order was also different:
 4. `Taskvars.yml` variables
 
 <!-- prettier-ignore-start -->
-[deprecate-version-2-schema]: https://github.com/go-task/task/issues/1197
+[deprecate-version-2-schema]: /deprecations/version-2-schema/
+[output]: /usage#output-syntax
+[ignore_errors]: /usage#ignore-errors
+[includes]: /usage#including-other-taskfiles
 <!-- prettier-ignore-end -->

docs/docs/usage.md

@@ -27,7 +27,7 @@ tasks:
 
 Running the tasks is as simple as running:
 
-```bash
+```shell
 task assets build
 ```
 
@@ -118,6 +118,18 @@ tasks:
 
 :::
 
+### Reading a Taskfile from stdin
+
+Taskfile also supports reading from stdin. This is useful if you are generating
+Taskfiles dynamically and don't want write them to disk. This works just like
+any other program that supports stdin. For example:
+
+```shell
+task < <(cat ./Taskfile.yml)
+# OR
+cat ./Taskfile.yml | task
+```
+
 ## Environment variables
 
 ### Task
@@ -162,11 +174,11 @@ variables, as you can see in the [Variables](#variables) section.
 You can also ask Task to include `.env` like files by using the `dotenv:`
 setting:
 
-```bash title=".env"
+```shell title=".env"
 KEYNAME=VALUE
 ```
 
-```bash title="testing/.env"
+```shell title="testing/.env"
 ENDPOINT=testing.com
 ```
 
@@ -642,11 +654,27 @@ tasks:
       - public/bundle.css
 ```
 
-`sources` and `generates` can be files or file patterns. When given, Task will
+`sources` and `generates` can be files or glob patterns. When given, Task will
 compare the checksum of the source files to determine if it's necessary to run
 the task. If not, it will just print a message like `Task "js" is up to date`.
 
-If you prefer this check to be made by the modification timestamp of the files,
+`exclude:` can also be used to exclude files from fingerprinting. Sources are
+evaluated in order, so `exclude:` must come after the positive glob it is
+negating.
+
+```yaml
+version: '3'
+
+tasks:
+  css:
+    sources:
+      - mysources/**/*.css
+      - exclude: mysources/ignoreme.css
+    generates:
+      - public/bundle.css
+```
+
+If you prefer these check to be made by the modification timestamp of the files,
 instead of its checksum (content), just set the `method` property to
 `timestamp`.
 
@@ -683,7 +711,7 @@ path like `tmp/task` that will be interpreted as relative to the project
 directory, or an absolute or home path like `/tmp/.task` or `~/.task`
 (subdirectories will be created for each project).
 
-```bash
+```shell
 export TASK_TEMP_DIR='~/.task'
 ```
 
@@ -934,7 +962,7 @@ listed below in order of importance (i.e. most important first):
 
 Example of sending parameters with environment variables:
 
-```bash
+```shell
 $ TASK_VARIABLE=a-value task do-something
 ```
 
@@ -948,7 +976,7 @@ Since some shells do not support the above syntax to set environment variables
 (Windows) tasks also accept a similar style when not at the beginning of the
 command.
 
-```bash
+```shell
 $ task write-file FILE=file.txt "CONTENT=Hello, World!" print "MESSAGE=All done!"
 ```
 
@@ -1001,9 +1029,9 @@ This works for all types of variables.
 
 ## Looping over values
 
-Task allows you to loop over certain values and execute a command for each.
-There are a number of ways to do this depending on the type of value you want to
-loop over.
+As of v3.28.0, Task allows you to loop over certain values and execute a command
+for each. There are a number of ways to do this depending on the type of value
+you want to loop over.
 
 ### Looping over a static list
 
@@ -1043,9 +1071,8 @@ match that glob.
 
 Source paths will always be returned as paths relative to the task directory. If
 you need to convert this to an absolute path, you can use the built-in
-`joinPath` function.
-There are some [special variables](/api/#special-variables) that you may find
-useful for this.
+`joinPath` function. There are some [special variables](/api/#special-variables)
+that you may find useful for this.
 
 ```yaml
 version: '3'
@@ -1177,7 +1204,7 @@ If `--` is given in the CLI, all following parameters are added to a special
 
 The below example will run `yarn install`.
 
-```bash
+```shell
 $ task yarn -- install
 ```
 
@@ -1190,6 +1217,53 @@ tasks:
       - yarn {{.CLI_ARGS}}
 ```
 
+## Wildcard arguments
+
+Another way to parse arguments into a task is to use a wildcard in your task's
+name. Wildcards are denoted by an asterisk (`*`) and can be used multiple times
+in a task's name to pass in multiple arguments.
+
+Matching arguments will be captured and stored in the `.MATCH` variable and can
+then be used in your task's commands like any other variable. This variable is
+an array of strings and so will need to be indexed to access the individual
+arguments. We suggest creating a named variable for each argument to make it
+clear what they contain:
+
+```yaml
+version: '3'
+
+tasks:
+  echo-*:
+    vars:
+      TEXT: '{{index .MATCH 0}}'
+    cmds:
+      - echo {{.TEXT}}
+
+  run-*-*:
+    vars:
+      ARG_1: '{{index .MATCH 0}}'
+      ARG_2: '{{index .MATCH 1}}'
+    cmds:
+      - echo {{.ARG_1}} {{.ARG_2}}
+```
+
+```shell
+# This call matches the "echo-*" task and the string "hello" is captured by the
+# wildcard and stored in the .MATCH variable. We then index the .MATCH array and
+# store the result in the .TEXT variable which is then echoed out in the cmds.
+$ task echo-hello
+hello
+# You can use whitespace in your arguments as long as you quote the task name
+$ task "echo-hello world"
+hello world
+# And you can pass multiple arguments
+$ task run-foo-bar
+foo bar
+```
+
+If multiple matching tasks are found, an error occurs. If you are using included
+Taskfiles, tasks in parent files will be considered first.
+
 ## Doing task cleanup with `defer`
 
 With the `defer` keyword, it's possible to schedule cleanup to be run once the
@@ -1271,6 +1345,17 @@ Task also adds the following functions:
   for this. The Bash dialect is assumed.
 - `splitArgs`: Splits a string as if it were a command's arguments. Task uses
   [this Go function](https://pkg.go.dev/mvdan.cc/sh/v3@v3.4.0/shell#Fields)
+- `joinPath`: Joins any number of arguments into a path. The same as Go's
+  [filepath.Join](https://pkg.go.dev/path/filepath#Join).
+- `relPath`: Converts an absolute path (second argument) into a relative path,
+  based on a base path (first argument). The same as Go's
+  [filepath.Rel](https://pkg.go.dev/path/filepath#Rel).
+- `merge`: Creates a new map that is a copy of the first map with the keys of
+  each subsequent map merged into it. If there is a duplicate key, the value of
+  the last map with that key is used.
+- `spew`: Returns the Go representation of a specific variable. Useful for
+  debugging. Uses the [davecgh/go-spew](https://github.com/davecgh/go-spew)
+  package.
 
 Example:
 
@@ -1327,7 +1412,7 @@ tasks:
 
 would print the following output:
 
-```bash
+```shell
 * build:   Build the go binary.
 * test:    Run all the go tests.
 ```
@@ -1460,16 +1545,16 @@ tasks:
       - echo 'dangerous command'
 ```
 
-```bash
+```shell
 ❯ task dangerous
 task: "This is a dangerous command... Do you want to continue?" [y/N]
 ```
 
 Warning prompts are called before executing a task. If a prompt is denied Task
-will exit with [exit code](api_reference.md#exit-codes) 205. If approved, Task
-will continue as normal.
+will exit with [exit code](/api#exit-codes) 205. If approved, Task will continue
+as normal.
 
-```bash
+```shell
 ❯ task example
 not dangerous command
 task: "This is a dangerous command. Do you want to continue?" [y/N]
@@ -1506,14 +1591,14 @@ tasks:
 
 Normally this will be printed:
 
-```sh
+```shell
 echo "Print something"
 Print something
 ```
 
 With silent mode on, the below will be printed instead:
 
-```sh
+```shell
 Print something
 ```
 
@@ -1660,7 +1745,7 @@ tasks:
     silent: true
 ```
 
-```bash
+```shell
 $ task default
 ::group::default
 Hello, World!
@@ -1685,7 +1770,7 @@ tasks:
   errors: echo 'output-of-errors' && exit 1
 ```
 
-```bash
+```shell
 $ task passes
 $ task errors
 output-of-errors
@@ -1718,7 +1803,7 @@ tasks:
     silent: true
 ```
 
-```bash
+```shell
 $ task default
 [print-foo] foo
 [print-bar] bar
@@ -1803,8 +1888,34 @@ task again. This requires the `sources` attribute to be given, so task knows
 which files to watch.
 
 The default watch interval is 5 seconds, but it's possible to change it by
-either setting `interval: '500ms'` in the root of the Taskfile passing it as an
-argument like `--interval=500ms`.
+either setting `interval: '500ms'` in the root of the Taskfile or by passing it
+as an argument like `--interval=500ms`.
+
+Also, it's possible to set `watch: true` in a given task and it'll automatically
+run in watch mode:
+
+```yaml
+version: '3'
+
+interval: 500ms
+
+tasks:
+  build:
+    desc: Builds the Go application
+    watch: true
+    sources:
+      - '**/*.go'
+    cmds:
+      - go build # ...
+```
+
+:::info
+
+Note that when setting `watch: true` to a task, it'll only run in watch mode
+when running from the CLI via `task my-watch-task`, but won't run in watch mode
+if called by another task, either directly or as a dependency.
+
+:::
 
 <!-- prettier-ignore-start -->
 [gotemplate]: https://golang.org/pkg/text/template/

docs/docusaurus.config.js

@@ -1,258 +0,0 @@
-// @ts-check
-// Note: type annotations allow type checking and IDEs autocompletion
-
-const {
-  DISCORD_URL,
-  GITHUB_URL,
-  MASTODON_URL,
-  TWITTER_URL
-} = require('./constants');
-const lightCodeTheme = require('./src/themes/prismLight');
-const darkCodeTheme = require('./src/themes/prismDark');
-
-const { getTranslationProgress } = require('./src/api/crowdin.js');
-
-const getConfig = async () => {
-  const translationProgress = await getTranslationProgress();
-
-  /** @type {import('@docusaurus/types').Config} */
-  const config = {
-    title: 'Task',
-    tagline: 'A task runner / simpler Make alternative written in Go ',
-    url: 'https://taskfile.dev',
-    baseUrl: '/',
-    onBrokenLinks: 'throw',
-    onBrokenMarkdownLinks: 'throw',
-    favicon: 'img/favicon.ico',
-
-    organizationName: 'go-task',
-    projectName: 'task',
-    deploymentBranch: 'gh-pages',
-
-    i18n: {
-      defaultLocale: 'en',
-      locales: [
-        'en',
-        'es-ES',
-        'fr-FR',
-        'ja-JP',
-        'pt-BR',
-        'ru-RU',
-        'tr-TR',
-        'zh-Hans'
-      ],
-      localeConfigs: {
-        en: {
-          label: 'English',
-          direction: 'ltr',
-          htmlLang: 'en-US'
-        },
-        'es-ES': {
-          label: `Español (${translationProgress['es-ES'] || 0}%)`,
-          direction: 'ltr',
-          htmlLang: 'es-ES'
-        },
-        'fr-FR': {
-          label: `Français (${translationProgress['fr'] || 0}%)`,
-          direction: 'ltr',
-          htmlLang: 'fr-FR'
-        },
-        'ja-JP': {
-          label: `日本語 (${translationProgress['ja'] || 0}%)`,
-          direction: 'ltr',
-          htmlLang: 'ja-JP'
-        },
-        'pt-BR': {
-          label: `Português (${translationProgress['pt-BR'] || 0}%)`,
-          direction: 'ltr',
-          htmlLang: 'pt-BR'
-        },
-        'ru-RU': {
-          label: `Pусский (${translationProgress['ru'] || 0}%)`,
-          direction: 'ltr',
-          htmlLang: 'ru-RU'
-        },
-        'tr-TR': {
-          label: `Türkçe (${translationProgress['tr'] || 0}%)`,
-          direction: 'ltr',
-          htmlLang: 'tr-TR'
-        },
-        'zh-Hans': {
-          label: `简体中文 (${translationProgress['zh-CN'] || 0}%)`,
-          direction: 'ltr',
-          htmlLang: 'zh-Hans'
-        }
-      }
-    },
-
-    presets: [
-      [
-        'classic',
-        /** @type {import('@docusaurus/preset-classic').Options} */
-        ({
-          docs: {
-            routeBasePath: '/',
-            sidebarPath: require.resolve('./sidebars.js')
-          },
-          blog: false,
-          theme: {
-            customCss: [require.resolve('./src/css/custom.css')]
-          },
-          gtag: {
-            trackingID: 'G-4RT25NXQ7N',
-            anonymizeIP: true
-          },
-          sitemap: {
-            changefreq: 'weekly',
-            priority: 0.5,
-            ignorePatterns: ['/tags/**']
-          }
-        })
-      ]
-    ],
-
-    themeConfig:
-      /** @type {import('@docusaurus/preset-classic').ThemeConfig} */
-      ({
-        metadata: [
-          {
-            name: 'og:image',
-            content: 'https://taskfile.dev/img/og-image.png'
-          }
-        ],
-        navbar: {
-          title: 'Task',
-          logo: {
-            alt: 'Task Logo',
-            src: 'img/logo.svg'
-          },
-          items: [
-            {
-              type: 'doc',
-              docId: 'installation',
-              position: 'left',
-              label: 'Installation'
-            },
-            {
-              type: 'doc',
-              docId: 'usage',
-              position: 'left',
-              label: 'Usage'
-            },
-            {
-              type: 'doc',
-              docId: 'api_reference',
-              position: 'left',
-              label: 'API'
-            },
-            {
-              type: 'doc',
-              docId: 'donate',
-              position: 'left',
-              label: 'Donate'
-            },
-            {
-              type: 'localeDropdown',
-              position: 'left',
-              dropdownItemsAfter: [
-                {
-                  to: '/translate/',
-                  label: 'Help Us Translate'
-                }
-              ]
-            },
-            {
-              href: GITHUB_URL,
-              label: 'GitHub',
-              position: 'right'
-            },
-            {
-              href: TWITTER_URL,
-              label: 'Twitter',
-              position: 'right'
-            },
-            {
-              href: MASTODON_URL,
-              label: 'Mastodon',
-              rel: 'me',
-              position: 'right'
-            },
-            {
-              href: DISCORD_URL,
-              label: 'Discord',
-              position: 'right'
-            }
-          ]
-        },
-        footer: {
-          style: 'dark',
-          links: [
-            {
-              title: 'Pages',
-              items: [
-                {
-                  label: 'Installation',
-                  to: '/installation/'
-                },
-                {
-                  label: 'Usage',
-                  to: '/usage/'
-                },
-                {
-                  label: 'Donate',
-                  to: '/donate/'
-                }
-              ]
-            },
-            {
-              title: 'Community',
-              items: [
-                {
-                  label: 'GitHub',
-                  href: GITHUB_URL
-                },
-                {
-                  label: 'Twitter',
-                  href: TWITTER_URL
-                },
-                {
-                  label: 'Mastodon',
-                  href: MASTODON_URL,
-                  rel: 'me'
-                },
-                {
-                  label: 'Discord',
-                  href: DISCORD_URL
-                },
-                {
-                  label: 'OpenCollective',
-                  href: 'https://opencollective.com/task'
-                }
-              ]
-            },
-            {
-              items: [
-                {
-                  html: '<a target="_blank" href="https://www.netlify.com"><img src="https://www.netlify.com/v3/img/components/netlify-color-accent.svg" alt="Deploys by Netlify" /></a>'
-                }
-              ]
-            }
-          ]
-        },
-        prism: {
-          theme: lightCodeTheme,
-          darkTheme: darkCodeTheme
-        },
-        // NOTE(@andreynering): Don't worry, these keys are meant to be public =)
-        algolia: {
-          appId: '7IZIJ13AI7',
-          apiKey: '34b64ae4fc8d9da43d9a13d9710aaddc',
-          indexName: 'taskfile'
-        }
-      })
-  };
-
-  return config;
-};
-
-module.exports = getConfig;

docs/docusaurus.config.ts

@@ -0,0 +1,273 @@
+import type {Config} from '@docusaurus/types';
+import type * as Preset from '@docusaurus/preset-classic';
+import { EnumChangefreq } from 'sitemap';
+
+import remarkGithub from 'remark-github';
+import remarkGfm from 'remark-gfm';
+
+import { DISCORD_URL } from './constants';
+import { GITHUB_URL } from './constants';
+import { MASTODON_URL } from './constants';
+import { TWITTER_URL } from './constants';
+
+import lightCodeTheme from './src/themes/prismLight';
+import darkCodeTheme from './src/themes/prismDark';
+
+import { getTranslationProgress } from './src/api/crowdin.js';
+const translationProgress = getTranslationProgress();
+
+const config: Config = {
+  title: 'Task',
+  tagline: 'A task runner / simpler Make alternative written in Go ',
+  url: 'https://taskfile.dev',
+  baseUrl: '/',
+  onBrokenLinks: 'throw',
+  onBrokenMarkdownLinks: 'throw',
+  favicon: 'img/favicon.ico',
+
+  organizationName: 'go-task',
+  projectName: 'task',
+  deploymentBranch: 'gh-pages',
+
+  i18n: {
+    defaultLocale: 'en',
+    locales: [
+      'en',
+      'es-ES',
+      'fr-FR',
+      'ja-JP',
+      'pt-BR',
+      'ru-RU',
+      'tr-TR',
+      'zh-Hans'
+    ],
+    localeConfigs: {
+      en: {
+        label: 'English',
+        direction: 'ltr',
+        htmlLang: 'en-US'
+      },
+      'es-ES': {
+        label: `Español (${translationProgress['es-ES'] || 0}%)`,
+        direction: 'ltr',
+        htmlLang: 'es-ES'
+      },
+      'fr-FR': {
+        label: `Français (${translationProgress['fr'] || 0}%)`,
+        direction: 'ltr',
+        htmlLang: 'fr-FR'
+      },
+      'ja-JP': {
+        label: `日本語 (${translationProgress['ja'] || 0}%)`,
+        direction: 'ltr',
+        htmlLang: 'ja-JP'
+      },
+      'pt-BR': {
+        label: `Português (${translationProgress['pt-BR'] || 0}%)`,
+        direction: 'ltr',
+        htmlLang: 'pt-BR'
+      },
+      'ru-RU': {
+        label: `Pусский (${translationProgress['ru'] || 0}%)`,
+        direction: 'ltr',
+        htmlLang: 'ru-RU'
+      },
+      'tr-TR': {
+        label: `Türkçe (${translationProgress['tr'] || 0}%)`,
+        direction: 'ltr',
+        htmlLang: 'tr-TR'
+      },
+      'zh-Hans': {
+        label: `简体中文 (${translationProgress['zh-CN'] || 0}%)`,
+        direction: 'ltr',
+        htmlLang: 'zh-Hans'
+      }
+    }
+  },
+
+  presets: [
+    [
+      'classic',
+      {
+        docs: {
+          routeBasePath: '/',
+          sidebarPath: './sidebars.ts',
+          remarkPlugins: [remarkGithub, remarkGfm]
+        },
+        blog: {},
+        theme: {
+          customCss: [
+            './src/css/custom.css',
+            './src/css/carbon.css',
+          ]
+        },
+        gtag: {
+          trackingID: 'G-4RT25NXQ7N',
+          anonymizeIP: true
+        },
+        sitemap: {
+          changefreq: EnumChangefreq.WEEKLY,
+          priority: 0.5,
+          ignorePatterns: ['/tags/**']
+        }
+      } satisfies Preset.Options,
+    ]
+  ],
+
+  scripts: [
+    {
+      src: '/js/carbon.js',
+      async: true
+    }
+  ],
+
+  themeConfig:{
+    metadata: [
+      {
+        name: 'og:image',
+        content: 'https://taskfile.dev/img/og-image.png'
+      }
+    ],
+    navbar: {
+      title: 'Task',
+      logo: {
+        alt: 'Task Logo',
+        src: 'img/logo.svg'
+      },
+      items: [
+        {
+          type: 'doc',
+          docId: 'installation',
+          position: 'left',
+          label: 'Installation'
+        },
+        {
+          type: 'doc',
+          docId: 'usage',
+          position: 'left',
+          label: 'Usage'
+        },
+        {
+          type: 'doc',
+          docId: 'api_reference',
+          position: 'left',
+          label: 'API'
+        },
+        {
+          to: 'blog',
+          label: 'Blog',
+          position: 'left'
+        },
+        {
+          type: 'doc',
+          docId: 'donate',
+          position: 'left',
+          label: 'Donate'
+        },
+        {
+          type: 'localeDropdown',
+          position: 'left',
+          dropdownItemsAfter: [
+            {
+              to: '/translate/',
+              label: 'Help Us Translate'
+            }
+          ]
+        },
+        {
+          href: GITHUB_URL,
+          label: 'GitHub',
+          position: 'right'
+        },
+        {
+          href: TWITTER_URL,
+          label: 'Twitter',
+          position: 'right'
+        },
+        {
+          href: MASTODON_URL,
+          label: 'Mastodon',
+          rel: 'me',
+          position: 'right'
+        },
+        {
+          href: DISCORD_URL,
+          label: 'Discord',
+          position: 'right'
+        }
+      ]
+    },
+    footer: {
+      style: 'dark',
+      links: [
+        {
+          title: 'Pages',
+          items: [
+            {
+              label: 'Installation',
+              to: '/installation/'
+            },
+            {
+              label: 'Usage',
+              to: '/usage/'
+            },
+            {
+              label: 'Donate',
+              to: '/donate/'
+            }
+          ]
+        },
+        {
+          title: 'Community',
+          items: [
+            {
+              label: 'GitHub',
+              href: GITHUB_URL
+            },
+            {
+              label: 'Twitter',
+              href: TWITTER_URL
+            },
+            {
+              label: 'Mastodon',
+              href: MASTODON_URL,
+              rel: 'me'
+            },
+            {
+              label: 'Discord',
+              href: DISCORD_URL
+            },
+            {
+              label: 'OpenCollective',
+              href: 'https://opencollective.com/task'
+            }
+          ]
+        },
+        {
+          items: [
+            {
+              html: '<a target="_blank" href="https://www.netlify.com"><img src="https://www.netlify.com/v3/img/components/netlify-color-accent.svg" alt="Deploys by Netlify" /></a>'
+            }
+          ]
+        }
+      ]
+    },
+    prism: {
+      theme: lightCodeTheme,
+      darkTheme: darkCodeTheme,
+      additionalLanguages: [
+        "bash", // aka. shell
+        "json",
+        "powershell"
+      ]
+    },
+    // NOTE(@andreynering): Don't worry, these keys are meant to be public =)
+    algolia: {
+      appId: '7IZIJ13AI7',
+      apiKey: '34b64ae4fc8d9da43d9a13d9710aaddc',
+      indexName: 'taskfile'
+    }
+  } satisfies Preset.ThemeConfig,
+};
+
+export default config;

docs/i18n/es-ES/docusaurus-plugin-content-blog/2023-09-02-introducing-experiments.md

@@ -0,0 +1,93 @@
+---
+title: Introducing Experiments
+description: A look at where task is, where it's going and how we're going to get there.
+slug: task-in-2023
+authors:
+  - pd93
+tags:
+  - experiments
+  - breaking-changes
+  - roadmap
+  - v4
+image: https://i.imgur.com/mErPwqL.png
+hide_table_of_contents: false
+---
+
+Lately, Task has been growing extremely quickly and I've found myself thinking a lot about the future of the project and how we continue to evolve and grow. I'm not much of a writer, but I think one of the things we could do better is to communicate these kinds of thoughts to the community. So, with that in mind, this is the first (hopefully of many) blog posts talking about Task and what we're up to.
+
+<!--truncate-->
+
+## :calendar: So, what have we been up to?
+
+Over the past 12 months or so, [@andreynering][] (Author and maintainer of the project) and I ([@pd93][]) have been working in our spare time to maintain and improve v3 of Task and we've made some amazing progress. Here are just some of the things we've released in that time:
+
+- An official [extension for VS Code][vscode-task].
+- Internal Tasks ([#818](https://github.com/go-task/task/pull/818)).
+- Task aliases ([#879](https://github.com/go-task/task/pull/879)).
+- Looping over tasks ([#1220](https://github.com/go-task/task/pull/1200)).
+- A series of refactors to the core codebase to make it more maintainable and extensible.
+- Loads of bug fixes and improvements.
+- An integration with [Crowdin][crowdin]. Work is in progress on making our docs available in **7 new languages** (Special thanks to all our translators for the huge help with this!).
+- And much, much more! :sparkles:
+
+We're also working on adding some really exciting and highly requested features to Task such as having the ability to run remote Taskfiles ([#1317](https://github.com/go-task/task/issues/1317)).
+
+None of this would have been possible without the [150 or so (and growing) contributors][contributors] to the project, numerous sponsors and a passionate community of users. Together we have more than doubled the number of GitHub stars to over 8400 :star: since the beginning of 2022 and this continues to accelerate. We can't thank you all enough for your help and support! :rocket:
+
+[![Star History Chart](https://api.star-history.com/svg?repos=go-task/task&type=Date)](https://star-history.com/#go-task/task&Date)
+
+## What's next? :thinking:
+
+It's extremely motivating to see so many people using and loving Task. However, in this time we've also seen an increase in the number of issues and feature requests. In particular, issues that require some kind of breaking change to Task. This isn't a bad thing, but as we grow we need to be more responsible about how we address these changes in a way that ensures stability and compatibility for existing users and their Taskfiles.
+
+At this point you're probably thinking something like:
+
+> "But you use [semantic versioning][semver] - Just release a new major version with your breaking changes."
+
+And you'd be right... sort of. In theory, this sounds great, but the reality is that we don't have the time to commit to a major overhaul of Task in one big bang release. This would require a colossal amount of time and coordination and with full time jobs and personal lives to tend to, this is a difficult commitment to make. Smaller, more frequent major releases are also a significant inconvenience for users as they have to constantly keep up-to-date with our breaking changes. Fortunately, there is a better way.
+
+## What's going to change? :monocle:
+
+Going forwards, breaking changes will be allowed into _minor_ versions of Task as "experimental features". To access these features users will need opt-in by enabling feature flags. This will allow us to release new features slowly and gather feedback from the community before making them the default behavior in a future major release.
+
+To prepare users for the next major release, we will maintain a list of [deprecated features][deprecations] and [experiments][experiments] on our docs website and publish information on how to migrate to the new behavior.
+
+You can read the [full breaking change proposal][breaking-change-proposal] and view all the [current experiments and their status][experiments-project] on GitHub including the [Gentle Force][gentle-force-experiment] and [Remote Taskfiles][remote-taskfiles-experiment] experiments.
+
+## What will happen to v2/v3 features?
+
+v2 has been [officially deprecated][deprecate-version-2-schema]. If you're still using a Taskfile with `version: "2"` at the top we _strongly recommend_ that you upgrade as soon as possible. Removing v2 will allow us to tidy up the codebase and focus on new functionality instead.
+
+When v4 is released, we will continue to support v3 for a period of time (bug fixes etc). However, since we are moving from a backward-compatibility model to a forwards-compatibility model, **v4 itself will not be backwards compatible with v3**.
+
+## v4 When? :eyes:
+
+:man_shrugging: When it's ready.
+
+In all seriousness, we don't have a timeline for this yet. We'll be working on the most serious deficiencies of the v3 API first and regularly evaluating the state of the project. When we feel its in a good, stable place and we have a clear upgrade path for users and a number of stable experiments, we'll start to think about v4.
+
+## :wave: Final thoughts
+
+Task is growing fast and we're excited to see where it goes next. We hope that the steps we're taking to improve the project and our process will help us to continue to grow. As always, if you have any questions or feedback, we encourage you to comment on or open [issues][issues] and [discussions][discussions] on GitHub. Alternatively, you can join us on [Discord][discord].
+
+I plan to write more of these blog posts in the future on a variety of Task-related topics, so make sure to check in occasionally and see what we're up to!
+
+<!-- prettier-ignore-start -->
+
+<!-- prettier-ignore-end -->
+[vscode-task]: https://github.com/go-task/vscode-task
+[crowdin]: https://crowdin.com
+[contributors]: https://github.com/go-task/task/graphs/contributors
+[semver]: https://semver.org
+[breaking-change-proposal]: https://github.com/go-task/task/discussions/1191
+[@andreynering]: https://github.com/andreynering
+[@pd93]: https://github.com/pd93
+[experiments]: https://taskfile.dev/experiments
+[deprecations]: https://taskfile.dev/deprecations
+[deprecate-version-2-schema]: https://github.com/go-task/task/issues/1197
+[issues]: https://github.com/go-task/task/issues
+[discussions]: https://github.com/go-task/task/discussions
+[discord]: https://discord.gg/6TY36E39UK
+[experiments-project]: https://github.com/orgs/go-task/projects/1
+[gentle-force-experiment]: https://github.com/go-task/task/issues/1200
+[remote-taskfiles-experiment]: https://github.com/go-task/task/issues/1317

docs/i18n/es-ES/docusaurus-plugin-content-blog/authors.yml

@@ -3,3 +3,8 @@ andreynering:
   title: Maintainer of Task
   url: https://github.com/andreynering
   image_url: https://github.com/andreynering.png
+pd93:
+  name: Pete Davison
+  title: Maintainer of Task
+  url: https://github.com/pd93
+  image_url: https://github.com/pd93.png

docs/i18n/es-ES/docusaurus-plugin-content-docs/current/api_reference.md

@@ -17,7 +17,7 @@ task [--flags] [tasks...] [-- CLI_ARGS...]
 
 :::tip
 
-If `--` is given, all remaning arguments will be assigned to a special `CLI_ARGS` variable
+If `--` is given, all remaining arguments will be assigned to a special `CLI_ARGS` variable
 
 :::
 
@@ -68,6 +68,11 @@ A full list of the exit codes and their descriptions can be found below:
 | 100  | No Taskfile was found                                        |
 | 101  | A Taskfile already exists when trying to initialize one      |
 | 102  | The Taskfile is invalid or cannot be parsed                  |
+| 103  | A remote Taskfile could not be downloaded                    |
+| 104  | A remote Taskfile was not trusted by the user                |
+| 105  | A remote Taskfile was could not be fetched securely          |
+| 106  | No cache was found for a remote Taskfile in offline mode     |
+| 107  | No schema version was defined in the Taskfile                |
 | 200  | The specified task could not be found                        |
 | 201  | An error occurred while executing a command inside of a task |
 | 202  | The user tried to invoke a task that is internal             |
@@ -115,17 +120,19 @@ There are some special variables that is available on the templating system:
 | Var                | Description                                                                                                                                              |
 | ------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------- |
 | `CLI_ARGS`         | Contain all extra arguments passed after `--` when calling Task through the CLI.                                                                         |
+| `CLI_FORCE`        | A boolean containing whether the `--force` or `--force-all` flags were set.                                                                              |
 | `TASK`             | The name of the current task.                                                                                                                            |
 | `ROOT_DIR`         | The absolute path of the root Taskfile.                                                                                                                  |
 | `TASKFILE_DIR`     | The absolute path of the included Taskfile.                                                                                                              |
 | `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 listes in `sources`. Only available within the `status` prop and if method is set to `timestamp`. |
+| `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.                                                                                                                             |
+| `ITEM`             | The value of the current iteration when using the `for` property. Can be changed to a different variable name using `as:`.                               |
 
 ## ENV
 
-Some environment variables can be overriden to adjust Task behavior.
+Some environment variables can be overridden to adjust Task behavior.
 
 | ENV                  | Default | Description                                                                                                       |
 | -------------------- | ------- | ----------------------------------------------------------------------------------------------------------------- |
@@ -145,12 +152,12 @@ Some environment variables can be overriden to adjust Task behavior.
 | ---------- | ---------------------------------- | ------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
 | `version`  | `string`                           |               | Version of the Taskfile. The current version is `3`.                                                                                                                   |
 | `output`   | `string`                           | `interleaved` | Output mode. Available options: `interleaved`, `group` and `prefixed`.                                                                                                 |
-| `method`   | `string`                           | `checksum`    | Default method in this Taskfile. Can be overriden in a task by task basis. Available options: `checksum`, `timestamp` and `none`.                                      |
+| `method`   | `string`                           | `checksum`    | Default method in this Taskfile. Can be overridden in a task by task basis. Available options: `checksum`, `timestamp` and `none`.                                     |
 | `includes` | [`map[string]Include`](#include)   |               | Additional Taskfiles to be included.                                                                                                                                   |
 | `vars`     | [`map[string]Variable`](#variable) |               | A set of global variables.                                                                                                                                             |
 | `env`      | [`map[string]Variable`](#variable) |               | A set of global environment variables.                                                                                                                                 |
 | `tasks`    | [`map[string]Task`](#task)         |               | A set of task definitions.                                                                                                                                             |
-| `silent`   | `bool`                             | `false`       | Default 'silent' options for this Taskfile. If `false`, can be overidden with `true` in a task by task basis.                                                          |
+| `silent`   | `bool`                             | `false`       | Default 'silent' options for this Taskfile. If `false`, can be overridden with `true` in a task by task basis.                                                         |
 | `dotenv`   | `[]string`                         |               | A list of `.env` file paths to be parsed.                                                                                                                              |
 | `run`      | `string`                           | `always`      | Default 'run' option for this Taskfile. Available options: `always`, `once` and `when_changed`.                                                                        |
 | `interval` | `string`                           | `5s`          | Sets a different watch interval when using `--watch`, the default being 5 seconds. This string should be a valid [Go Duration](https://pkg.go.dev/time#ParseDuration). |
@@ -254,8 +261,9 @@ tasks:
 | Attribute      | Type                               | Default       | Description                                                                                                                                                                                        |
 | -------------- | ---------------------------------- | ------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
 | `cmd`          | `string`                           |               | The shell command to be executed.                                                                                                                                                                  |
-| `silent`       | `bool`                             | `false`       | Skips some output for this command. Note that STDOUT and STDERR of the commands will still be redirected.                                                                                          |
 | `task`         | `string`                           |               | Set this to trigger execution of another task instead of running a command. This cannot be set together with `cmd`.                                                                                |
+| `for`          | [`For`](#for)                      |               | Runs the command once for each given value.                                                                                                                                                        |
+| `silent`       | `bool`                             | `false`       | Skips some output for this command. Note that STDOUT and STDERR of the commands will still be redirected.                                                                                          |
 | `vars`         | [`map[string]Variable`](#variable) |               | Optional additional variables to be passed to the referenced task. Only relevant when setting `task` instead of `cmd`.                                                                             |
 | `ignore_error` | `bool`                             | `false`       | Continue execution if errors happen while executing the command.                                                                                                                                   |
 | `defer`        | `string`                           |               | Alternative to `cmd`, but schedules the command to be executed at the end of this task instead of immediately. This cannot be used together with `cmd`.                                            |
@@ -297,6 +305,22 @@ tasks:
 
 :::
 
+#### For
+
+The `for` parameter can be defined as a string, a list of strings or a map. If it is defined as a string, you can give it any of the following values:
+
+- `source` - Will run the command for each source file defined on the task. (Glob patterns will be resolved, so `*.go` will run for every Go file that matches).
+
+If it is defined as a list of strings, the command will be run for each value.
+
+Finally, the `for` parameter can be defined as a map when you want to use a variable to define the values to loop over:
+
+| Attribute | Type     | Default          | Description                                  |
+| --------- | -------- | ---------------- | -------------------------------------------- |
+| `var`     | `string` |                  | The name of the variable to use as an input. |
+| `split`   | `string` | (any whitespace) | What string the variable should be split on. |
+| `as`      | `string` | `ITEM`           | The name of the iterator variable.           |
+
 #### Precondition
 
 | Attribute | Type     | Default | Description                                                                                                  |

docs/i18n/es-ES/docusaurus-plugin-content-docs/current/changelog.md

@@ -1,394 +1,473 @@
 ---
 slug: /changelog/
-sidebar_position: 9
+sidebar_position: 14
 ---
 
 # Changelog
 
+## v3.33.1 - 2023-12-21
+
+- Added support for looping over map variables with the [Any Variables experiment](https://taskfile.dev/experiments/any_variables) enabled (#1435, #1437 by @pd93).
+- Fixed a bug where dynamic variables were causing errors during fast compilation (#1435, #1437 by @pd93)
+
+## v3.33.0 - 2023-12-20
+
+- Added [Any Variables experiment](https://taskfile.dev/experiments/any-variables) (#1415, #1421 by @pd93).
+- Updated Docusaurus to v3 (#1432 by @pd93).
+- Added `aliases` to `--json` flag output (#1430, #1431 by @pd93).
+- Added new `CLI_FORCE` special variable containing whether the `--force` or `--force-all` flags were set (#1412, #1434 by @pd93).
+
+## v3.32.0 - 2023-11-29
+
+- Added ability to exclude some files from `sources:` by using `exclude:` (#225,
+
+  # 1324 by @pd93 and @andreynering).
+- The [Remote Taskfiles experiment](https://taskfile.dev/experiments/remote-taskfiles) now prefers remote files over cached ones by default (#1317, #1345 by @pd93).
+- Added `--timeout` flag to the [Remote Taskfiles experiment](https://taskfile.dev/experiments/remote-taskfiles) (#1317, #1345 by @pd93).
+- Fix bug where dynamic `vars:` and `env:` were being executed when they should actually be skipped by `platforms:` (#1273, #1377 by @andreynering).
+- Fix `schema.json` to make `silent` valid in `cmds` that use `for` (#1385,
+
+  # 1386 by @iainvm).
+- Add new `--no-status` flag to skip expensive status checks when running `task --list --json` (#1348, #1368 by @amancevice).
+
+## v3.31.0 - 2023-10-07
+
+- Enabled the `--yes` flag for the [Remote Taskfiles experiment](https://taskfile.dev/experiments/remote-taskfiles) (#1317, #1344 by @pd93).
+- Add ability to set `watch: true` in a task to automatically run it in watch mode (#231, #1361 by @andreynering).
+- Fixed a bug on the watch mode where paths that contained `.git` (like `.github`), for example, were also being ignored (#1356 by @butuzov).
+- Fixed a nil pointer error when running a Taskfile with no contents (#1341,
+
+  # 1342 by @pd93).
+- Added a new [exit code](https://taskfile.dev/api/#exit-codes) (107) for when a Taskfile does not contain a schema version (#1342 by @pd93).
+- Increased limit of maximum task calls from 100 to 1000 for now, as some people have been reaching this limit organically now that we have loops. This check exists to detect recursive calls, but will be removed in favor of a better algorithm soon (#1321, #1332).
+- Fixed templating on descriptions on `task --list` (#1343 by @blackjid).
+- Fixed a bug where precondition errors were incorrectly being printed when task execution was aborted (#1337, #1338 by @sylv-io).
+
+## v3.30.1 - 2023-09-14
+
+- Fixed a regression where some special variables weren't being set correctly (#1331, #1334 by @pd93).
+
+## v3.30.0 - 2023-09-13
+
+- Prep work for Remote Taskfiles (#1316 by @pd93).
+- Added the [Remote Taskfiles experiment](https://taskfile.dev/experiments/remote-taskfiles) as a draft (#1152, #1317 by @pd93).
+- Improve performance of content checksuming on `sources:` by replacing md5 with [XXH3](https://xxhash.com/) which is much faster. This is a soft breaking change because checksums will be invalidated when upgrading to this release (#1325 by @ReillyBrogan).
+
+## v3.29.1 - 2023-08-26
+
+- Update to Go 1.21 (bump minimum version to 1.20) (#1302 by @pd93)
+- Fix a missing a line break on log when using `--watch` mode (#1285, #1297 by @FilipSolich).
+- Fix `defer` on JSON Schema (#1288 by @calvinmclean and @andreynering).
+- Fix bug in usage of special variables like `{{.USER_WORKING_DIR}}` in combination with `includes` (#1046, #1205, #1250, #1293, #1312, #1274 by @andarto, #1309 by @andreynering).
+- Fix bug on `--status` flag. Running this flag should not have side-effects: it should not update the checksum on `.task`, only report its status (#1305,
+
+  # 1307 by @visciang, #1313 by @andreynering).
+
+## v3.28.0 - 2023-07-24
+
+- Added the ability to [loop over commands and tasks](https://taskfile.dev/usage/#looping-over-values) using `for` (#82, #1220 by @pd93).
+- Fixed variable propagation in multi-level includes (#778, #996, #1256 by @hudclark).
+- Fixed a bug where the `--exit-code` code flag was not returning the correct exit code when calling commands indirectly (#1266, #1270 by @pd93).
+- Fixed a `nil` panic when a dependency was commented out or left empty (#1263 by @neomantra).
+
 ## v3.27.1 - 2023-06-30
 
-- Fix panic when a `.env` directory (not file) is present on current directory ([#1244](https://github.com/go-task/task/issues/1244), [#1245](https://github.com/go-task/task/issues/1245) by [@pd93](https://github.com/pd93)).
+- Fix panic when a `.env` directory (not file) is present on current directory (#1244, #1245 by @pd93).
 
 ## v3.27.0 - 2023-06-29
 
-- Allow Taskfiles starting with lowercase characters ([#947](https://github.com/go-task/task/issues/947), [#1221](https://github.com/go-task/task/issues/1221) by [@pd93](https://github.com/pd93)).
+- Allow Taskfiles starting with lowercase characters (#947, #1221 by @pd93).
   - e.g. `taskfile.yml`, `taskfile.yaml`, `taskfile.dist.yml` & `taskfile.dist.yaml`
-- Bug fixes were made to the [npm installation method](https://taskfile.dev/installation/#npm). ([#1190](https://github.com/go-task/task/issues/1190), by [@sounisi5011](https://github.com/sounisi5011)).
-- Added the [gentle force experiment](https://taskfile.dev/experiments) as a draft ([#1200](https://github.com/go-task/task/issues/1200), [#1216](https://github.com/go-task/task/issues/1216) by [@pd93](https://github.com/pd93)).
-- Added an `--experiments` flag to allow you to see which experiments are enabled ([#1242](https://github.com/go-task/task/issues/1242) by [@pd93](https://github.com/pd93)).
-- Added ability to specify which variables are required in a task ([#1203](https://github.com/go-task/task/issues/1203), [#1204](https://github.com/go-task/task/issues/1204) by [@benc](https://github.com/benc)-uk).
+- Bug fixes were made to the [npm installation method](https://taskfile.dev/installation/#npm). (#1190, by @sounisi5011).
+- Added the [gentle force experiment](https://taskfile.dev/experiments/gentle-force) as a draft (#1200, #1216 by @pd93).
+- Added an `--experiments` flag to allow you to see which experiments are enabled (#1242 by @pd93).
+- Added ability to specify which variables are required in a task (#1203, #1204 by @benc-uk).
 
 ## v3.26.0 - 2023-06-10
 
-- Only rewrite checksum files in `.task` if the checksum has changed ([#1185](https://github.com/go-task/task/issues/1185), [#1194](https://github.com/go-task/task/issues/1194) by [@deviantintegral](https://github.com/deviantintegral)).
-- Added [experiments documentation](https://taskfile.dev/experiments) to the website ([#1198](https://github.com/go-task/task/issues/1198) by [@pd93](https://github.com/pd93)).
-- Deprecated `version: 2` schema. This will be removed in the next major release ([#1197](https://github.com/go-task/task/issues/1197), [#1198](https://github.com/go-task/task/issues/1198), [#1199](https://github.com/go-task/task/issues/1199) by [@pd93](https://github.com/pd93)).
-- Added a new `prompt:` prop to set a warning prompt to be shown before running a potential dangurous task ([#100](https://github.com/go-task/task/issues/100), [#1163](https://github.com/go-task/task/issues/1163) by [@MaxCheetham](https://github.com/MaxCheetham), [Documentation](https://taskfile.dev/usage/#warning-prompts)).
-- Added support for single command task syntax. With this change, it's now possible to declare just `cmd:` in a task, avoiding the more complex `cmds: []` when you have only a single command for that task ([#1130](https://github.com/go-task/task/issues/1130), [#1131](https://github.com/go-task/task/issues/1131) by [@timdp](https://github.com/timdp)).
+- Only rewrite checksum files in `.task` if the checksum has changed (#1185,
+
+  # 1194 by @deviantintegral).
+- Added [experiments documentation](https://taskfile.dev/experiments) to the website (#1198 by @pd93).
+- Deprecated `version: 2` schema. This will be removed in the next major release (#1197, #1198, #1199 by @pd93).
+- Added a new `prompt:` prop to set a warning prompt to be shown before running a potential dangurous task (#100, #1163 by @MaxCheetham, [Documentation](https://taskfile.dev/usage/#warning-prompts)).
+- Added support for single command task syntax. With this change, it's now possible to declare just `cmd:` in a task, avoiding the more complex `cmds: []` when you have only a single command for that task (#1130, #1131 by @timdp).
 
 ## v3.25.0 - 2023-05-22
 
-- Support `silent:` when calling another tasks ([#680](https://github.com/go-task/task/issues/680), [#1142](https://github.com/go-task/task/issues/1142) by [@danquah](https://github.com/danquah)).
-- Improve PowerShell completion script ([#1168](https://github.com/go-task/task/issues/1168) by [@trim21](https://github.com/trim21)).
-- Add more languages to the website menu and show translation progress percentage ([#1173](https://github.com/go-task/task/issues/1173) by [@misitebao](https://github.com/misitebao)).
-- Starting on this release, official binaries for FreeBSD will be available to download ([#1068](https://github.com/go-task/task/issues/1068) by [@andreynering](https://github.com/andreynering)).
-- Fix some errors being unintendedly supressed ([#1134](https://github.com/go-task/task/issues/1134) by [@clintmod](https://github.com/clintmod)).
-- Fix a nil pointer error when `version` is omitted from a Taskfile ([#1148](https://github.com/go-task/task/issues/1148), [#1149](https://github.com/go-task/task/issues/1149) by [@pd93](https://github.com/pd93)).
-- Fix duplicate error message when a task does not exists ([#1141](https://github.com/go-task/task/issues/1141), [#1144](https://github.com/go-task/task/issues/1144) by [@pd93](https://github.com/pd93)).
+- Support `silent:` when calling another tasks (#680, #1142 by @danquah).
+- Improve PowerShell completion script (#1168 by @trim21).
+- Add more languages to the website menu and show translation progress percentage (#1173 by @misitebao).
+- Starting on this release, official binaries for FreeBSD will be available to download (#1068 by @andreynering).
+- Fix some errors being unintendedly supressed (#1134 by @clintmod).
+- Fix a nil pointer error when `version` is omitted from a Taskfile (#1148,
+
+  # 1149 by @pd93).
+- Fix duplicate error message when a task does not exists (#1141, #1144 by @pd93).
 
 ## v3.24.0 - 2023-04-15
 
-- Fix Fish shell completion for tasks with aliases ([#1113](https://github.com/go-task/task/issues/1113) by [@patricksjackson](https://github.com/patricksjackson)).
-- The default branch was renamed from `master` to `main` ([#1049](https://github.com/go-task/task/issues/1049), [#1048](https://github.com/go-task/task/issues/1048) by [@pd93](https://github.com/pd93)).
-- Fix bug where "up-to-date" logs were not being omitted for silent tasks ([#546](https://github.com/go-task/task/issues/546), [#1107](https://github.com/go-task/task/issues/1107) by [@danquah](https://github.com/danquah)).
-- Add `.hg` (Mercurial) to the list of ignored directories when using `--watch` ([#1098](https://github.com/go-task/task/issues/1098) by [@misery](https://github.com/misery)).
-- More improvements to the release tool ([#1096](https://github.com/go-task/task/issues/1096) by [@pd93](https://github.com/pd93)).
-- Enforce [gofumpt](https://github.com/mvdan/gofumpt) linter ([#1099](https://github.com/go-task/task/issues/1099) by [@pd93](https://github.com/pd93))
-- Add `--sort` flag for use with `--list` and `--list-all` ([#946](https://github.com/go-task/task/issues/946), [#1105](https://github.com/go-task/task/issues/1105) by [@pd93](https://github.com/pd93)).
-- Task now has [custom exit codes](https://taskfile.dev/api/#exit-codes) depending on the error ([#1114](https://github.com/go-task/task/issues/1114) by [@pd93](https://github.com/pd93)).
+- Fix Fish shell completion for tasks with aliases (#1113 by @patricksjackson).
+- The default branch was renamed from `master` to `main` (#1049, #1048 by @pd93).
+- Fix bug where "up-to-date" logs were not being omitted for silent tasks (#546,
+
+  # 1107 by @danquah).
+- Add `.hg` (Mercurial) to the list of ignored directories when using `--watch` (#1098 by @misery).
+- More improvements to the release tool (#1096 by @pd93).
+- Enforce [gofumpt](https://github.com/mvdan/gofumpt) linter (#1099 by @pd93)
+- Add `--sort` flag for use with `--list` and `--list-all` (#946, #1105 by @pd93).
+- Task now has [custom exit codes](https://taskfile.dev/api/#exit-codes) depending on the error (#1114 by @pd93).
 
 ## v3.23.0 - 2023-03-26
 
-Task now has an [official extension for Visual Studio Code](https://marketplace.visualstudio.com/items?itemName=task.vscode-task) contributed by [@pd93](https://github.com/pd93)! :tada: The extension is maintained in a [new repository](https://github.com/go-task/vscode-task) under the `go-task` organization. We're looking to gather feedback from the community so please give it a go and let us know what you think via a [discussion](https://github.com/go-task/vscode-task/discussions), [issue](https://github.com/go-task/vscode-task/issues) or on our [Discord](https://discord.gg/6TY36E39UK)!
+Task now has an [official extension for Visual Studio Code](https://marketplace.visualstudio.com/items?itemName=task.vscode-task) contributed by @pd93! :tada: The extension is maintained in a [new repository](https://github.com/go-task/vscode-task) under the `go-task` organization. We're looking to gather feedback from the community so please give it a go and let us know what you think via a [discussion](https://github.com/go-task/vscode-task/discussions), [issue](https://github.com/go-task/vscode-task/issues) or on our [Discord](https://discord.gg/6TY36E39UK)!
 
 > **NOTE:** The extension _requires_ v3.23.0 to be installed in order to work.
 
-- The website was integrated with [Crowdin](https://crowdin.com/project/taskfile) to allow the community to contribute with translations! [Chinese](https://taskfile.dev/zh-Hans/) is the first language available ([#1057](https://github.com/go-task/task/issues/1057), [#1058](https://github.com/go-task/task/issues/1058) by [@misitebao](https://github.com/misitebao)).
-- Added task location data to the `--json` flag output ([#1056](https://github.com/go-task/task/issues/1056) by [@pd93](https://github.com/pd93))
-- Change the name of the file generated by `task --init` from `Taskfile.yaml` to `Taskfile.yml` ([#1062](https://github.com/go-task/task/issues/1062) by [@misitebao](https://github.com/misitebao)).
-- Added new `splitArgs` template function (`{{splitArgs "foo bar 'foo bar baz'"}}`) to ensure string is split as arguments ([#1040](https://github.com/go-task/task/issues/1040), [#1059](https://github.com/go-task/task/issues/1059) by [@dhanusaputra](https://github.com/dhanusaputra)).
-- Fix the value of `{{.CHECKSUM}}` variable in status ([#1076](https://github.com/go-task/task/issues/1076), [#1080](https://github.com/go-task/task/issues/1080) by [@pd93](https://github.com/pd93)).
-- Fixed deep copy implementation ([#1072](https://github.com/go-task/task/issues/1072) by [@pd93](https://github.com/pd93))
-- Created a tool to assist with releases ([#1086](https://github.com/go-task/task/issues/1086) by [@pd93](https://github.com/pd93)).
+- The website was integrated with [Crowdin](https://crowdin.com/project/taskfile) to allow the community to contribute with translations! [Chinese](https://taskfile.dev/zh-Hans/) is the first language available (#1057, #1058 by @misitebao).
+- Added task location data to the `--json` flag output (#1056 by @pd93)
+- Change the name of the file generated by `task --init` from `Taskfile.yaml` to `Taskfile.yml` (#1062 by @misitebao).
+- Added new `splitArgs` template function (`{{splitArgs "foo bar 'foo bar baz'"}}`) to ensure string is split as arguments (#1040, #1059 by @dhanusaputra).
+- Fix the value of `{{.CHECKSUM}}` variable in status (#1076, #1080 by @pd93).
+- Fixed deep copy implementation (#1072 by @pd93)
+- Created a tool to assist with releases (#1086 by @pd93).
 
 ## v3.22.0 - 2023-03-10
 
-- Add a brand new `--global` (`-g`) flag that will run a Taskfile from your `$HOME` directory. This is useful to have automation that you can run from anywhere in your system! ([Documentation](https://taskfile.dev/usage/#running-a-global-taskfile), [#1029](https://github.com/go-task/task/issues/1029) by [@andreynering](https://github.com/andreynering)).
-- Add ability to set `error_only: true` on the `group` output mode. This will instruct Task to only print a command output if it returned with a non-zero exit code ([#664](https://github.com/go-task/task/issues/664), [#1022](https://github.com/go-task/task/issues/1022) by [@jaedle](https://github.com/jaedle)).
-- Fixed bug where `.task/checksum` file was sometimes not being created when task also declares a `status:` ([#840](https://github.com/go-task/task/issues/840), [#1035](https://github.com/go-task/task/issues/1035) by [@harelwa](https://github.com/harelwa), [#1037](https://github.com/go-task/task/issues/1037) by [@pd93](https://github.com/pd93)).
-- Refactored and decoupled fingerprinting from the main Task executor ([#1039](https://github.com/go-task/task/issues/1039) by [@pd93](https://github.com/pd93)).
-- Fixed deadlock issue when using `run: once` ([#715](https://github.com/go-task/task/issues/715), [#1025](https://github.com/go-task/task/issues/1025) by [@theunrepentantgeek](https://github.com/theunrepentantgeek)).
+- Add a brand new `--global` (`-g`) flag that will run a Taskfile from your `$HOME` directory. This is useful to have automation that you can run from anywhere in your system! ([Documentation](https://taskfile.dev/usage/#running-a-global-taskfile), #1029 by @andreynering).
+- Add ability to set `error_only: true` on the `group` output mode. This will instruct Task to only print a command output if it returned with a non-zero exit code (#664, #1022 by @jaedle).
+- Fixed bug where `.task/checksum` file was sometimes not being created when task also declares a `status:` (#840, #1035 by @harelwa, #1037 by @pd93).
+- Refactored and decoupled fingerprinting from the main Task executor (#1039 by @pd93).
+- Fixed deadlock issue when using `run: once` (#715, #1025 by @theunrepentantgeek).
 
 ## v3.21.0 - 2023-02-22
 
-- Added new `TASK_VERSION` special variable ([#990](https://github.com/go-task/task/issues/990), [#1014](https://github.com/go-task/task/issues/1014) by [@ja1code](https://github.com/ja1code)).
-- Fixed a bug where tasks were sometimes incorrectly marked as internal ([#1007](https://github.com/go-task/task/issues/1007) by [@pd93](https://github.com/pd93)).
-- Update to Go 1.20 (bump minimum version to 1.19) ([#1010](https://github.com/go-task/task/issues/1010) by [@pd93](https://github.com/pd93))
-- Added environment variable `FORCE_COLOR` support to force color output. Usefull for environments without TTY ([#1003](https://github.com/go-task/task/issues/1003) by [@automation](https://github.com/automation)-stack)
+- Added new `TASK_VERSION` special variable (#990, #1014 by @ja1code).
+- Fixed a bug where tasks were sometimes incorrectly marked as internal (#1007 by @pd93).
+- Update to Go 1.20 (bump minimum version to 1.19) (#1010 by @pd93)
+- Added environment variable `FORCE_COLOR` support to force color output. Usefull for environments without TTY (#1003 by @automation-stack)
 
 ## v3.20.0 - 2023-01-14
 
-- Improve behavior and performance of status checking when using the `timestamp` mode ([#976](https://github.com/go-task/task/issues/976), [#977](https://github.com/go-task/task/issues/977) by [@aminya](https://github.com/aminya)).
-- Performance optimizations were made for large Taskfiles ([#982](https://github.com/go-task/task/issues/982) by [@pd93](https://github.com/pd93)).
-- Add ability to configure options for the [`set`](https://www.gnu.org/software/bash/manual/html_node/The-Set-Builtin.html) and [`shopt`](https://www.gnu.org/software/bash/manual/html_node/The-Shopt-Builtin.html) builtins ([#908](https://github.com/go-task/task/issues/908), [#929](https://github.com/go-task/task/issues/929) by [@pd93](https://github.com/pd93), [Documentation](http://taskfile.dev/usage/#set-and-shopt)).
-- Add new `platforms:` attribute to `task` and `cmd`, so it's now possible to choose in which platforms that given task or command will be run on. Possible values are operating system (GOOS), architecture (GOARCH) or a combination of the two. Example: `platforms: [linux]`, `platforms: [amd64]` or `platforms: [linux/amd64]`. Other platforms will be skipped ([#978](https://github.com/go-task/task/issues/978), [#980](https://github.com/go-task/task/issues/980) by [@leaanthony](https://github.com/leaanthony)).
+- Improve behavior and performance of status checking when using the `timestamp` mode (#976, #977 by @aminya).
+- Performance optimizations were made for large Taskfiles (#982 by @pd93).
+- Add ability to configure options for the [`set`](https://www.gnu.org/software/bash/manual/html_node/The-Set-Builtin.html) and [`shopt`](https://www.gnu.org/software/bash/manual/html_node/The-Shopt-Builtin.html) builtins (#908, #929 by @pd93, [Documentation](http://taskfile.dev/usage/#set-and-shopt)).
+- Add new `platforms:` attribute to `task` and `cmd`, so it's now possible to choose in which platforms that given task or command will be run on. Possible values are operating system (GOOS), architecture (GOARCH) or a combination of the two. Example: `platforms: [linux]`, `platforms: [amd64]` or `platforms: [linux/amd64]`. Other platforms will be skipped (#978, #980 by @leaanthony).
 
 ## v3.19.1 - 2022-12-31
 
-- Small bug fix: closing `Taskfile.yml` once we're done reading it ([#963](https://github.com/go-task/task/issues/963), [#964](https://github.com/go-task/task/issues/964) by [@HeCorr](https://github.com/HeCorr)).
-- Fixes a bug in v2 that caused a panic when using a `Taskfile_{{OS}}.yml` file ([#961](https://github.com/go-task/task/issues/961), [#971](https://github.com/go-task/task/issues/971) by [@pd93](https://github.com/pd93)).
-- Fixed a bug where watch intervals set in the Taskfile were not being respected ([#969](https://github.com/go-task/task/issues/969), [#970](https://github.com/go-task/task/issues/970) by [@pd93](https://github.com/pd93))
-- Add `--json` flag (alias `-j`) with the intent to improve support for code editors and add room to other possible integrations. This is basic for now, but we plan to add more info in the near future ([#936](https://github.com/go-task/task/issues/936) by [@davidalpert](https://github.com/davidalpert), [#764](https://github.com/go-task/task/issues/764)).
+- Small bug fix: closing `Taskfile.yml` once we're done reading it (#963, #964 by @HeCorr).
+- Fixes a bug in v2 that caused a panic when using a `Taskfile_{{OS}}.yml` file (#961, #971 by @pd93).
+- Fixed a bug where watch intervals set in the Taskfile were not being respected (#969, #970 by @pd93)
+- Add `--json` flag (alias `-j`) with the intent to improve support for code editors and add room to other possible integrations. This is basic for now, but we plan to add more info in the near future (#936 by @davidalpert, #764).
 
 ## v3.19.0 - 2022-12-05
 
-- Installation via npm now supports [pnpm](https://pnpm.io/) as well ([go-task/go-npm\[#2\](https://github.com/go-task/task/issues/2)](https://github.com/go-task/go-npm/issues/2), [go-task/go-npm\[#3\](https://github.com/go-task/task/issues/3)](https://github.com/go-task/go-npm/pull/3)).
-- It's now possible to run Taskfiles from subdirectories! A new `USER_WORKING_DIR` special variable was added to add even more flexibility for monorepos ([#289](https://github.com/go-task/task/issues/289), [#920](https://github.com/go-task/task/issues/920)).
-- Add task-level `dotenv` support ([#389](https://github.com/go-task/task/issues/389), [#904](https://github.com/go-task/task/issues/904)).
-- It's now possible to use global level variables on `includes` ([#942](https://github.com/go-task/task/issues/942), [#943](https://github.com/go-task/task/issues/943)).
-- The website got a brand new [translation to Chinese](https://task-zh.readthedocs.io/zh_CN/latest/) by [\[@DeronW\](https://github.com/DeronW)](https://github.com/DeronW). Thanks!
+- Installation via npm now supports [pnpm](https://pnpm.io/) as well ([go-task/go-npm#2](https://github.com/go-task/go-npm/issues/2), [go-task/go-npm#3](https://github.com/go-task/go-npm/pull/3)).
+- It's now possible to run Taskfiles from subdirectories! A new `USER_WORKING_DIR` special variable was added to add even more flexibility for monorepos (#289, #920).
+- Add task-level `dotenv` support (#389, #904).
+- It's now possible to use global level variables on `includes` (#942, #943).
+- The website got a brand new [translation to Chinese](https://task-zh.readthedocs.io/zh_CN/latest/) by [@DeronW](https://github.com/DeronW). Thanks!
 
 ## v3.18.0 - 2022-11-12
 
-- Show aliases on `task --list --silent` (`task --ls`). This means that aliases will be completed by the completion scripts ([#919](https://github.com/go-task/task/issues/919)).
-- Tasks in the root Taskfile will now be displayed first in `--list`/`--list-all` output ([#806](https://github.com/go-task/task/issues/806), [#890](https://github.com/go-task/task/issues/890)).
-- It's now possible to call a `default` task in an included Taskfile by using just the namespace. For example: `docs:default` is now automatically aliased to `docs` ([#661](https://github.com/go-task/task/issues/661), [#815](https://github.com/go-task/task/issues/815)).
+- Show aliases on `task --list --silent` (`task --ls`). This means that aliases will be completed by the completion scripts (#919).
+- Tasks in the root Taskfile will now be displayed first in `--list`/`--list-all` output (#806, #890).
+- It's now possible to call a `default` task in an included Taskfile by using just the namespace. For example: `docs:default` is now automatically aliased to `docs` (#661, #815).
 
 ## v3.17.0 - 2022-10-14
 
-- Add a "Did you mean ...?" suggestion when a task does not exits another one with a similar name is found ([#867](https://github.com/go-task/task/issues/867), [#880](https://github.com/go-task/task/issues/880)).
-- Now YAML parse errors will print which Taskfile failed to parse ([#885](https://github.com/go-task/task/issues/885), [#887](https://github.com/go-task/task/issues/887)).
-- Add ability to set `aliases` for tasks and namespaces ([#268](https://github.com/go-task/task/issues/268), [#340](https://github.com/go-task/task/issues/340), [#879](https://github.com/go-task/task/issues/879)).
-- Improvements to Fish shell completion ([#897](https://github.com/go-task/task/issues/897)).
-- Added ability to set a different watch interval by setting `interval: '500ms'` or using the `--interval=500ms` flag ([#813](https://github.com/go-task/task/issues/813), [#865](https://github.com/go-task/task/issues/865)).
-- Add colored output to `--list`, `--list-all` and `--summary` flags ([#845](https://github.com/go-task/task/issues/845), [#874](https://github.com/go-task/task/issues/874)).
-- Fix unexpected behavior where `label:` was being shown instead of the task name on `--list` ([#603](https://github.com/go-task/task/issues/603), [#877](https://github.com/go-task/task/issues/877)).
+- Add a "Did you mean ...?" suggestion when a task does not exits another one with a similar name is found (#867, #880).
+- Now YAML parse errors will print which Taskfile failed to parse (#885, #887).
+- Add ability to set `aliases` for tasks and namespaces (#268, #340, #879).
+- Improvements to Fish shell completion (#897).
+- Added ability to set a different watch interval by setting `interval: '500ms'` or using the `--interval=500ms` flag (#813, #865).
+- Add colored output to `--list`, `--list-all` and `--summary` flags (#845,
+
+  # 874).
+- Fix unexpected behavior where `label:` was being shown instead of the task name on `--list` (#603, #877).
 
 ## v3.16.0 - 2022-09-29
 
-- Add `npm` as new installation method: `npm i -g [@go](https://github.com/go)-task/cli` ([#870](https://github.com/go-task/task/issues/870), [#871](https://github.com/go-task/task/issues/871), [npm package](https://www.npmjs.com/package/[@go](https://github.com/go)-task/cli)).
-- Add support to marking tasks and includes as internal, which will hide them from `--list` and `--list-all` ([#818](https://github.com/go-task/task/issues/818)).
+- Add `npm` as new installation method: `npm i -g @go-task/cli` (#870, #871, [npm package](https://www.npmjs.com/package/@go-task/cli)).
+- Add support to marking tasks and includes as internal, which will hide them from `--list` and `--list-all` (#818).
 
 ## v3.15.2 - 2022-09-08
 
-- Fix error when using variable in `env:` introduced in the previous release ([#858](https://github.com/go-task/task/issues/858), [#866](https://github.com/go-task/task/issues/866)).
-- Fix handling of `CLI_ARGS` (`--`) in Bash completion ([#863](https://github.com/go-task/task/issues/863)).
-- On zsh completion, add ability to replace `--list-all` with `--list` as already possible on the Bash completion ([#861](https://github.com/go-task/task/issues/861)).
+- Fix error when using variable in `env:` introduced in the previous release (#858, #866).
+- Fix handling of `CLI_ARGS` (`--`) in Bash completion (#863).
+- On zsh completion, add ability to replace `--list-all` with `--list` as already possible on the Bash completion (#861).
 
 ## v3.15.0 - 2022-09-03
 
-- Add new special variables `ROOT_DIR` and `TASKFILE_DIR`. This was a highly requested feature ([#215](https://github.com/go-task/task/issues/215), [#857](https://github.com/go-task/task/issues/857), [Documentation](https://taskfile.dev/api/#special-variables)).
-- Follow symlinks on `sources` ([#826](https://github.com/go-task/task/issues/826), [#831](https://github.com/go-task/task/issues/831)).
-- Improvements and fixes to Bash completion ([#835](https://github.com/go-task/task/issues/835), [#844](https://github.com/go-task/task/issues/844)).
+- Add new special variables `ROOT_DIR` and `TASKFILE_DIR`. This was a highly requested feature (#215, #857, [Documentation](https://taskfile.dev/api/#special-variables)).
+- Follow symlinks on `sources` (#826, #831).
+- Improvements and fixes to Bash completion (#835, #844).
 
 ## v3.14.1 - 2022-08-03
 
-- Always resolve relative include paths relative to the including Taskfile ([#822](https://github.com/go-task/task/issues/822), [#823](https://github.com/go-task/task/issues/823)).
-- Fix ZSH and PowerShell completions to consider all tasks instead of just the public ones (those with descriptions) ([#803](https://github.com/go-task/task/issues/803)).
+- Always resolve relative include paths relative to the including Taskfile (#822, #823).
+- Fix ZSH and PowerShell completions to consider all tasks instead of just the public ones (those with descriptions) (#803).
 
 ## v3.14.0 - 2022-07-08
 
 - Add ability to override the `.task` directory location with the `TASK_TEMP_DIR` environment variable.
-- Allow to override Task colors using environment variables: `TASK_COLOR_RESET`, `TASK_COLOR_BLUE`, `TASK_COLOR_GREEN`, `TASK_COLOR_CYAN`, `TASK_COLOR_YELLOW`, `TASK_COLOR_MAGENTA` and `TASK_COLOR_RED` ([#568](https://github.com/go-task/task/issues/568), [#792](https://github.com/go-task/task/issues/792)).
-- Fixed bug when using the `output: group` mode where STDOUT and STDERR were being print in separated blocks instead of in the right order ([#779](https://github.com/go-task/task/issues/779)).
-- Starting on this release, ARM architecture binaries are been released to Snap as well ([#795](https://github.com/go-task/task/issues/795)).
+- Allow to override Task colors using environment variables: `TASK_COLOR_RESET`, `TASK_COLOR_BLUE`, `TASK_COLOR_GREEN`, `TASK_COLOR_CYAN`, `TASK_COLOR_YELLOW`, `TASK_COLOR_MAGENTA` and `TASK_COLOR_RED` (#568, #792).
+- Fixed bug when using the `output: group` mode where STDOUT and STDERR were being print in separated blocks instead of in the right order (#779).
+- Starting on this release, ARM architecture binaries are been released to Snap as well (#795).
 - i386 binaries won't be available anymore on Snap because Ubuntu removed the support for this architecture.
-- Upgrade mvdan.cc/sh, which fixes a bug with associative arrays ([#785](https://github.com/go-task/task/issues/785), [mvdan/sh\[#884\](https://github.com/go-task/task/issues/884)](https://github.com/mvdan/sh/issues/884), [mvdan/sh\[#893\](https://github.com/go-task/task/issues/893)](https://github.com/mvdan/sh/pull/893)).
+- Upgrade mvdan.cc/sh, which fixes a bug with associative arrays (#785, [mvdan/sh#884](https://github.com/mvdan/sh/issues/884), [mvdan/sh#893](https://github.com/mvdan/sh/pull/893)).
 
 ## v3.13.0 - 2022-06-13
 
-- Added `-n` as an alias to `--dry` ([#776](https://github.com/go-task/task/issues/776), [#777](https://github.com/go-task/task/issues/777)).
-- Fix behavior of interrupt (SIGINT, SIGTERM) signals. Task will now give time for the processes running to do cleanup work ([#458](https://github.com/go-task/task/issues/458), [#479](https://github.com/go-task/task/issues/479), [#728](https://github.com/go-task/task/issues/728), [#769](https://github.com/go-task/task/issues/769)).
-- Add new `--exit-code` (`-x`) flag that will pass-through the exit form the command being ran ([#755](https://github.com/go-task/task/issues/755)).
+- Added `-n` as an alias to `--dry` (#776, #777).
+- Fix behavior of interrupt (SIGINT, SIGTERM) signals. Task will now give time for the processes running to do cleanup work (#458, #479, #728, #769).
+- Add new `--exit-code` (`-x`) flag that will pass-through the exit form the command being ran (#755).
 
 ## v3.12.1 - 2022-05-10
 
-- Fixed bug where, on Windows, variables were ending with `\r` because we were only removing the final `\n` but not `\r\n` ([#717](https://github.com/go-task/task/issues/717)).
+- Fixed bug where, on Windows, variables were ending with `\r` because we were only removing the final `\n` but not `\r\n` (#717).
 
 ## v3.12.0 - 2022-03-31
 
-- The `--list` and `--list-all` flags can now be combined with the `--silent` flag to print the task names only, without their description ([#691](https://github.com/go-task/task/issues/691)).
-- Added support for multi-level inclusion of Taskfiles. This means that included Taskfiles can also include other Taskfiles. Before this was limited to one level ([#390](https://github.com/go-task/task/issues/390), [#623](https://github.com/go-task/task/issues/623), [#656](https://github.com/go-task/task/issues/656)).
-- Add ability to specify vars when including a Taskfile. [Check out the documentation](https://taskfile.dev/#/usage?id=vars-of-included-taskfiles) for more information ([#677](https://github.com/go-task/task/issues/677)).
+- The `--list` and `--list-all` flags can now be combined with the `--silent` flag to print the task names only, without their description (#691).
+- Added support for multi-level inclusion of Taskfiles. This means that included Taskfiles can also include other Taskfiles. Before this was limited to one level (#390, #623, #656).
+- Add ability to specify vars when including a Taskfile. [Check out the documentation](https://taskfile.dev/#/usage?id=vars-of-included-taskfiles) for more information (#677).
 
 ## v3.11.0 - 2022-02-19
 
-- Task now supports printing begin and end messages when using the `group` output mode, useful for grouping tasks in CI systems. [Check out the documentation](http://taskfile.dev/#/usage?id=output-syntax) for more information ([#647](https://github.com/go-task/task/issues/647), [#651](https://github.com/go-task/task/issues/651)).
-- Add `Taskfile.dist.yml` and `Taskfile.dist.yaml` to the supported file name list. [Check out the documentation](https://taskfile.dev/#/usage?id=supported-file-names) for more information ([#498](https://github.com/go-task/task/issues/498), [#666](https://github.com/go-task/task/issues/666)).
+- Task now supports printing begin and end messages when using the `group` output mode, useful for grouping tasks in CI systems. [Check out the documentation](http://taskfile.dev/#/usage?id=output-syntax) for more information (#647, #651).
+- Add `Taskfile.dist.yml` and `Taskfile.dist.yaml` to the supported file name list. [Check out the documentation](https://taskfile.dev/#/usage?id=supported-file-names) for more information (#498, #666).
 
 ## v3.10.0 - 2022-01-04
 
-- A new `--list-all` (alias `-a`) flag is now available. It's similar to the exiting `--list` (`-l`) but prints all tasks, even those without a description ([#383](https://github.com/go-task/task/issues/383), [#401](https://github.com/go-task/task/issues/401)).
-- It's now possible to schedule cleanup commands to run once a task finishes with the `defer:` keyword ([Documentation](https://taskfile.dev/#/usage?id=doing-task-cleanup-with-defer), [#475](https://github.com/go-task/task/issues/475), [#626](https://github.com/go-task/task/issues/626)).
-- Remove long deprecated and undocumented `$` variable prefix and `^` command prefix ([#642](https://github.com/go-task/task/issues/642), [#644](https://github.com/go-task/task/issues/644), [#645](https://github.com/go-task/task/issues/645)).
-- Add support for `.yaml` extension (as an alternative to `.yml`). This was requested multiple times throughout the years. Enjoy! ([#183](https://github.com/go-task/task/issues/183), [#184](https://github.com/go-task/task/issues/184), [#369](https://github.com/go-task/task/issues/369), [#584](https://github.com/go-task/task/issues/584), [#621](https://github.com/go-task/task/issues/621)).
-- Fixed error when computing a variable when the task directory do not exist yet ([#481](https://github.com/go-task/task/issues/481), [#579](https://github.com/go-task/task/issues/579)).
+- A new `--list-all` (alias `-a`) flag is now available. It's similar to the exiting `--list` (`-l`) but prints all tasks, even those without a description (#383, #401).
+- It's now possible to schedule cleanup commands to run once a task finishes with the `defer:` keyword ([Documentation](https://taskfile.dev/#/usage?id=doing-task-cleanup-with-defer),
+
+  # 475, #626).
+- Remove long deprecated and undocumented `$` variable prefix and `^` command prefix (#642, #644, #645).
+- Add support for `.yaml` extension (as an alternative to `.yml`). This was requested multiple times throughout the years. Enjoy! (#183, #184, #369, #584,
+
+  # 621).
+- Fixed error when computing a variable when the task directory do not exist yet (#481, #579).
 
 ## v3.9.2 - 2021-12-02
 
-- Upgrade [mvdan/sh](https://github.com/mvdan/sh) which contains a fix a for a important regression on Windows ([#619](https://github.com/go-task/task/issues/619), [mvdan/sh\[#768\](https://github.com/go-task/task/issues/768)](https://github.com/mvdan/sh/issues/768), [mvdan/sh\[#769\](https://github.com/go-task/task/issues/769)](https://github.com/mvdan/sh/pull/769)).
+- Upgrade [mvdan/sh](https://github.com/mvdan/sh) which contains a fix a for a important regression on Windows (#619, [mvdan/sh#768](https://github.com/mvdan/sh/issues/768), [mvdan/sh#769](https://github.com/mvdan/sh/pull/769)).
 
 ## v3.9.1 - 2021-11-28
 
-- Add logging in verbose mode for when a task starts and finishes ([#533](https://github.com/go-task/task/issues/533), [#588](https://github.com/go-task/task/issues/588)).
-- Fix an issue with preconditions and context errors ([#597](https://github.com/go-task/task/issues/597), [#598](https://github.com/go-task/task/issues/598)).
-- Quote each `{{.CLI_ARGS}}` argument to prevent one with spaces to become many ([#613](https://github.com/go-task/task/issues/613)).
-- Fix nil pointer when `cmd:` was left empty ([#612](https://github.com/go-task/task/issues/612), [#614](https://github.com/go-task/task/issues/614)).
+- Add logging in verbose mode for when a task starts and finishes (#533, #588).
+- Fix an issue with preconditions and context errors (#597, #598).
+- Quote each `{{.CLI_ARGS}}` argument to prevent one with spaces to become many (#613).
+- Fix nil pointer when `cmd:` was left empty (#612, #614).
 - Upgrade [mvdan/sh](https://github.com/mvdan/sh) which contains two relevant fixes:
-  - Fix quote of empty strings in `shellQuote` ([#609](https://github.com/go-task/task/issues/609), [mvdan/sh\[#763\](https://github.com/go-task/task/issues/763)](https://github.com/mvdan/sh/issues/763)).
-  - Fix issue of wrong environment variable being picked when there's another very similar one ([#586](https://github.com/go-task/task/issues/586), [mvdan/sh\[#745\](https://github.com/go-task/task/issues/745)](https://github.com/mvdan/sh/pull/745)).
-- Install shell completions automatically when installing via Homebrew ([#264](https://github.com/go-task/task/issues/264), [#592](https://github.com/go-task/task/issues/592), [go-task/homebrew-tap\[#2\](https://github.com/go-task/task/issues/2)](https://github.com/go-task/homebrew-tap/pull/2)).
+  - Fix quote of empty strings in `shellQuote` (#609, [mvdan/sh#763](https://github.com/mvdan/sh/issues/763)).
+  - Fix issue of wrong environment variable being picked when there's another very similar one (#586, [mvdan/sh#745](https://github.com/mvdan/sh/pull/745)).
+- Install shell completions automatically when installing via Homebrew (#264, #592, [go-task/homebrew-tap#2](https://github.com/go-task/homebrew-tap/pull/2)).
 
 ## v3.9.0 - 2021-10-02
 
-- A new `shellQuote` function was added to the template system (`{{shellQuote "a string"}}`) to ensure a string is safe for use in shell ([mvdan/sh\[#727\](https://github.com/go-task/task/issues/727)](https://github.com/mvdan/sh/pull/727), [mvdan/sh\[#737\](https://github.com/go-task/task/issues/737)](https://github.com/mvdan/sh/pull/737), [Documentation](https://pkg.go.dev/mvdan.cc/sh/v3[@v3](https://github.com/v3).4.0/syntax#Quote))
+- A new `shellQuote` function was added to the template system (`{{shellQuote "a string"}}`) to ensure a string is safe for use in shell ([mvdan/sh#727](https://github.com/mvdan/sh/pull/727), [mvdan/sh#737](https://github.com/mvdan/sh/pull/737), [Documentation](https://pkg.go.dev/mvdan.cc/sh/v3@v3.4.0/syntax#Quote))
 - In this version [mvdan.cc/sh](https://github.com/mvdan/sh) was upgraded with some small fixes and features
-  - The `read -p` flag is now supported ([#314](https://github.com/go-task/task/issues/314), [mvdan/sh\[#551\](https://github.com/go-task/task/issues/551)](https://github.com/mvdan/sh/issues/551), [mvdan/sh\[#772\](https://github.com/go-task/task/issues/772)](https://github.com/mvdan/sh/pull/722))
-  - The `pwd -P` and `pwd -L` flags are now supported ([#553](https://github.com/go-task/task/issues/553), [mvdan/sh\[#724\](https://github.com/go-task/task/issues/724)](https://github.com/mvdan/sh/issues/724), [mvdan/sh\[#728\](https://github.com/go-task/task/issues/728)](https://github.com/mvdan/sh/pull/728))
-  - The `$GID` environment variable is now correctly being set ([#561](https://github.com/go-task/task/issues/561), [mvdan/sh\[#723\](https://github.com/go-task/task/issues/723)](https://github.com/mvdan/sh/pull/723))
+  - The `read -p` flag is now supported (#314, [mvdan/sh#551](https://github.com/mvdan/sh/issues/551), [mvdan/sh#772](https://github.com/mvdan/sh/pull/722))
+  - The `pwd -P` and `pwd -L` flags are now supported (#553, [mvdan/sh#724](https://github.com/mvdan/sh/issues/724), [mvdan/sh#728](https://github.com/mvdan/sh/pull/728))
+  - The `$GID` environment variable is now correctly being set (#561, [mvdan/sh#723](https://github.com/mvdan/sh/pull/723))
 
 ## v3.8.0 - 2021-09-26
 
-- Add `interactive: true` setting to improve support for interactive CLI apps ([#217](https://github.com/go-task/task/issues/217), [#563](https://github.com/go-task/task/issues/563)).
-- Fix some `nil` errors ([#534](https://github.com/go-task/task/issues/534), [#573](https://github.com/go-task/task/issues/573)).
-- Add ability to declare an included Taskfile as optional ([#519](https://github.com/go-task/task/issues/519), [#552](https://github.com/go-task/task/issues/552)).
-- Add support for including Taskfiles in the home directory by using `~` ([#539](https://github.com/go-task/task/issues/539), [#557](https://github.com/go-task/task/issues/557)).
+- Add `interactive: true` setting to improve support for interactive CLI apps (#217, #563).
+- Fix some `nil` errors (#534, #573).
+- Add ability to declare an included Taskfile as optional (#519, #552).
+- Add support for including Taskfiles in the home directory by using `~` (#539, #557).
 
 ## v3.7.3 - 2021-09-04
 
-- Add official support to Apple M1 ([#564](https://github.com/go-task/task/issues/564), [#567](https://github.com/go-task/task/issues/567)).
+- Add official support to Apple M1 (#564, #567).
 - Our [official Homebrew tap](https://github.com/go-task/homebrew-tap) will support more platforms, including Apple M1
 
 ## v3.7.0 - 2021-07-31
 
-- Add `run:` setting to control if tasks should run multiple times or not. Available options are `always` (the default), `when_changed` (if a variable modified the task) and `once` (run only once no matter what). This is a long time requested feature. Enjoy! ([#53](https://github.com/go-task/task/issues/53), [#359](https://github.com/go-task/task/issues/359)).
+- Add `run:` setting to control if tasks should run multiple times or not. Available options are `always` (the default), `when_changed` (if a variable modified the task) and `once` (run only once no matter what). This is a long time requested feature. Enjoy! (#53, #359).
 
 ## v3.6.0 - 2021-07-10
 
-- Allow using both `sources:` and `status:` in the same task ([#411](https://github.com/go-task/task/issues/411), [#427](https://github.com/go-task/task/issues/427), [#477](https://github.com/go-task/task/issues/477)).
-- Small optimization and bug fix: don't compute variables if not needed for `dotenv:` ([#517](https://github.com/go-task/task/issues/517)).
+- Allow using both `sources:` and `status:` in the same task (#411, #427, #477).
+- Small optimization and bug fix: don't compute variables if not needed for `dotenv:` (#517).
 
 ## v3.5.0 - 2021-07-04
 
-- Add support for interpolation in `dotenv:` ([#433](https://github.com/go-task/task/issues/433), [#434](https://github.com/go-task/task/issues/434), [#453](https://github.com/go-task/task/issues/453)).
+- Add support for interpolation in `dotenv:` (#433, #434, #453).
 
 ## v3.4.3 - 2021-05-30
 
-- Add support for the `NO_COLOR` environment variable. ([#459](https://github.com/go-task/task/issues/459), [fatih/color\[#137\](https://github.com/go-task/task/issues/137)](https://github.com/fatih/color/pull/137)).
-- Fix bug where sources were not considering the right directory in `--watch` mode ([#484](https://github.com/go-task/task/issues/484), [#485](https://github.com/go-task/task/issues/485)).
+- Add support for the `NO_COLOR` environment variable. (#459, [fatih/color#137](https://github.com/fatih/color/pull/137)).
+- Fix bug where sources were not considering the right directory in `--watch` mode (#484, #485).
 
 ## v3.4.2 - 2021-04-23
 
-- On watch, report which file failed to read ([#472](https://github.com/go-task/task/issues/472)).
-- Do not try to catch SIGKILL signal, which are not actually possible ([#476](https://github.com/go-task/task/issues/476)).
-- Improve version reporting when building Task from source using Go Modules ([#462](https://github.com/go-task/task/issues/462), [#473](https://github.com/go-task/task/issues/473)).
+- On watch, report which file failed to read (#472).
+- Do not try to catch SIGKILL signal, which are not actually possible (#476).
+- Improve version reporting when building Task from source using Go Modules (#462, #473).
 
 ## v3.4.1 - 2021-04-17
 
-- Improve error reporting when parsing YAML: in some situations where you would just see an generic error, you'll now see the actual error with more detail: the YAML line the failed to parse, for example ([#467](https://github.com/go-task/task/issues/467)).
-- A JSON Schema was published [here](https://json.schemastore.org/taskfile.json) and is automatically being used by some editors like Visual Studio Code ([#135](https://github.com/go-task/task/issues/135)).
-- Print task name before the command in the log output ([#398](https://github.com/go-task/task/issues/398)).
+- Improve error reporting when parsing YAML: in some situations where you would just see an generic error, you'll now see the actual error with more detail: the YAML line the failed to parse, for example (#467).
+- A JSON Schema was published [here](https://json.schemastore.org/taskfile.json) and is automatically being used by some editors like Visual Studio Code (#135).
+- Print task name before the command in the log output (#398).
 
 ## v3.3.0 - 2021-03-20
 
-- Add support for delegating CLI arguments to commands with `--` and a special `CLI_ARGS` variable ([#327](https://github.com/go-task/task/issues/327)).
-- Add a `--concurrency` (alias `-C`) flag, to limit the number of tasks that run concurrently. This is useful for heavy workloads. ([#345](https://github.com/go-task/task/issues/345)).
+- Add support for delegating CLI arguments to commands with `--` and a special `CLI_ARGS` variable (#327).
+- Add a `--concurrency` (alias `-C`) flag, to limit the number of tasks that run concurrently. This is useful for heavy workloads. (#345).
 
 ## v3.2.2 - 2021-01-12
 
-- Improve performance of `--list` and `--summary` by skipping running shell variables for these flags ([#332](https://github.com/go-task/task/issues/332)).
-- Fixed a bug where an environment in a Taskfile was not always overridable by the system environment ([#425](https://github.com/go-task/task/issues/425)).
-- Fixed environment from .env files not being available as variables ([#379](https://github.com/go-task/task/issues/379)).
-- The install script is now working for ARM platforms ([#428](https://github.com/go-task/task/issues/428)).
+- Improve performance of `--list` and `--summary` by skipping running shell variables for these flags (#332).
+- Fixed a bug where an environment in a Taskfile was not always overridable by the system environment (#425).
+- Fixed environment from .env files not being available as variables (#379).
+- The install script is now working for ARM platforms (#428).
 
 ## v3.2.1 - 2021-01-09
 
-- Fixed some bugs and regressions regarding dynamic variables and directories ([#426](https://github.com/go-task/task/issues/426)).
+- Fixed some bugs and regressions regarding dynamic variables and directories (#426).
 - The [slim-sprig](https://github.com/go-task/slim-sprig) package was updated with the upstream [sprig](https://github.com/Masterminds/sprig).
 
 ## v3.2.0 - 2021-01-07
 
-- Fix the `.task` directory being created in the task directory instead of the Taskfile directory ([#247](https://github.com/go-task/task/issues/247)).
-- Fix a bug where dynamic variables (those declared with `sh:`) were not running in the task directory when the task has a custom dir or it was in an included Taskfile ([#384](https://github.com/go-task/task/issues/384)).
-- The watch feature (via the `--watch` flag) got a few different bug fixes and should be more stable now ([#423](https://github.com/go-task/task/issues/423), [#365](https://github.com/go-task/task/issues/365)).
+- Fix the `.task` directory being created in the task directory instead of the Taskfile directory (#247).
+- Fix a bug where dynamic variables (those declared with `sh:`) were not running in the task directory when the task has a custom dir or it was in an included Taskfile (#384).
+- The watch feature (via the `--watch` flag) got a few different bug fixes and should be more stable now (#423, #365).
 
 ## v3.1.0 - 2021-01-03
 
-- Fix a bug when the checksum up-to-date resolution is used by a task with a custom `label:` attribute ([#412](https://github.com/go-task/task/issues/412)).
-- Starting from this release, we're releasing official ARMv6 and ARM64 binaries for Linux ([#375](https://github.com/go-task/task/issues/375), [#418](https://github.com/go-task/task/issues/418)).
-- Task now respects the order of declaration of included Taskfiles when evaluating variables declaring by them ([#393](https://github.com/go-task/task/issues/393)).
-- `set -e` is now automatically set on every command. This was done to fix an issue where multiline string commands wouldn't really fail unless the sentence was in the last line ([#403](https://github.com/go-task/task/issues/403)).
+- Fix a bug when the checksum up-to-date resolution is used by a task with a custom `label:` attribute (#412).
+- Starting from this release, we're releasing official ARMv6 and ARM64 binaries for Linux (#375, #418).
+- Task now respects the order of declaration of included Taskfiles when evaluating variables declaring by them (#393).
+- `set -e` is now automatically set on every command. This was done to fix an issue where multiline string commands wouldn't really fail unless the sentence was in the last line (#403).
 
 ## v3.0.1 - 2020-12-26
 
-- Allow use as a library by moving the required packages out of the `internal` directory ([#358](https://github.com/go-task/task/issues/358)).
-- Do not error if a specified dotenv file does not exist ([#378](https://github.com/go-task/task/issues/378), [#385](https://github.com/go-task/task/issues/385)).
-- Fix panic when you have empty tasks in your Taskfile ([#338](https://github.com/go-task/task/issues/338), [#362](https://github.com/go-task/task/issues/362)).
+- Allow use as a library by moving the required packages out of the `internal` directory (#358).
+- Do not error if a specified dotenv file does not exist (#378, #385).
+- Fix panic when you have empty tasks in your Taskfile (#338, #362).
 
 ## v3.0.0 - 2020-08-16
 
-- On `v3`, all CLI variables will be considered global variables ([#336](https://github.com/go-task/task/issues/336), [#341](https://github.com/go-task/task/issues/341))
-- Add support to `.env` like files ([#324](https://github.com/go-task/task/issues/324), [#356](https://github.com/go-task/task/issues/356)).
-- Add `label:` to task so you can override the task name in the logs ([\[#321\](https://github.com/go-task/task/issues/321)](https://github.com/go-task/task/issues/321]), [#337](https://github.com/go-task/task/issues/337)).
-- Refactor how variables work on version 3 ([#311](https://github.com/go-task/task/issues/311)).
+- On `v3`, all CLI variables will be considered global variables (#336, #341)
+- Add support to `.env` like files (#324, #356).
+- Add `label:` to task so you can override the task name in the logs (#321,
+
+  # 337).
+- Refactor how variables work on version 3 (#311).
 - Disallow `expansions` on v3 since it has no effect.
 - `Taskvars.yml` is not automatically included anymore.
 - `Taskfile_{{OS}}.yml` is not automatically included anymore.
 - Allow interpolation on `includes`, so you can manually include a Taskfile based on operation system, for example.
-- Expose `.TASK` variable in templates with the task name ([#252](https://github.com/go-task/task/issues/252)).
-- Implement short task syntax ([#194](https://github.com/go-task/task/issues/194), [#240](https://github.com/go-task/task/issues/240)).
-- Added option to make included Taskfile run commands on its own directory ([#260](https://github.com/go-task/task/issues/260), [#144](https://github.com/go-task/task/issues/144))
-- Taskfiles in version 1 are not supported anymore ([#237](https://github.com/go-task/task/issues/237)).
-- Added global `method:` option. With this option, you can set a default method to all tasks in a Taskfile ([#246](https://github.com/go-task/task/issues/246)).
-- Changed default method from `timestamp` to `checksum` ([#246](https://github.com/go-task/task/issues/246)).
-- New magic variables are now available when using `status:`: `.TIMESTAMP` which contains the greatest modification date from the files listed in `sources:`, and `.CHECKSUM`, which contains a checksum of all files listed in `status:`. This is useful for manual checking when using external, or even remote, artifacts when using `status:` ([#216](https://github.com/go-task/task/issues/216)).
-- We're now using [slim-sprig](https://github.com/go-task/slim-sprig) instead of [sprig](https://github.com/Masterminds/sprig), which allowed a file size reduction of about 22% ([#219](https://github.com/go-task/task/issues/219)).
-- We now use some colors on Task output to better distinguish message types - commands are green, errors are red, etc ([#207](https://github.com/go-task/task/issues/207)).
+- Expose `.TASK` variable in templates with the task name (#252).
+- Implement short task syntax (#194, #240).
+- Added option to make included Taskfile run commands on its own directory (#260, #144)
+- Taskfiles in version 1 are not supported anymore (#237).
+- Added global `method:` option. With this option, you can set a default method to all tasks in a Taskfile (#246).
+- Changed default method from `timestamp` to `checksum` (#246).
+- New magic variables are now available when using `status:`: `.TIMESTAMP` which contains the greatest modification date from the files listed in `sources:`, and `.CHECKSUM`, which contains a checksum of all files listed in `status:`. This is useful for manual checking when using external, or even remote, artifacts when using `status:` (#216).
+- We're now using [slim-sprig](https://github.com/go-task/slim-sprig) instead of [sprig](https://github.com/Masterminds/sprig), which allowed a file size reduction of about 22% (#219).
+- We now use some colors on Task output to better distinguish message types - commands are green, errors are red, etc (#207).
 
 ## v2.8.1 - 2020-05-20
 
-- Fix error code for the `--help` flag ([#300](https://github.com/go-task/task/issues/300), [#330](https://github.com/go-task/task/issues/330)).
-- Print version to stdout instead of stderr ([#299](https://github.com/go-task/task/issues/299), [#329](https://github.com/go-task/task/issues/329)).
-- Supress `context` errors when using the `--watch` flag ([#313](https://github.com/go-task/task/issues/313), [#317](https://github.com/go-task/task/issues/317)).
-- Support templating on description ([#276](https://github.com/go-task/task/issues/276), [#283](https://github.com/go-task/task/issues/283)).
+- Fix error code for the `--help` flag (#300, #330).
+- Print version to stdout instead of stderr (#299, #329).
+- Supress `context` errors when using the `--watch` flag (#313, #317).
+- Support templating on description (#276, #283).
 
 ## v2.8.0 - 2019-12-07
 
-- Add `--parallel` flag (alias `-p`) to run tasks given by the command line in parallel ([#266](https://github.com/go-task/task/issues/266)).
+- Add `--parallel` flag (alias `-p`) to run tasks given by the command line in parallel (#266).
 - Fixed bug where calling the `task` CLI only informing global vars would not execute the `default` task.
 - Add hability to silent all tasks by adding `silent: true` a the root of the Taskfile.
 
 ## v2.7.1 - 2019-11-10
 
-- Fix error being raised when `exit 0` was called ([#251](https://github.com/go-task/task/issues/251)).
+- Fix error being raised when `exit 0` was called (#251).
 
 ## v2.7.0 - 2019-09-22
 
-- Fixed panic bug when assigning a global variable ([#229](https://github.com/go-task/task/issues/229), [#243](https://github.com/go-task/task/issues/243)).
-- A task with `method: checksum` will now re-run if generated files are deleted ([#228](https://github.com/go-task/task/issues/228), [#238](https://github.com/go-task/task/issues/238)).
+- Fixed panic bug when assigning a global variable (#229, #243).
+- A task with `method: checksum` will now re-run if generated files are deleted (#228, #238).
 
 ## v2.6.0 - 2019-07-21
 
 - Fixed some bugs regarding minor version checks on `version:`.
-- Add `preconditions:` to task ([#205](https://github.com/go-task/task/issues/205)).
-- Create directory informed on `dir:` if it doesn't exist ([#209](https://github.com/go-task/task/issues/209), [#211](https://github.com/go-task/task/issues/211)).
-- We now have a `--taskfile` flag (alias `-t`), which can be used to run another Taskfile (other than the default `Taskfile.yml`) ([#221](https://github.com/go-task/task/issues/221)).
-- It's now possible to install Task using Homebrew on Linux ([go-task/homebrew-tap\[#1\](https://github.com/go-task/task/issues/1)](https://github.com/go-task/homebrew-tap/pull/1)).
+- Add `preconditions:` to task (#205).
+- Create directory informed on `dir:` if it doesn't exist (#209, #211).
+- We now have a `--taskfile` flag (alias `-t`), which can be used to run another Taskfile (other than the default `Taskfile.yml`) (#221).
+- It's now possible to install Task using Homebrew on Linux ([go-task/homebrew-tap#1](https://github.com/go-task/homebrew-tap/pull/1)).
 
 ## v2.5.2 - 2019-05-11
 
-- Reverted YAML upgrade due issues with CRLF on Windows ([#201](https://github.com/go-task/task/issues/201), [go-yaml/yaml\[#450\](https://github.com/go-task/task/issues/450)](https://github.com/go-yaml/yaml/issues/450)).
-- Allow setting global variables through the CLI ([#192](https://github.com/go-task/task/issues/192)).
+- Reverted YAML upgrade due issues with CRLF on Windows (#201, [go-yaml/yaml#450](https://github.com/go-yaml/yaml/issues/450)).
+- Allow setting global variables through the CLI (#192).
 
 ## 2.5.1 - 2019-04-27
 
-- Fixed some issues with interactive command line tools, where sometimes the output were not being shown, and similar issues ([#114](https://github.com/go-task/task/issues/114), [#190](https://github.com/go-task/task/issues/190), [#200](https://github.com/go-task/task/issues/200)).
+- Fixed some issues with interactive command line tools, where sometimes the output were not being shown, and similar issues (#114, #190, #200).
 - Upgraded [go-yaml/yaml](https://github.com/go-yaml/yaml) from v2 to v3.
 
 ## v2.5.0 - 2019-03-16
 
 - We moved from the taskfile.org domain to the new fancy taskfile.dev domain. While stuff is being redirected, we strongly recommend to everyone that use [this install script](https://taskfile.dev/#/installation?id=install-script) to use the new taskfile.dev domain on scripts from now on.
-- Fixed to the ZSH completion ([#182](https://github.com/go-task/task/issues/182)).
-- Add [`--summary` flag along with `summary:` task attribute](https://taskfile.org/#/usage?id=display-summary-of-task) ([#180](https://github.com/go-task/task/issues/180)).
+- Fixed to the ZSH completion (#182).
+- Add [`--summary` flag along with `summary:` task attribute](https://taskfile.org/#/usage?id=display-summary-of-task) (#180).
 
 ## v2.4.0 - 2019-02-21
 
-- Allow calling a task of the root Taskfile from an included Taskfile by prefixing it with `:` ([#161](https://github.com/go-task/task/issues/161), [#172](https://github.com/go-task/task/issues/172)).
-- Add flag to override the `output` option ([#173](https://github.com/go-task/task/issues/173)).
-- Fix bug where Task was persisting the new checksum on the disk when the Dry Mode is enabled ([#166](https://github.com/go-task/task/issues/166)).
-- Fix file timestamp issue when the file name has spaces ([#176](https://github.com/go-task/task/issues/176)).
-- Mitigating path expanding issues on Windows ([#170](https://github.com/go-task/task/issues/170)).
+- Allow calling a task of the root Taskfile from an included Taskfile by prefixing it with `:` (#161, #172).
+- Add flag to override the `output` option (#173).
+- Fix bug where Task was persisting the new checksum on the disk when the Dry Mode is enabled (#166).
+- Fix file timestamp issue when the file name has spaces (#176).
+- Mitigating path expanding issues on Windows (#170).
 
 ## v2.3.0 - 2019-01-02
 
-- On Windows, Task can now be installed using [Scoop](https://scoop.sh/) ([#152](https://github.com/go-task/task/issues/152)).
-- Fixed issue with file/directory globing ([#153](https://github.com/go-task/task/issues/153)).
-- Added ability to globally set environment variables ([#138](https://github.com/go-task/task/issues/138), [#159](https://github.com/go-task/task/issues/159)).
+- On Windows, Task can now be installed using [Scoop](https://scoop.sh/) (#152).
+- Fixed issue with file/directory globing (#153).
+- Added ability to globally set environment variables (#138, #159).
 
 ## v2.2.1 - 2018-12-09
 
-- This repository now uses Go Modules ([#143](https://github.com/go-task/task/issues/143)). We'll still keep the `vendor` directory in sync for some time, though;
-- Fixing a bug when the Taskfile has no tasks but includes another Taskfile ([#150](https://github.com/go-task/task/issues/150));
-- Fix a bug when calling another task or a dependency in an included Taskfile ([#151](https://github.com/go-task/task/issues/151)).
+- This repository now uses Go Modules (#143). We'll still keep the `vendor` directory in sync for some time, though;
+- Fixing a bug when the Taskfile has no tasks but includes another Taskfile (#150);
+- Fix a bug when calling another task or a dependency in an included Taskfile (#151).
 
 ## v2.2.0 - 2018-10-25
 
-- Added support for [including other Taskfiles](https://taskfile.org/#/usage?id=including-other-taskfiles) ([#98](https://github.com/go-task/task/issues/98))
-  - This should be considered experimental. For now, only including local files is supported, but support for including remote Taskfiles is being discussed. If you have any feedback, please comment on [#98](https://github.com/go-task/task/issues/98).
+- Added support for [including other Taskfiles](https://taskfile.org/#/usage?id=including-other-taskfiles) (#98)
+  - This should be considered experimental. For now, only including local files is supported, but support for including remote Taskfiles is being discussed. If you have any feedback, please comment on #98.
 - Task now have a dedicated documentation site: https://taskfile.org
   - Thanks to [Docsify](https://docsify.js.org/) for making this pretty easy. To check the source code, just take a look at the [docs](https://github.com/go-task/task/tree/main/docs) directory of this repository. Contributions to the documentation is really appreciated.
 
 ## v2.1.1 - 2018-09-17
 
 - Fix suggestion to use `task --init` not being shown anymore (when a `Taskfile.yml` is not found)
-- Fix error when using checksum method and no file exists for a source glob ([#131](https://github.com/go-task/task/issues/131))
-- Fix signal handling when the `--watch` flag is given ([#132](https://github.com/go-task/task/issues/132))
+- Fix error when using checksum method and no file exists for a source glob (#131)
+- Fix signal handling when the `--watch` flag is given (#132)
 
 ## v2.1.0 - 2018-08-19
 
-- Add a `ignore_error` option to task and command ([#123](https://github.com/go-task/task/issues/123))
-- Add a dry run mode (`--dry` flag) ([#126](https://github.com/go-task/task/issues/126))
+- Add a `ignore_error` option to task and command (#123)
+- Add a dry run mode (`--dry` flag) (#126)
 
 ## v2.0.3 - 2018-06-24
 
-- Expand environment variables on "dir", "sources" and "generates" ([#116](https://github.com/go-task/task/issues/116))
-- Fix YAML merging syntax ([#112](https://github.com/go-task/task/issues/112))
-- Add ZSH completion ([#111](https://github.com/go-task/task/issues/111))
+- Expand environment variables on "dir", "sources" and "generates" (#116)
+- Fix YAML merging syntax (#112)
+- Add ZSH completion (#111)
 - Implement new `output` option. Please check out the [documentation](https://github.com/go-task/task#output-syntax)
 
 ## v2.0.2 - 2018-05-01
 
-- Fix merging of YAML anchors ([#112](https://github.com/go-task/task/issues/112))
+- Fix merging of YAML anchors (#112)
 
 ## v2.0.1 - 2018-03-11
 
@@ -400,36 +479,36 @@ Version 2.0.0 is here, with a new Taskfile format.
 
 Please, make sure to read the [Taskfile versions](https://github.com/go-task/task/blob/main/TASKFILE_VERSIONS.md) document, since it describes in depth what changed for this version.
 
-- New Taskfile version 2 ([#77](https://github.com/go-task/task/issues/77))
-- Possibility to have global variables in the `Taskfile.yml` instead of `Taskvars.yml` ([#66](https://github.com/go-task/task/issues/66))
+- New Taskfile version 2 (#77)
+- Possibility to have global variables in the `Taskfile.yml` instead of `Taskvars.yml` (#66)
 - Small improvements and fixes
 
 ## v1.4.4 - 2017-11-19
 
-- Handle SIGINT and SIGTERM ([#75](https://github.com/go-task/task/issues/75));
+- Handle SIGINT and SIGTERM (#75);
 - List: print message with there's no task with description;
-- Expand home dir ("~" symbol) on paths ([#74](https://github.com/go-task/task/issues/74));
+- Expand home dir ("~" symbol) on paths (#74);
 - Add Snap as an installation method;
 - Move examples to its own repo;
 - Watch: also walk on tasks called on on "cmds", and not only on "deps";
-- Print logs to stderr instead of stdout ([#68](https://github.com/go-task/task/issues/68));
+- Print logs to stderr instead of stdout (#68);
 - Remove deprecated `set` keyword;
 - Add checksum based status check, alternative to timestamp based.
 
 ## v1.4.3 - 2017-09-07
 
-- Allow assigning variables to tasks at run time via CLI ([#33](https://github.com/go-task/task/issues/33))
-- Added suport for multiline variables from sh ([#64](https://github.com/go-task/task/issues/64))
-- Fixes env: remove square braces and evaluate shell ([#62](https://github.com/go-task/task/issues/62))
+- Allow assigning variables to tasks at run time via CLI (#33)
+- Added suport for multiline variables from sh (#64)
+- Fixes env: remove square braces and evaluate shell (#62)
 - Watch: change watch library and few fixes and improvements
-- When use watching, cancel and restart long running process on file change ([#59](https://github.com/go-task/task/issues/59) and [#60](https://github.com/go-task/task/issues/60))
+- When use watching, cancel and restart long running process on file change (#59 and #60)
 
 ## v1.4.2 - 2017-07-30
 
 - Flag to set directory of execution
 - Always echo command if is verbose mode
 - Add silent mode to disable echoing of commands
-- Fixes and improvements of variables ([#56](https://github.com/go-task/task/issues/56))
+- Fixes and improvements of variables (#56)
 
 ## v1.4.1 - 2017-07-15
 
@@ -437,28 +516,28 @@ Please, make sure to read the [Taskfile versions](https://github.com/go-task/tas
   - `VAR: {sh: echo Hello}` instead of `VAR: $echo Hello`
 - Add `--list` (or `-l`) flag to print existing tasks
 - OS specific Taskvars file (e.g. `Taskvars_windows.yml`, `Taskvars_linux.yml`, etc)
-- Consider task up-to-date on equal timestamps ([#49](https://github.com/go-task/task/issues/49))
-- Allow absolute path in generates section ([#48](https://github.com/go-task/task/issues/48))
-- Bugfix: allow templating when calling deps ([#42](https://github.com/go-task/task/issues/42))
+- Consider task up-to-date on equal timestamps (#49)
+- Allow absolute path in generates section (#48)
+- Bugfix: allow templating when calling deps (#42)
 - Fix panic for invalid task in cyclic dep detection
-- Better error output for dynamic variables in Taskvars.yml ([#41](https://github.com/go-task/task/issues/41))
+- Better error output for dynamic variables in Taskvars.yml (#41)
 - Allow template evaluation in parameters
 
 ## v1.4.0 - 2017-07-06
 
 - Cache dynamic variables
 - Add verbose mode (`-v` flag)
-- Support to task parameters (overriding vars) ([#31](https://github.com/go-task/task/issues/31)) ([#32](https://github.com/go-task/task/issues/32))
-- Print command, also when "set:" is specified ([#35](https://github.com/go-task/task/issues/35))
-- Improve task command help text ([#35](https://github.com/go-task/task/issues/35))
+- Support to task parameters (overriding vars) (#31) (#32)
+- Print command, also when "set:" is specified (#35)
+- Improve task command help text (#35)
 
 ## v1.3.1 - 2017-06-14
 
-- Fix glob not working on commands ([#28](https://github.com/go-task/task/issues/28))
+- Fix glob not working on commands (#28)
 - Add ExeExt template function
 - Add `--init` flag to create a new Taskfile
-- Add status option to prevent task from running ([#27](https://github.com/go-task/task/issues/27))
-- Allow interpolation on `generates` and `sources` attributes ([#26](https://github.com/go-task/task/issues/26))
+- Add status option to prevent task from running (#27)
+- Allow interpolation on `generates` and `sources` attributes (#26)
 
 ## v1.3.0 - 2017-04-24
 
@@ -476,18 +555,18 @@ Please, make sure to read the [Taskfile versions](https://github.com/go-task/tas
 - Watch a task (experimental)
 - Possibility to call another task
 - Fix "=" not being reconized in variables/environment variables
-- Tasks can now have a description, and help will print them ([#10](https://github.com/go-task/task/issues/10))
+- Tasks can now have a description, and help will print them (#10)
 - Task dependencies now run concurrently
-- Support for a default task ([#16](https://github.com/go-task/task/issues/16))
+- Support for a default task (#16)
 
 ## v1.1.0 - 2017-03-08
 
-- Support for YAML, TOML and JSON ([#1](https://github.com/go-task/task/issues/1))
-- Support running command in another directory ([#4](https://github.com/go-task/task/issues/4))
+- Support for YAML, TOML and JSON (#1)
+- Support running command in another directory (#4)
 - `--force` or `-f` flag to force execution of task even when it's up-to-date
-- Detection of cyclic dependencies ([#5](https://github.com/go-task/task/issues/5))
-- Support for variables ([#6](https://github.com/go-task/task/issues/6), [#9](https://github.com/go-task/task/issues/9), [#14](https://github.com/go-task/task/issues/14))
-- Operation System specific commands and variables ([#13](https://github.com/go-task/task/issues/13))
+- Detection of cyclic dependencies (#5)
+- Support for variables (#6, #9, #14)
+- Operation System specific commands and variables (#13)
 
 ## v1.0.0 - 2017-02-28
 

docs/i18n/es-ES/docusaurus-plugin-content-docs/current/community.md

@@ -1,6 +1,6 @@
 ---
 slug: /community/
-sidebar_position: 10
+sidebar_position: 9
 ---
 
 # Community
@@ -19,8 +19,8 @@ Many of our integrations are contributed and maintained by the community. You ca
 
 Some installation methods are maintained by third party:
 
-- [GitHub Actions](https://github.com/arduino/setup-task) by [@arduino](https://github.com/arduino)
-- [AUR](https://aur.archlinux.org/packages/go-task-bin) by [@carlsmedstad](https://github.com/carlsmedstad)
+- [GitHub Actions](https://github.com/arduino/setup-task) by @arduino
+- [AUR](https://aur.archlinux.org/packages/go-task-bin) by @carlsmedstad
 - [Scoop](https://github.com/ScoopInstaller/Main/blob/master/bucket/task.json)
 - [Fedora](https://packages.fedoraproject.org/pkgs/golang-github-task/go-task/)
 - [NixOS](https://github.com/NixOS/nixpkgs/blob/master/pkgs/development/tools/go-task/default.nix)

docs/i18n/es-ES/docusaurus-plugin-content-docs/current/contributing.md

@@ -41,9 +41,9 @@ To run Task for Visual Studio Code, you can open the project in VSCode and hit F
 
 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 docs` (requires `nodejs` & `yarn`). All content is written in Markdown and is located in the `docs/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.md) is necessary. This document contains descriptions and examples of how to use Task features. If you're adding a new feature, try to find an appropriate place to add a new section. If you're updating an existing feature, ensure that the documentation and any examples are up-to-date. Ensure that any examples follow the [Taskfile Styleguide](./styleguide.md).
+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 features. If you're adding a new feature, try to find an appropriate place to add a new section. If you're updating an existing feature, ensure that the documentation and any examples are up-to-date. Ensure that any examples follow the [Taskfile Styleguide](/styleguide).
 
-If you added a new field, command or flag, ensure that you add it to the [API Reference](./api_reference.md). New fields also need to be added to the [JSON Schema][json-schema]. The descriptions for fields in the API reference and the schema should match.
+If you added a new field, command or flag, ensure that you add it to the [API Reference](/api). New fields also need to be added to the [JSON Schema][json-schema]. The descriptions for fields in the API reference and the schema should match.
 
 ### Writing tests
 
@@ -72,7 +72,7 @@ If you're not sure how to format your commit message, check out [Conventional Co
 
 Take a look at the list of [open issues for Task][task-open-issues] or [Task for Visual Studio Code][vscode-task-open-issues]. We have a [good first issue][good-first-issue] label for simpler issues that are ideal for first time contributions.
 
-All kinds of contributions are welcome, whether its a typo fix or a shiny new feature. You can also contribute by upvoting/commenting on issues, helping to answer questions or contributing to other [community projects](./community.md).
+All kinds of contributions are welcome, whether its a typo fix or a shiny new feature. You can also contribute by upvoting/commenting on issues, helping to answer questions or contributing to other [community projects](/community).
 
 > I'm stuck, where can I get help?
 

docs/i18n/es-ES/docusaurus-plugin-content-docs/current/deprecations/deprecations.md

@@ -0,0 +1,12 @@
+---
+slug: /deprecations/
+sidebar_position: 7
+---
+
+# Deprecations
+
+As Task evolves, it occasionally outgrows some of its functionality. This can be because they are no longer useful, because another feature has replaced it or because of a change in the way that Task works internally.
+
+When this happens, we mark the functionality as deprecated. This means that it will be removed in a future version of Task. This functionality will continue to work until that time, but we strongly recommend that you do not implement this functionality in new Taskfiles and make a plan to migrate away from it as soon as possible.
+
+You can view a full list of active deprecations in the "Deprecations" section of the sidebar.

docs/i18n/es-ES/docusaurus-plugin-content-docs/current/deprecations/template.md

@@ -0,0 +1,22 @@
+---
+#This is a template for an experiments documentation
+#Copy this page and fill in the details as necessary
+title: '--- Template ---'
+sidebar_position: -1 #Always push to the top
+draft: true #Hide in production
+---
+
+# \{Name of Deprecated Feature\} (#\{Issue\})
+
+:::warning
+
+This deprecation breaks the following functionality:
+
+- \{list any existing functionality that will be broken by this deprecation\}
+- \{if there are no breaking changes, remove this admonition\}
+
+:::
+
+\{Short description of the feature/behavior and why it is being deprecated\}
+
+\{Short explanation of any replacement features/behaviors and how users should migrate to it\}

docs/i18n/es-ES/docusaurus-plugin-content-docs/current/deprecations/version_2_schema.md

@@ -0,0 +1,25 @@
+---
+slug: /deprecations/version-2-schema/
+---
+
+# Version 2 Schema (#1197)
+
+:::warning
+
+This deprecation breaks the following functionality:
+
+- Any Taskfiles that use the version 2 schema
+- `Taskvar.yml` files
+
+:::
+
+The Taskfile version 2 schema was introduced in March 2018 and replaced by version 3 in August 2019. In May 2023 [we published a deprecation notice][deprecation-notice] for the version 2 schema on the basis that the vast majority of users had already upgraded to version 3 and removing support for version 2 would allow us to tidy up the codebase and focus on new functionality instead.
+
+In December 2023, the final version of Task that supports the version 2 schema ([v3.33.0][v3.33.0]) was published and all legacy code was removed from Task's main branch. To use a more recent version of Task, you will need to ensure that your Taskfile uses the version 3 schema instead. A list of changes between version 2 and version 3 are available in the [Task v3 Release Notes][v3.0.0].
+
+<!-- prettier-ignore-start -->
+
+<!-- prettier-ignore-end -->
+[v3.0.0]: https://github.com/go-task/task/releases/tag/v3.0.0
+[v3.33.0]: https://github.com/go-task/task/releases/tag/v3.33.0
+[deprecation-notice]: https://github.com/go-task/task/issues/1197

docs/i18n/es-ES/docusaurus-plugin-content-docs/current/donate.md

@@ -1,6 +1,6 @@
 ---
 slug: /donate/
-sidebar_position: 15
+sidebar_position: 16
 ---
 
 # Donate
@@ -13,7 +13,7 @@ Companies who donate at least $50/month will be featured as a "Gold Sponsor" in
 
 ## GitHub Sponsors
 
-The preferred way to donate to the maintainers is via GitHub Sponsors. Just use the following links to do your donation:
+The preferred way to donate to the maintainers is via GitHub Sponsors. Just use the following links to do your donation. We suggest a 50/50 split to each maintainer of the total amount you plan to donate to the project.
 
 - [@andreynering](https://github.com/sponsors/andreynering)
 - [@pd93](https://github.com/sponsors/pd93)

docs/i18n/es-ES/docusaurus-plugin-content-docs/current/experiments/any_variables.md

@@ -0,0 +1,206 @@
+---
+slug: /experiments/any-variables/
+---
+
+# Any Variables (#1415)
+
+:::caution
+
+All experimental features are subject to breaking changes and/or removal _at any
+time_. We strongly recommend that you do not use these features in a production
+environment. They are intended for testing and feedback only.
+
+:::
+
+:::warning
+
+This experiment breaks the following functionality:
+
+- Dynamically defined variables (using the `sh` keyword)
+
+:::
+
+:::info
+
+To enable this experiment, set the environment variable:
+`TASK_X_ANY_VARIABLES=1`. Check out [our guide to enabling experiments
+][enabling-experiments] for more information.
+
+:::
+
+Currently, Task only supports string variables. This experiment allows you to
+specify and use the following variable types:
+
+- `string`
+- `bool`
+- `int`
+- `float`
+- `array`
+- `map`
+
+This allows you to have a lot more flexibility in how you use variables in
+Task's templating engine. For example:
+
+Evaluating booleans:
+
+```yaml
+version: 3
+
+tasks:
+  foo:
+    vars:
+      BOOL: false
+    cmds:
+      - '{{if .BOOL}}echo foo{{end}}'
+```
+
+Arithmetic:
+
+```yaml
+version: 3
+
+tasks:
+  foo:
+    vars:
+      INT: 10
+      FLOAT: 3.14159
+    cmds:
+      - 'echo {{add .INT .FLOAT}}'
+```
+
+Ranging:
+
+```yaml
+version: 3
+
+tasks:
+  foo:
+    vars:
+      ARRAY: [1, 2, 3]
+    cmds:
+      - 'echo {{range .ARRAY}}{{.}}{{end}}'
+```
+
+There are many more templating functions which can be used with the new types of
+variables. For a full list, see the [slim-sprig][slim-sprig] documentation.
+
+## Looping over variables
+
+Previously, you would have to use a delimiter separated string to loop over an
+arbitrary list of items in a variable and split them by using the `split` subkey
+to specify the delimiter:
+
+```yaml
+version: 3
+
+tasks:
+  foo:
+    vars:
+      LIST: 'foo,bar,baz'
+    cmds:
+      - for:
+          var: LIST
+          split: ','
+        cmd: echo {{.ITEM}}
+```
+
+Because this experiment adds support for "collection-type" variables, the `for`
+keyword has been updated to support looping over arrays directly:
+
+```yaml
+version: 3
+
+tasks:
+  foo:
+    vars:
+      LIST: [foo, bar, baz]
+    cmds:
+      - for:
+          var: LIST
+        cmd: echo {{.ITEM}}
+```
+
+This also works for maps. When looping over a map we also make an additional
+`{{.KEY}}` variable availabe that holds the string value of the map key.
+Remember that maps are unordered, so the order in which the items are looped
+over is random:
+
+```yaml
+version: 3
+
+tasks:
+  foo:
+    vars:
+      MAP:
+        KEY_1:
+          SUBKEY: sub_value_1
+        KEY_2:
+          SUBKEY: sub_value_2
+        KEY_3:
+          SUBKEY: sub_value_3
+    cmds:
+      - for:
+          var: MAP
+        cmd: echo {{.KEY}} {{.ITEM.SUBKEY}}
+```
+
+String splitting is still supported and remember that for simple cases, you have
+always been able to loop over an array without using variables at all:
+
+```yaml
+version: 3
+
+tasks:
+  foo:
+    cmds:
+      - for: [foo, bar, baz]
+        cmd: echo {{.ITEM}}
+```
+
+## Migration
+
+Taskfiles with dynamically defined variables via the `sh` subkey will no longer
+work with this experiment enabled. In order to keep using dynamically defined
+variables, you will need to migrate your Taskfile to use the new syntax.
+
+Previously, you might have defined a dynamic variable like this:
+
+```yaml
+version: 3
+
+task:
+  foo:
+    vars:
+      CALCULATED_VAR:
+        sh: 'echo hello'
+    cmds:
+      - 'echo {{.CALCULATED_VAR}}'
+```
+
+With this experiment enabled, you will need to remove the `sh` subkey and define
+your command as a string that begins with a `$`. This will instruct Task to
+interpret the string as a command instead of a literal value and the variable
+will be populated with the output of the command. For example:
+
+```yaml
+version: 3
+
+task:
+  foo:
+    vars:
+      CALCULATED_VAR: '$echo hello'
+    cmds:
+      - 'echo {{.CALCULATED_VAR}}'
+```
+
+If your current Taskfile contains a string variable that begins with a `$`, you
+will now need to escape the `$` with a backslash (`\`) to stop Task from
+executing it as a command.
+
+<!-- prettier-ignore-start -->
+
+[enabling-experiments]: /experiments/#enabling-experiments
+
+[slim-sprig]: https://go-task.github.io/slim-sprig/
+
+<!-- prettier-ignore-end -->

docs/i18n/es-ES/docusaurus-plugin-content-docs/current/experiments/any_variables.mdx

@@ -0,0 +1,162 @@
+---
+slug: /experiments/any-variables/
+---
+
+# Any Variables
+
+-   Issue: #1415
+-   Environment variable: `TASK_X_ANY_VARIABLES=1`
+-   Breaks:
+    -   Dynamically defined variables (using the `sh` keyword)
+
+Currently, Task only supports string variables. This experiment allows you to
+specify and use the following variable types:
+
+-   `string`
+-   `bool`
+-   `int`
+-   `float`
+-   `array`
+-   `map`
+
+This allows you to have a lot more flexibility in how you use variables in
+Task's templating engine. For example:
+
+Evaluating booleans:
+
+```yaml
+version: 3
+
+tasks:
+  foo:
+    vars:
+      BOOL: false
+    cmds:
+      - '{{if .BOOL}}echo foo{{end}}'
+```
+
+Arithmetic:
+
+```yaml
+version: 3
+
+tasks:
+  foo:
+    vars:
+      INT: 10
+      FLOAT: 3.14159
+    cmds:
+      - 'echo {{add .INT .FLOAT}}'
+```
+
+Ranging:
+
+```yaml
+version: 3
+
+tasks:
+  foo:
+    vars:
+      ARRAY: [1, 2, 3]
+    cmds:
+      - 'echo {{range .ARRAY}}{{.}}{{end}}'
+```
+
+There are many more templating functions which can be used with the new types of
+variables. For a full list, see the
+[slim-sprig][slim-sprig] documentation.
+
+## Looping over variables
+
+Previously, you would have to use a delimiter separated string to loop over an
+arbitrary list of items in a variable and split them by using the `split` subkey
+to specify the delimiter:
+
+```yaml
+version: 3
+
+tasks:
+  foo:
+    vars:
+      LIST: 'foo,bar,baz'
+    cmds:
+      - for:
+          var: LIST
+          split: ','
+        cmd: echo {{.ITEM}}
+```
+
+Because this experiment adds support for array variables, the `for` keyword has
+been updated to support looping over arrays directly:
+
+```yaml
+version: 3
+
+tasks:
+  foo:
+    vars:
+      LIST: [foo, bar, baz]
+    cmds:
+      - for:
+          var: LIST
+        cmd: echo {{.ITEM}}
+```
+
+String splitting is still supported and remember that for simple cases, you have
+always been able to loop over an array without using variables at all:
+
+```yaml
+version: 3
+
+tasks:
+  foo:
+    cmds:
+      - for: [foo, bar, baz]
+        cmd: echo {{.ITEM}}
+```
+
+## Migration
+
+Taskfiles with dynamically defined variables via the `sh` subkey will no longer
+work with this experiment enabled. In order to keep using dynamically defined
+variables, you will need to migrate your Taskfile to use the new syntax.
+
+Previously, you might have defined a dynamic variable like this:
+
+```yaml
+version: 3
+
+task:
+  foo:
+    vars:
+      CALCULATED_VAR:
+        sh: 'echo hello'
+    cmds:
+      - 'echo {{.CALCULATED_VAR}}'
+```
+
+With this experiment enabled, you will need to remove the `sh` subkey and define
+your command as a string that begins with a `$`. This will instruct Task to
+interpret the string as a command instead of a literal value and the variable
+will be populated with the output of the command. For example:
+
+```yaml
+version: 3
+
+task:
+  foo:
+    vars:
+      CALCULATED_VAR: '$echo hello'
+    cmds:
+      - 'echo {{.CALCULATED_VAR}}'
+```
+
+If your current Taskfile contains a string variable that begins with a `$`, you
+will now need to escape the `$` with a backslash (`\`) to stop Task from
+executing it as a command.
+
+<!-- prettier-ignore-start -->
+
+[slim-sprig]: https://go-task.github.io/slim-sprig/
+
+<!-- prettier-ignore-end -->

docs/i18n/es-ES/docusaurus-plugin-content-docs/current/experiments/experiments.md

@@ -1,6 +1,6 @@
 ---
 slug: /experiments/
-sidebar_position: 5
+sidebar_position: 6
 ---
 
 # Experiments
@@ -11,16 +11,19 @@ All experimental features are subject to breaking changes and/or removal _at any
 
 :::
 
-In order to allow Task to evolve quickly, we roll out breaking changes to minor versions behind experimental flags. This allows us to gather feedback on breaking changes before committing to a major release. This document describes the current set of experimental features and the deprecated feature that they are intended to replace.
+In order to allow Task to evolve quickly, we roll out breaking changes to minor versions behind experimental flags. This allows us to gather feedback on breaking changes before committing to a major release. This document describes the current set of experimental features and their status in the [workflow](#workflow).
 
-You can enable an experimental feature by:
+You can view a full list of active experiments in the "Experiments" section of the sidebar.
+
+## Enabling Experiments
+
+You can enable an experimental feature by doing one of the following:
 
 1. Using the relevant environment variable in front of a task command. For example, `TASK_X_{FEATURE}=1 task {my-task}`. This is intended for one-off invocations of Task to test out experimental features.
 1. Using the relevant environment variable in your "dotfiles" (e.g. `.bashrc`, `.zshrc` etc.). This is intended for permanently enabling experimental features in your environment.
-1. Creating a `.env` file in the same directory as your root Taskfile that contains the relevant environment variables. e.g.
+1. Creating a `.env` file in the same directory as your root Taskfile that contains the relevant environment variables. This allows you to enable an experimental feature at a project level. For example:
 
-```shell
-# .env
+```shell title=".env"
 TASK_X_FEATURE=1
 ```
 
@@ -28,43 +31,49 @@ TASK_X_FEATURE=1
 
 Each section below details an experiment or deprecation and explains what the flags/environment variables to enable the experiment are and how the feature's behavior will change. It will also explain what you need to do to migrate any existing Taskfiles to the new behavior.
 
-<!-- EXPERIMENT TEMPLATE - Include sections as necessary...
+## Workflow
 
-### ![experiment] {Feature} ([#{issue}](https://github.com/go-task/task/issues/{issue})), ...)
+Experiments are a way for us to test out new features in Task before committing to them in a major release. Because this concept is built around the idea of feedback from our community, we have built a workflow for the process of introducing these changes. This ensures that experiments are given the attention and time that they need and that we are getting the best possible results out of them.
 
-- Environment variable: `TASK_X_{feature}`
-- Deprecates: {list any existing functionality that will be deprecated by this experiment}
-- Breaks: {list any existing functionality that will be broken by this experiment}
+The sections below describe the various stages that an experiment must go through from its proposal all the way to being released in a major version of Task.
 
-{Short description of the feature}
+### 1. Proposal
 
-{Short explanation of how users should migrate to the new behavior}
+All experimental features start with a proposal in the form of a GitHub issue. If the maintainers decide that an issue has enough support and is a breaking change or is complex/controversial enough to require user feedback, then the issue will be marked with the ![proposal][] label. At this point, the issue becomes a proposal and a period of consultation begins. During this period, we request that users provide feedback on the proposal and how it might effect their use of Task. It is up to the discretion of the maintainers to decide how long this period lasts.
 
--->
+### 2. Draft
 
-### ![deprecated][] Version 2 Schema ([#1197][deprecate-version-2-schema])
+Once a proposal's consultation ends, a contributor may pick up the work and begin the initial implementation. Once a PR is opened, the maintainers will ensure that it meets the requirements for an experimental feature (i.e. flags are in the right format etc) and merge the feature. Once this code is released, the status will be updated via the ![draft][] label. This indicates that an implementation is now available for use in a release and the experiment is open for feedback.
 
-The Taskfile v2 schema was introduced in March 2018 and replaced by version 3 in August the following year. Users have had a long time to update and so we feel that it is time to tidy up the codebase and focus on new functionality instead.
+:::note
 
-This notice does not mean that we are immediately removing support for version 2 schemas. However, support will not be extended to future major releases and we _strongly recommend_ that anybody still using a version 2 schema upgrades to version 3 as soon as possible.
+During the draft period, major changes to the implementation may be made based on the feedback received from users. There are _no stability guarantees_ and experimental features may be abandoned _at any time_.
 
-A list of changes between version 2 and version 3 are available in the [Task v3 Release Notes][version-3-release-notes].
+:::
 
-### ![experiment][] Gentle Force ([#1200](https://github.com/go-task/task/issues/1200))
+### 3. Candidate
 
-- Environment variable: `TASK_X_FORCE=1`
-- Breaks: `--force` flag
+Once an acceptable level of consensus has been reached by the community and feedback/changes are less frequent/significant, the status may be updated via the ![candidate][] label. This indicates that a proposal is _likely_ to accepted and will enter a period for final comments and minor changes.
 
-The `--force` flag currently forces _all_ tasks to run regardless of the status checks. This can be useful, but we have found that most of the time users only expect the direct task they are calling to be forced and _not_ all of its dependant tasks.
+### 4. Stable
 
-This experiment changes the `--force` flag to only force the directly called task. All dependant tasks will have their statuses checked as normal and will only run if Task considers them to be out of date. A new `--force-all` flag will also be added to maintain the current behavior for users that need this functionality.
+Once a suitable amount of time has passed with no changes or feedback, an experiment will be given the ![stable][] label. At this point, the functionality will be treated like any other feature in Task and any changes _must_ be backward compatible. This allows users to migrate to the new functionality without having to worry about anything breaking in future releases. This provides the best experience for users migrating to a new major version.
 
-If you want to migrate, but continue to force all dependant tasks to run, you should replace all uses of the `--force` flag with `--force-all`. Alternatively, if you want to adopt the new behavior, you can continue to use the `--force` flag as you do now!
+### 5. Released
+
+When making a new major release of Task, all experiments marked as ![stable][] will move to ![released][] and their behaviors will become the new default in Task. Experiments in an earlier stage (i.e. not stable) cannot be released and so will continue to be experiments in the new version.
+
+### Abandoned / Superseded
+
+If an experiment is unsuccessful at any point then it will be given the ![abandoned][] or ![superseded][] labels depending on which is more suitable. These experiments will be removed from Task.
 
 <!-- prettier-ignore-start -->
 
 <!-- prettier-ignore-end -->
-[deprecate-version-2-schema]: https://github.com/go-task/task/issues/1197
-[version-3-release-notes]: https://github.com/go-task/task/releases/tag/v3.0.0
-[deprecated]: https://img.shields.io/badge/deprecated-red
-[experiment]: https://img.shields.io/badge/experiment-yellow
+[proposal]: https://img.shields.io/badge/experiment:%20proposal-purple
+[draft]: https://img.shields.io/badge/experiment:%20draft-purple
+[candidate]: https://img.shields.io/badge/experiment:%20candidate-purple
+[stable]: https://img.shields.io/badge/experiment:%20stable-purple
+[released]: https://img.shields.io/badge/experiment:%20released-purple
+[abandoned]: https://img.shields.io/badge/experiment:%20abandoned-purple
+[superseded]: https://img.shields.io/badge/experiment:%20superseded-purple

docs/i18n/es-ES/docusaurus-plugin-content-docs/current/experiments/gentle_force.md

@@ -0,0 +1,36 @@
+---
+slug: /experiments/gentle-force/
+---
+
+# Gentle Force (#1200)
+
+:::caution
+
+All experimental features are subject to breaking changes and/or removal _at any time_. We strongly recommend that you do not use these features in a production environment. They are intended for testing and feedback only.
+
+:::
+
+:::warning
+
+This experiment breaks the following functionality:
+
+- The `--force` flag
+
+:::
+
+:::info
+
+To enable this experiment, set the environment variable: `TASK_X_FORCE=1`. Check out [our guide to enabling experiments ][enabling-experiments] for more information.
+
+:::
+
+The `--force` flag currently forces _all_ tasks to run regardless of the status checks. This can be useful, but we have found that most of the time users only expect the direct task they are calling to be forced and _not_ all of its dependant tasks.
+
+This experiment changes the `--force` flag to only force the directly called task. All dependant tasks will have their statuses checked as normal and will only run if Task considers them to be out of date. A new `--force-all` flag will also be added to maintain the current behavior for users that need this functionality.
+
+If you want to migrate, but continue to force all dependant tasks to run, you should replace all uses of the `--force` flag with `--force-all`. Alternatively, if you want to adopt the new behavior, you can continue to use the `--force` flag as you do now!
+
+<!-- prettier-ignore-start -->
+
+<!-- prettier-ignore-end -->
+[enabling-experiments]: /experiments/#enabling-experiments

docs/i18n/es-ES/docusaurus-plugin-content-docs/current/experiments/remote_taskfiles.md

@@ -0,0 +1,66 @@
+---
+slug: /experiments/remote-taskfiles/
+---
+
+# Remote Taskfiles (#1317)
+
+:::caution
+
+All experimental features are subject to breaking changes and/or removal _at any time_. We strongly recommend that you do not use these features in a production environment. They are intended for testing and feedback only.
+
+:::
+
+:::info
+
+To enable this experiment, set the environment variable: `TASK_X_REMOTE_TASKFILES=1`. Check out [our guide to enabling experiments ][enabling-experiments] for more information.
+
+:::
+
+This experiment allows you to specify a remote Taskfile URL when including a Taskfile. For example:
+
+```yaml
+version: '3'
+
+includes:
+  my-remote-namespace: https://raw.githubusercontent.com/my-org/my-repo/main/Taskfile.yml
+```
+
+This works exactly the same way that including a local file does. Any tasks in the remote Taskfile will be available to run from your main Taskfile via the namespace `my-remote-namespace`. For example, if the remote file contains the following:
+
+```yaml
+version: '3'
+
+tasks:
+  hello:
+    silent: true
+    cmds:
+      - echo "Hello from the remote Taskfile!"
+```
+
+and you run `task my-remote-namespace:hello`, it will print the text: "Hello from the remote Taskfile!" to your console.
+
+## Security
+
+Running commands from sources that you do not control is always a potential security risk. For this reason, we have added some checks when using remote Taskfiles:
+
+1. When running a task from a remote Taskfile for the first time, Task will print a warning to the console asking you to check that you are sure that you trust the source of the Taskfile. If you do not accept the prompt, then Task will exit with code `104` (not trusted) and nothing will run. If you accept the prompt, the remote Taskfile will run and further calls to the remote Taskfile will not prompt you again.
+2. Whenever you run a remote Taskfile, Task will create and store a checksum of the file that you are running. If the checksum changes, then Task will print another warning to the console to inform you that the contents of the remote file has changed. If you do not accept the prompt, then Task will exit with code `104` (not trusted) and nothing will run. If you accept the prompt, the checksum will be updated and the remote Taskfile will run.
+
+Sometimes you need to run Task in an environment that does not have an interactive terminal, so you are not able to accept a prompt. In these cases you are able to tell task to accept these prompts automatically by using the `--yes` flag. Before enabling this flag, you should:
+
+1. Be sure that you trust the source and contents of the remote Taskfile.
+2. Consider using a pinned version of the remote Taskfile (e.g. A link containing a commit hash) to prevent Task from automatically accepting a prompt that says a remote Taskfile has changed.
+
+Task currently supports both `http` and `https` URLs. However, the `http` requests will not execute by default unless you run the task with the `--insecure` flag. This is to protect you from accidentally running a remote Taskfile that is hosted on and unencrypted connection. Sources that are not protected by TLS are vulnerable to [man-in-the-middle attacks][man-in-the-middle-attacks] and should be avoided unless you know what you are doing.
+
+## Caching & Running Offline
+
+Whenever you run a remote Taskfile, the latest copy will be downloaded from the internet and cached locally. If for whatever reason, you lose access to the internet, you will still be able to run your tasks by specifying the `--offline` flag. This will tell Task to use the latest cached version of the file instead of trying to download it. You are able to use the `--download` flag to update the cached version of the remote files without running any tasks.
+
+By default, Task will timeout requests to download remote files after 10 seconds and look for a cached copy instead. This timeout can be configured by setting the `--timeout` flag and specifying a duration. For example, `--timeout 5s` will set the timeout to 5 seconds.
+
+<!-- prettier-ignore-start -->
+
+<!-- prettier-ignore-end -->
+[enabling-experiments]: /experiments/#enabling-experiments
+[man-in-the-middle-attacks]: https://en.wikipedia.org/wiki/Man-in-the-middle_attack

docs/i18n/es-ES/docusaurus-plugin-content-docs/current/experiments/template.md

@@ -0,0 +1,39 @@
+---
+#This is a template for an experiments documentation
+#Copy this page and fill in the details as necessary
+title: '--- Template ---'
+sidebar_position: -1 #Always push to the top
+draft: true #Hide in production
+---
+
+# \{Name of Experiment\} (#\{Issue\})
+
+:::caution
+
+All experimental features are subject to breaking changes and/or removal _at any time_. We strongly recommend that you do not use these features in a production environment. They are intended for testing and feedback only.
+
+:::
+
+:::warning
+
+This experiment breaks the following functionality:
+
+- \{list any existing functionality that will be broken by this experiment\}
+- \{if there are no breaking changes, remove this admonition\}
+
+:::
+
+:::info
+
+To enable this experiment, set the environment variable: `TASK_X_{feature}=1`. Check out [our guide to enabling experiments ][enabling-experiments] for more information.
+
+:::
+
+\{Short description of the feature\}
+
+\{Short explanation of how users should migrate to the new behavior\}
+
+<!-- prettier-ignore-start -->
+
+<!-- prettier-ignore-end -->
+[enabling-experiments]: /experiments/#enabling-experiments

docs/i18n/es-ES/docusaurus-plugin-content-docs/current/faq.md

@@ -1,6 +1,6 @@
 ---
 slug: /faq/
-sidebar_position: 7
+sidebar_position: 15
 ---
 
 # FAQ
@@ -78,7 +78,7 @@ The default shell on Windows (`cmd` and `powershell`) do not have commands like
 
 We want to make improvements to this part of Task and the issues below track this work. Constructive comments and contributions are very welcome!
 
-- [#197](https://github.com/go-task/task/issues/197)
+- #197
 - [mvdan/sh#93](https://github.com/mvdan/sh/issues/93)
 - [mvdan/sh#97](https://github.com/mvdan/sh/issues/97)
 

docs/i18n/es-ES/docusaurus-plugin-content-docs/current/installation.md

@@ -17,7 +17,7 @@ If you're on macOS or Linux and have [Homebrew][homebrew] installed, getting Tas
 brew install go-task/tap/go-task
 ```
 
-The above Formula is [maintained by ourselves](https://github.com/go-task/homebrew-tap/blob/master/Formula/go-task.rb).
+The above Formula is [maintained by ourselves](https://github.com/go-task/homebrew-tap/blob/main/Formula/go-task.rb).
 
 Recently, Task was also made available [on the official Homebrew repository](https://formulae.brew.sh/formula/go-task), so you also have that option if you prefer:
 

docs/i18n/es-ES/docusaurus-plugin-content-docs/current/integrations.md

@@ -1,6 +1,6 @@
 ---
 slug: /integrations/
-sidebar_position: 6
+sidebar_position: 8
 ---
 
 # Integrations
@@ -9,7 +9,7 @@ sidebar_position: 6
 
 Task has an [official extension for Visual Studio Code](https://marketplace.visualstudio.com/items?itemName=task.vscode-task). El código de ese proyecto puede ser encontrado [aquí](https://github.com/go-task/vscode-task). Para usar la extensión es necesario tener instalada la versión v3.23.0+ de Task.
 
-This extension provides the following features (and more):
+La extensión proporciona las siguientes funcionalidades (y más...):
 
 - View tasks in the sidebar.
 - Ejecuta tareas desde la barra lateral y la paleta de comandos.
@@ -24,7 +24,7 @@ To get autocompletion and validation for your Taskfile, see the [Schema](#schema
 
 ## Schema
 
-This was initially created by [@KROSF](https://github.com/KROSF) in [this Gist](https://gist.github.com/KROSF/c5435acf590acd632f71bb720f685895) and is now officially maintained in [this file](https://github.com/go-task/task/blob/main/docs/static/schema.json) and made available at https://taskfile.dev/schema.json. This schema can be used to validate Taskfiles and provide autocompletion in many code editors:
+This was initially created by @KROSF in [this Gist](https://gist.github.com/KROSF/c5435acf590acd632f71bb720f685895) and is now officially maintained in [this file](https://github.com/go-task/task/blob/main/docs/static/schema.json) and made available at https://taskfile.dev/schema.json. This schema can be used to validate Taskfiles and provide autocompletion in many code editors:
 
 ### Visual Studio Code
 
@@ -55,8 +55,8 @@ You can find more information on this in the [YAML language server project](http
 
 In addition to our official integrations, there is an amazing community of developers who have created their own integrations for Task:
 
-- [Sublime Text Plugin](https://packagecontrol.io/packages/Taskfile) [[source](https://github.com/biozz/sublime-taskfile)] by [@biozz](https://github.com/biozz)
-- [IntelliJ Plugin](https://plugins.jetbrains.com/plugin/17058-taskfile) [[source](https://github.com/lechuckroh/task-intellij-plugin)] by [@lechuckroh](https://github.com/lechuckroh)
+- [Sublime Text Plugin](https://packagecontrol.io/packages/Taskfile) [[source](https://github.com/biozz/sublime-taskfile)] by @biozz
+- [IntelliJ Plugin](https://plugins.jetbrains.com/plugin/17058-taskfile) [[source](https://github.com/lechuckroh/task-intellij-plugin)] by @lechuckroh
 - [mk](https://github.com/pycontribs/mk) command line tool recognizes Taskfiles natively.
 
 If you have made something that integrates with Task, please feel free to open a PR to add it to this list.

docs/i18n/es-ES/docusaurus-plugin-content-docs/current/intro.md

@@ -14,7 +14,7 @@ Task is a task runner / build tool that aims to be simpler and easier to use tha
 
 Since it's written in [Go][go], Task is just a single binary and has no other dependencies, which means you don't need to mess with any complicated install setups just to use a build tool.
 
-Once [installed](installation.md), you just need to describe your build tasks using a simple [YAML][yaml] schema in a file called `Taskfile.yml`:
+Once [installed](/installation), you just need to describe your build tasks using a simple [YAML][yaml] schema in a file called `Taskfile.yml`:
 
 ```yaml title="Taskfile.yml"
 version: '3'
@@ -32,21 +32,11 @@ The above example is just the start, you can take a look at the [usage](/usage)
 
 ## Features
 
-- [Easy installation](installation.md): just download a single binary, add to `$PATH` and you're done! Or you can also install using [Homebrew][homebrew], [Snapcraft][snapcraft], or [Scoop][scoop] if you want.
-- Available on CIs: by adding [this simple command](installation.md#install-script) to install on your CI script and you're ready to use Task as part of your CI pipeline;
+- [Easy installation](/installation): just download a single binary, add to `$PATH` and you're done! Or you can also install using [Homebrew][homebrew], [Snapcraft][snapcraft], or [Scoop][scoop] if you want.
+- Available on CIs: by adding [this simple command](/installation#install-script) to install on your CI script and you're ready to use Task as part of your CI pipeline;
 - Truly cross-platform: while most build tools only work well on Linux or macOS, Task also supports Windows thanks to [this shell interpreter for Go][sh].
 - Great for code generation: you can easily [prevent a task from running](/usage#prevent-unnecessary-work) if a given set of files haven't changed since last run (based either on its timestamp or content).
 
-## Gold Sponsors
-
-<div class="gold-sponsors">
-
-| [Appwrite](https://appwrite.io/?utm_source=taskfile.dev&utm_medium=website&utm_campaign=task_oss_fund)                       |
-| ---------------------------------------------------------------------------------------------------------------------------- |
-| [![Appwrite](/img/appwrite.svg)](https://appwrite.io/?utm_source=taskfile.dev&utm_medium=website&utm_campaign=task_oss_fund) |
-
-</div>
-
 <!-- prettier-ignore-start -->
 
 <!-- prettier-ignore-end -->

docs/i18n/es-ES/docusaurus-plugin-content-docs/current/releasing.md

@@ -26,6 +26,10 @@ The [snap package][snappackage] requires to manual steps to release a new versio
 - Updating the current version on [snapcraft.yaml][snapcraftyaml].
 - Moving both `amd64`, `armhf` and `arm64` new artifacts to the stable channel on the [Snapcraft dashboard][snapcraftdashboard].
 
+# winget
+
+winget also requires manual steps to be completed. By running `task goreleaser:test` locally, manifest files will be generated on `dist/winget/manifests/t/Task/Task/v{version}`. [Upload the manifest directory into this fork](https://github.com/go-task/winget-pkgs/tree/master/manifests/t/Task/Task) and open a pull request into [this repository](https://github.com/microsoft/winget-pkgs).
+
 # Scoop
 
 Scoop is a command-line package manager for the Windows operating system. Scoop package manifests are maintained by the community. Scoop owners usually take care of updating versions there by editing [this file](https://github.com/ScoopInstaller/Main/blob/master/bucket/task.json). If you think its Task version is outdated, open an issue to let us know.
@@ -39,8 +43,8 @@ Nix is a community owned installation method. Nix package maintainers usually ta
 <!-- prettier-ignore-end -->
 [goreleaser]: https://goreleaser.com/
 [homebrewtap]: https://github.com/go-task/homebrew-tap
-[gotaskrb]: https://github.com/go-task/homebrew-tap/blob/master/Formula/go-task.rb
+[gotaskrb]: https://github.com/go-task/homebrew-tap/blob/main/Formula/go-task.rb
 [packagejson]: https://github.com/go-task/task/blob/main/package.json#L3
 [snappackage]: https://github.com/go-task/snap
-[snapcraftyaml]: https://github.com/go-task/snap/blob/master/snap/snapcraft.yaml#L2
+[snapcraftyaml]: https://github.com/go-task/snap/blob/main/snap/snapcraft.yaml#L2
 [snapcraftdashboard]: https://snapcraft.io/task/releases

docs/i18n/es-ES/docusaurus-plugin-content-docs/current/styleguide.md

@@ -1,6 +1,6 @@
 ---
 slug: /styleguide/
-sidebar_position: 8
+sidebar_position: 10
 ---
 
 # Styleguide
@@ -9,19 +9,6 @@ This is the official Task styleguide for `Taskfile.yml` files. This guide contai
 
 This contains general guidelines, but they don't necessarily need to be strictly followed. Feel free to disagree and proceed differently at some point if you need or want to. Also, feel free to open issues or pull requests with improvements to this guide.
 
-## Use `Taskfile.yml` and not `taskfile.yml`
-
-```yaml
-# bad
-taskfile.yml
-
-
-# good
-Taskfile.yml
-```
-
-This is important especially for Linux users. Windows and macOS have case insensitive filesystems, so `taskfile.yml` will end up working, even that not officially supported. On Linux, only `Taskfile.yml` will work, though.
-
 ## Use the correct order of keywords
 
 - `version:`

docs/i18n/es-ES/docusaurus-plugin-content-docs/current/taskfile_versions.md

@@ -1,6 +1,6 @@
 ---
 slug: /taskfile-versions/
-sidebar_position: 14
+sidebar_position: 5
 ---
 
 # Taskfile Versions
@@ -21,7 +21,7 @@ These are some major changes done on `v3`:
 - Added support for `.env` like files
 - Added `label:` setting to task so one can override how the task name appear in the logs
 - A global `method:` was added to allow setting the default method, and Task's default changed to `checksum`
-- Two magic variables were added when using `status:`: `CHECKSUM` and `TIMESTAMP` which contains, respectively, the md5 checksum and greatest modification timestamp of the files listed on `sources:`
+- Two magic variables were added when using `status:`: `CHECKSUM` and `TIMESTAMP` which contains, respectively, the XXH3 checksum and greatest modification timestamp of the files listed on `sources:`
 - Also, the `TASK` variable is always available with the current task name
 - CLI variables are always treated as global variables
 - Added `dir:` option to `includes` to allow choosing on which directory an included Taskfile will run:
@@ -69,7 +69,7 @@ tasks:
 
 :::caution
 
-v2 schema support is [deprecated][deprecate-version-2-schema] and will be removed in a future release.
+v2 schemas are [no longer supported by the latest version of Task][deprecate-version-2-schema].
 
 :::
 
@@ -92,7 +92,7 @@ Please check the [documentation][includes]
 
 :::caution
 
-v2 schema support is [deprecated][deprecate-version-2-schema] and will be removed in a future release.
+v2 schemas are [no longer supported by the latest version of Task][deprecate-version-2-schema].
 
 :::
 
@@ -110,7 +110,7 @@ includes:
 
 :::caution
 
-v2 schema support is [deprecated][deprecate-version-2-schema] and will be removed in a future release.
+v2 schemas are [no longer supported by the latest version of Task][deprecate-version-2-schema].
 
 :::
 
@@ -151,7 +151,7 @@ tasks:
 
 :::caution
 
-v2 schema support is [deprecated][deprecate-version-2-schema] and will be removed in a future release.
+v2 schemas are [no longer supported by the latest version of Task][deprecate-version-2-schema].
 
 :::
 
@@ -234,7 +234,7 @@ The variable priority order was also different:
 <!-- prettier-ignore-start -->
 
 <!-- prettier-ignore-end -->
-[output]: usage.md#output-syntax
-[ignore_errors]: usage.md#ignore-errors
-[includes]: usage.md#including-other-taskfiles
-[deprecate-version-2-schema]: https://github.com/go-task/task/issues/1197
+[deprecate-version-2-schema]: /deprecations/version-2-schema/
+[output]: /usage#output-syntax
+[ignore_errors]: /usage#ignore-errors
+[includes]: /usage#including-other-taskfiles

docs/i18n/es-ES/docusaurus-plugin-content-docs/current/usage.md

@@ -567,9 +567,23 @@ tasks:
       - public/bundle.css
 ```
 
-`sources` and `generates` can be files or file patterns. When given, Task will compare the checksum of the source files to determine if it's necessary to run the task. If not, it will just print a message like `Task "js" is up to date`.
+`sources` and `generates` can be files or glob patterns. When given, Task will compare the checksum of the source files to determine if it's necessary to run the task. If not, it will just print a message like `Task "js" is up to date`.
 
-If you prefer this check to be made by the modification timestamp of the files, instead of its checksum (content), just set the `method` property to `timestamp`.
+`exclude:` can also be used to exclude files from fingerprinting. Sources are evaluated in order, so `exclude:` must come after the positive glob it is negating.
+
+```yaml
+version: '3'
+
+tasks:
+  css:
+    sources:
+      - mysources/**/*.css
+      - exclude: mysources/ignoreme.css
+    generates:
+      - public/bundle.css
+```
+
+If you prefer these check to be made by the modification timestamp of the files, instead of its checksum (content), just set the `method` property to `timestamp`.
 
 ```yaml
 version: '3'
@@ -764,7 +778,7 @@ Environmental variables are also checked.
 Syntax:
 
 ```yaml
-requires: 
+requires:
   vars: [] # Array of strings
 ```
 
@@ -785,7 +799,7 @@ tasks:
       - 'docker build . -t {{.IMAGE_NAME}}:{{.IMAGE_TAG}}'
 
     # Make sure these variables are set before running
-    requires: 
+    requires:
       vars: [IMAGE_NAME, IMAGE_TAG]
 ```
 
@@ -863,6 +877,162 @@ tasks:
 
 This works for all types of variables.
 
+## Looping over values
+
+As of v3.28.0, Task allows you to loop over certain values and execute a command for each. There are a number of ways to do this depending on the type of value you want to loop over.
+
+### Looping over a static list
+
+The simplest kind of loop is an explicit one. This is useful when you want to loop over a set of values that are known ahead of time.
+
+```yaml
+version: '3'
+
+tasks:
+  default:
+    cmds:
+      - for: ['foo.txt', 'bar.txt']
+        cmd: cat {{ .ITEM }}
+```
+
+### Looping over your task's sources
+
+You are also able to loop over the sources of your task:
+
+```yaml
+version: '3'
+
+tasks:
+  default:
+    sources:
+      - foo.txt
+      - bar.txt
+    cmds:
+      - for: sources
+        cmd: cat {{ .ITEM }}
+```
+
+This will also work if you use globbing syntax in your sources. For example, if you specify a source for `*.txt`, the loop will iterate over all files that match that glob.
+
+Source paths will always be returned as paths relative to the task directory. If you need to convert this to an absolute path, you can use the built-in `joinPath` function. There are some [special variables](/api/#special-variables) that you may find useful for this.
+
+```yaml
+version: '3'
+
+tasks:
+  default:
+    vars:
+      MY_DIR: /path/to/dir
+    dir: '{{.MY_DIR}}'
+    sources:
+      - foo.txt
+      - bar.txt
+    cmds:
+      - for: sources
+        cmd: cat {{joinPath .MY_DIR .ITEM}}
+```
+
+### Looping over variables
+
+To loop over the contents of a variable, you simply need to specify the variable you want to loop over. By default, variables will be split on any whitespace characters.
+
+```yaml
+version: '3'
+
+tasks:
+  default:
+    vars:
+      MY_VAR: foo.txt bar.txt
+    cmds:
+      - for: { var: MY_VAR }
+        cmd: cat {{.ITEM}}
+```
+
+If you need to split on a different character, you can do this by specifying the `split` property:
+
+```yaml
+version: '3'
+
+tasks:
+  default:
+    vars:
+      MY_VAR: foo.txt,bar.txt
+    cmds:
+      - for: { var: MY_VAR, split: ',' }
+        cmd: cat {{.ITEM}}
+```
+
+All of this also works with dynamic variables!
+
+```yaml
+version: '3'
+
+tasks:
+  default:
+    vars:
+      MY_VAR:
+        sh: find -type f -name '*.txt'
+    cmds:
+      - for: { var: MY_VAR }
+        cmd: cat {{.ITEM}}
+```
+
+### Renaming variables
+
+If you want to rename the iterator variable to make it clearer what the value contains, you can do so by specifying the `as` property:
+
+```yaml
+version: '3'
+
+tasks:
+  default:
+    vars:
+      MY_VAR: foo.txt bar.txt
+    cmds:
+      - for: { var: MY_VAR, as: FILE }
+        cmd: cat {{.FILE}}
+```
+
+### Looping over tasks
+
+Because the `for` property is defined at the `cmds` level, you can also use it alongside the `task` keyword to run tasks multiple times with different variables.
+
+```yaml
+version: '3'
+
+tasks:
+  default:
+    cmds:
+      - for: [foo, bar]
+        task: my-task
+        vars:
+          FILE: '{{.ITEM}}'
+
+  my-task:
+    cmds:
+      - echo '{{.FILE}}'
+```
+
+Or if you want to run different tasks depending on the value of the loop:
+
+```yaml
+version: '3'
+
+tasks:
+  default:
+    cmds:
+      - for: [foo, bar]
+        task: task-{{.ITEM}}
+
+  task-foo:
+    cmds:
+      - echo 'foo'
+
+  task-bar:
+    cmds:
+      - echo 'bar'
+```
+
 ## Forwarding CLI arguments to commands
 
 If `--` is given in the CLI, all following parameters are added to a special `.CLI_ARGS` variable. This is useful to forward arguments to another command.
@@ -1128,7 +1298,7 @@ tasks:
 task: "This is a dangerous command... Do you want to continue?" [y/N]
 ```
 
-Warning prompts are called before executing a task. If a prompt is denied Task will exit with [exit code](api_reference.md#exit-codes) 205. If approved, Task will continue as normal.
+Warning prompts are called before executing a task. If a prompt is denied Task will exit with [exit code](/api#exit-codes) 205. If approved, Task will continue as normal.
 
 ```bash
 ❯ task example
@@ -1425,6 +1595,29 @@ With the flags `--watch` or `-w` task will watch for file changes and run the ta
 
 The default watch interval is 5 seconds, but it's possible to change it by either setting `interval: '500ms'` in the root of the Taskfile passing it as an argument like `--interval=500ms`.
 
+Also, it's possible to set `watch: true` in a given task and it'll automatically run in watch mode:
+
+```yaml
+version: '3'
+
+interval: 500ms
+
+tasks:
+  build:
+    desc: Builds the Go application
+    watch: true
+    sources:
+      - '**/*.go'
+    cmds:
+      - go build  # ...
+```
+
+:::info
+
+Note that when setting `watch: true` to a task, it'll only run in watch mode when running from the CLI via `task my-watch-task`, but won't run in watch mode if called by another task, either directly or as a dependency.
+
+:::
+
 <!-- prettier-ignore-start -->
 
 <!-- prettier-ignore-end -->

docs/i18n/fr-FR/docusaurus-plugin-content-blog/2023-09-02-introducing-experiments.md

@@ -0,0 +1,93 @@
+---
+title: Introducing Experiments
+description: A look at where task is, where it's going and how we're going to get there.
+slug: task-in-2023
+authors:
+  - pd93
+tags:
+  - experiments
+  - breaking-changes
+  - roadmap
+  - v4
+image: https://i.imgur.com/mErPwqL.png
+hide_table_of_contents: false
+---
+
+Lately, Task has been growing extremely quickly and I've found myself thinking a lot about the future of the project and how we continue to evolve and grow. I'm not much of a writer, but I think one of the things we could do better is to communicate these kinds of thoughts to the community. So, with that in mind, this is the first (hopefully of many) blog posts talking about Task and what we're up to.
+
+<!--truncate-->
+
+## :calendar: So, what have we been up to?
+
+Over the past 12 months or so, [@andreynering][] (Author and maintainer of the project) and I ([@pd93][]) have been working in our spare time to maintain and improve v3 of Task and we've made some amazing progress. Here are just some of the things we've released in that time:
+
+- An official [extension for VS Code][vscode-task].
+- Internal Tasks ([#818](https://github.com/go-task/task/pull/818)).
+- Task aliases ([#879](https://github.com/go-task/task/pull/879)).
+- Looping over tasks ([#1220](https://github.com/go-task/task/pull/1200)).
+- A series of refactors to the core codebase to make it more maintainable and extensible.
+- Loads of bug fixes and improvements.
+- An integration with [Crowdin][crowdin]. Work is in progress on making our docs available in **7 new languages** (Special thanks to all our translators for the huge help with this!).
+- And much, much more! :sparkles:
+
+We're also working on adding some really exciting and highly requested features to Task such as having the ability to run remote Taskfiles ([#1317](https://github.com/go-task/task/issues/1317)).
+
+None of this would have been possible without the [150 or so (and growing) contributors][contributors] to the project, numerous sponsors and a passionate community of users. Together we have more than doubled the number of GitHub stars to over 8400 :star: since the beginning of 2022 and this continues to accelerate. We can't thank you all enough for your help and support! :rocket:
+
+[![Star History Chart](https://api.star-history.com/svg?repos=go-task/task&type=Date)](https://star-history.com/#go-task/task&Date)
+
+## What's next? :thinking:
+
+It's extremely motivating to see so many people using and loving Task. However, in this time we've also seen an increase in the number of issues and feature requests. In particular, issues that require some kind of breaking change to Task. This isn't a bad thing, but as we grow we need to be more responsible about how we address these changes in a way that ensures stability and compatibility for existing users and their Taskfiles.
+
+At this point you're probably thinking something like:
+
+> "But you use [semantic versioning][semver] - Just release a new major version with your breaking changes."
+
+And you'd be right... sort of. In theory, this sounds great, but the reality is that we don't have the time to commit to a major overhaul of Task in one big bang release. This would require a colossal amount of time and coordination and with full time jobs and personal lives to tend to, this is a difficult commitment to make. Smaller, more frequent major releases are also a significant inconvenience for users as they have to constantly keep up-to-date with our breaking changes. Fortunately, there is a better way.
+
+## What's going to change? :monocle:
+
+Going forwards, breaking changes will be allowed into _minor_ versions of Task as "experimental features". To access these features users will need opt-in by enabling feature flags. This will allow us to release new features slowly and gather feedback from the community before making them the default behavior in a future major release.
+
+To prepare users for the next major release, we will maintain a list of [deprecated features][deprecations] and [experiments][experiments] on our docs website and publish information on how to migrate to the new behavior.
+
+You can read the [full breaking change proposal][breaking-change-proposal] and view all the [current experiments and their status][experiments-project] on GitHub including the [Gentle Force][gentle-force-experiment] and [Remote Taskfiles][remote-taskfiles-experiment] experiments.
+
+## What will happen to v2/v3 features?
+
+v2 has been [officially deprecated][deprecate-version-2-schema]. If you're still using a Taskfile with `version: "2"` at the top we _strongly recommend_ that you upgrade as soon as possible. Removing v2 will allow us to tidy up the codebase and focus on new functionality instead.
+
+When v4 is released, we will continue to support v3 for a period of time (bug fixes etc). However, since we are moving from a backward-compatibility model to a forwards-compatibility model, **v4 itself will not be backwards compatible with v3**.
+
+## v4 When? :eyes:
+
+:man_shrugging: When it's ready.
+
+In all seriousness, we don't have a timeline for this yet. We'll be working on the most serious deficiencies of the v3 API first and regularly evaluating the state of the project. When we feel its in a good, stable place and we have a clear upgrade path for users and a number of stable experiments, we'll start to think about v4.
+
+## :wave: Final thoughts
+
+Task is growing fast and we're excited to see where it goes next. We hope that the steps we're taking to improve the project and our process will help us to continue to grow. As always, if you have any questions or feedback, we encourage you to comment on or open [issues][issues] and [discussions][discussions] on GitHub. Alternatively, you can join us on [Discord][discord].
+
+I plan to write more of these blog posts in the future on a variety of Task-related topics, so make sure to check in occasionally and see what we're up to!
+
+<!-- prettier-ignore-start -->
+
+<!-- prettier-ignore-end -->
+[vscode-task]: https://github.com/go-task/vscode-task
+[crowdin]: https://crowdin.com
+[contributors]: https://github.com/go-task/task/graphs/contributors
+[semver]: https://semver.org
+[breaking-change-proposal]: https://github.com/go-task/task/discussions/1191
+[@andreynering]: https://github.com/andreynering
+[@pd93]: https://github.com/pd93
+[experiments]: https://taskfile.dev/experiments
+[deprecations]: https://taskfile.dev/deprecations
+[deprecate-version-2-schema]: https://github.com/go-task/task/issues/1197
+[issues]: https://github.com/go-task/task/issues
+[discussions]: https://github.com/go-task/task/discussions
+[discord]: https://discord.gg/6TY36E39UK
+[experiments-project]: https://github.com/orgs/go-task/projects/1
+[gentle-force-experiment]: https://github.com/go-task/task/issues/1200
+[remote-taskfiles-experiment]: https://github.com/go-task/task/issues/1317

docs/i18n/fr-FR/docusaurus-plugin-content-blog/authors.yml

@@ -3,3 +3,8 @@ andreynering:
   title: Mainteneur de Task
   url: https://github.com/andreynering
   image_url: https://github.com/andreynering.png
+pd93:
+  name: Pete Davison
+  title: Mainteneur de Task
+  url: https://github.com/pd93
+  image_url: https://github.com/pd93.png

docs/i18n/fr-FR/docusaurus-plugin-content-docs/current/api_reference.md

@@ -17,7 +17,7 @@ task [--flags] [tasks...] [-- CLI_ARGS...]
 
 :::tip
 
-Si `--` est renseigné, tous les arguments suivants seront assigné à la variable spéciale `CLI_ARGS`
+If `--` is given, all remaining arguments will be assigned to a special `CLI_ARGS` variable
 
 :::
 
@@ -68,6 +68,11 @@ A full list of the exit codes and their descriptions can be found below:
 | 100  | No Taskfile was found                                        |
 | 101  | A Taskfile already exists when trying to initialize one      |
 | 102  | The Taskfile is invalid or cannot be parsed                  |
+| 103  | A remote Taskfile could not be downloaded                    |
+| 104  | A remote Taskfile was not trusted by the user                |
+| 105  | A remote Taskfile was could not be fetched securely          |
+| 106  | No cache was found for a remote Taskfile in offline mode     |
+| 107  | No schema version was defined in the Taskfile                |
 | 200  | The specified task could not be found                        |
 | 201  | An error occurred while executing a command inside of a task |
 | 202  | The user tried to invoke a task that is internal             |
@@ -115,17 +120,19 @@ There are some special variables that is available on the templating system:
 | Var                | Description                                                                                                                                              |
 | ------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------- |
 | `CLI_ARGS`         | Contain all extra arguments passed after `--` when calling Task through the CLI.                                                                         |
+| `CLI_FORCE`        | A boolean containing whether the `--force` or `--force-all` flags were set.                                                                              |
 | `TASK`             | The name of the current task.                                                                                                                            |
 | `ROOT_DIR`         | The absolute path of the root Taskfile.                                                                                                                  |
 | `TASKFILE_DIR`     | The absolute path of the included Taskfile.                                                                                                              |
 | `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 listes in `sources`. Only available within the `status` prop and if method is set to `timestamp`. |
+| `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.                                                                                                                             |
+| `ITEM`             | The value of the current iteration when using the `for` property. Can be changed to a different variable name using `as:`.                               |
 
 ## ENV
 
-Some environment variables can be overriden to adjust Task behavior.
+Some environment variables can be overridden to adjust Task behavior.
 
 | ENV                  | Default | Description                                                                                                       |
 | -------------------- | ------- | ----------------------------------------------------------------------------------------------------------------- |
@@ -145,12 +152,12 @@ Some environment variables can be overriden to adjust Task behavior.
 | ---------- | ---------------------------------- | ------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
 | `version`  | `string`                           |               | Version of the Taskfile. The current version is `3`.                                                                                                                   |
 | `output`   | `string`                           | `interleaved` | Output mode. Available options: `interleaved`, `group` and `prefixed`.                                                                                                 |
-| `method`   | `string`                           | `checksum`    | Default method in this Taskfile. Can be overriden in a task by task basis. Available options: `checksum`, `timestamp` and `none`.                                      |
+| `method`   | `string`                           | `checksum`    | Default method in this Taskfile. Can be overridden in a task by task basis. Available options: `checksum`, `timestamp` and `none`.                                     |
 | `includes` | [`map[string]Include`](#include)   |               | Additional Taskfiles to be included.                                                                                                                                   |
 | `vars`     | [`map[string]Variable`](#variable) |               | A set of global variables.                                                                                                                                             |
 | `env`      | [`map[string]Variable`](#variable) |               | A set of global environment variables.                                                                                                                                 |
 | `tasks`    | [`map[string]Task`](#task)         |               | A set of task definitions.                                                                                                                                             |
-| `silent`   | `bool`                             | `false`       | Default 'silent' options for this Taskfile. If `false`, can be overidden with `true` in a task by task basis.                                                          |
+| `silent`   | `bool`                             | `false`       | Default 'silent' options for this Taskfile. If `false`, can be overridden with `true` in a task by task basis.                                                         |
 | `dotenv`   | `[]string`                         |               | A list of `.env` file paths to be parsed.                                                                                                                              |
 | `run`      | `string`                           | `always`      | Default 'run' option for this Taskfile. Available options: `always`, `once` and `when_changed`.                                                                        |
 | `interval` | `string`                           | `5s`          | Sets a different watch interval when using `--watch`, the default being 5 seconds. This string should be a valid [Go Duration](https://pkg.go.dev/time#ParseDuration). |
@@ -254,8 +261,9 @@ tasks:
 | Attribute      | Type                               | Default       | Description                                                                                                                                                                                        |
 | -------------- | ---------------------------------- | ------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
 | `cmd`          | `string`                           |               | The shell command to be executed.                                                                                                                                                                  |
-| `silent`       | `bool`                             | `false`       | Skips some output for this command. Note that STDOUT and STDERR of the commands will still be redirected.                                                                                          |
 | `task`         | `string`                           |               | Set this to trigger execution of another task instead of running a command. This cannot be set together with `cmd`.                                                                                |
+| `for`          | [`For`](#for)                      |               | Runs the command once for each given value.                                                                                                                                                        |
+| `silent`       | `bool`                             | `false`       | Skips some output for this command. Note that STDOUT and STDERR of the commands will still be redirected.                                                                                          |
 | `vars`         | [`map[string]Variable`](#variable) |               | Optional additional variables to be passed to the referenced task. Only relevant when setting `task` instead of `cmd`.                                                                             |
 | `ignore_error` | `bool`                             | `false`       | Continue execution if errors happen while executing the command.                                                                                                                                   |
 | `defer`        | `string`                           |               | Alternative to `cmd`, but schedules the command to be executed at the end of this task instead of immediately. This cannot be used together with `cmd`.                                            |
@@ -297,6 +305,22 @@ tasks:
 
 :::
 
+#### For
+
+The `for` parameter can be defined as a string, a list of strings or a map. If it is defined as a string, you can give it any of the following values:
+
+- `source` - Will run the command for each source file defined on the task. (Glob patterns will be resolved, so `*.go` will run for every Go file that matches).
+
+If it is defined as a list of strings, the command will be run for each value.
+
+Finally, the `for` parameter can be defined as a map when you want to use a variable to define the values to loop over:
+
+| Attribute | Type     | Default          | Description                                  |
+| --------- | -------- | ---------------- | -------------------------------------------- |
+| `var`     | `string` |                  | The name of the variable to use as an input. |
+| `split`   | `string` | (any whitespace) | What string the variable should be split on. |
+| `as`      | `string` | `ITEM`           | The name of the iterator variable.           |
+
 #### Precondition
 
 | Attribute | Type     | Default | Description                                                                                                  |

docs/i18n/fr-FR/docusaurus-plugin-content-docs/current/changelog.md

@@ -1,394 +1,473 @@
 ---
 slug: /changelog/
-sidebar_position: 9
+sidebar_position: 14
 ---
 
 # Changelog
 
+## v3.33.1 - 2023-12-21
+
+- Added support for looping over map variables with the [Any Variables experiment](https://taskfile.dev/experiments/any_variables) enabled (#1435, #1437 by @pd93).
+- Fixed a bug where dynamic variables were causing errors during fast compilation (#1435, #1437 by @pd93)
+
+## v3.33.0 - 2023-12-20
+
+- Added [Any Variables experiment](https://taskfile.dev/experiments/any-variables) (#1415, #1421 by @pd93).
+- Updated Docusaurus to v3 (#1432 by @pd93).
+- Added `aliases` to `--json` flag output (#1430, #1431 by @pd93).
+- Added new `CLI_FORCE` special variable containing whether the `--force` or `--force-all` flags were set (#1412, #1434 by @pd93).
+
+## v3.32.0 - 2023-11-29
+
+- Added ability to exclude some files from `sources:` by using `exclude:` (#225,
+
+  # 1324 by @pd93 and @andreynering).
+- The [Remote Taskfiles experiment](https://taskfile.dev/experiments/remote-taskfiles) now prefers remote files over cached ones by default (#1317, #1345 by @pd93).
+- Added `--timeout` flag to the [Remote Taskfiles experiment](https://taskfile.dev/experiments/remote-taskfiles) (#1317, #1345 by @pd93).
+- Fix bug where dynamic `vars:` and `env:` were being executed when they should actually be skipped by `platforms:` (#1273, #1377 by @andreynering).
+- Fix `schema.json` to make `silent` valid in `cmds` that use `for` (#1385,
+
+  # 1386 by @iainvm).
+- Add new `--no-status` flag to skip expensive status checks when running `task --list --json` (#1348, #1368 by @amancevice).
+
+## v3.31.0 - 2023-10-07
+
+- Enabled the `--yes` flag for the [Remote Taskfiles experiment](https://taskfile.dev/experiments/remote-taskfiles) (#1317, #1344 by @pd93).
+- Add ability to set `watch: true` in a task to automatically run it in watch mode (#231, #1361 by @andreynering).
+- Fixed a bug on the watch mode where paths that contained `.git` (like `.github`), for example, were also being ignored (#1356 by @butuzov).
+- Fixed a nil pointer error when running a Taskfile with no contents (#1341,
+
+  # 1342 by @pd93).
+- Added a new [exit code](https://taskfile.dev/api/#exit-codes) (107) for when a Taskfile does not contain a schema version (#1342 by @pd93).
+- Increased limit of maximum task calls from 100 to 1000 for now, as some people have been reaching this limit organically now that we have loops. This check exists to detect recursive calls, but will be removed in favor of a better algorithm soon (#1321, #1332).
+- Fixed templating on descriptions on `task --list` (#1343 by @blackjid).
+- Fixed a bug where precondition errors were incorrectly being printed when task execution was aborted (#1337, #1338 by @sylv-io).
+
+## v3.30.1 - 2023-09-14
+
+- Fixed a regression where some special variables weren't being set correctly (#1331, #1334 by @pd93).
+
+## v3.30.0 - 2023-09-13
+
+- Prep work for Remote Taskfiles (#1316 by @pd93).
+- Added the [Remote Taskfiles experiment](https://taskfile.dev/experiments/remote-taskfiles) as a draft (#1152, #1317 by @pd93).
+- Improve performance of content checksuming on `sources:` by replacing md5 with [XXH3](https://xxhash.com/) which is much faster. This is a soft breaking change because checksums will be invalidated when upgrading to this release (#1325 by @ReillyBrogan).
+
+## v3.29.1 - 2023-08-26
+
+- Update to Go 1.21 (bump minimum version to 1.20) (#1302 by @pd93)
+- Fix a missing a line break on log when using `--watch` mode (#1285, #1297 by @FilipSolich).
+- Fix `defer` on JSON Schema (#1288 by @calvinmclean and @andreynering).
+- Fix bug in usage of special variables like `{{.USER_WORKING_DIR}}` in combination with `includes` (#1046, #1205, #1250, #1293, #1312, #1274 by @andarto, #1309 by @andreynering).
+- Fix bug on `--status` flag. Running this flag should not have side-effects: it should not update the checksum on `.task`, only report its status (#1305,
+
+  # 1307 by @visciang, #1313 by @andreynering).
+
+## v3.28.0 - 2023-07-24
+
+- Added the ability to [loop over commands and tasks](https://taskfile.dev/usage/#looping-over-values) using `for` (#82, #1220 by @pd93).
+- Fixed variable propagation in multi-level includes (#778, #996, #1256 by @hudclark).
+- Fixed a bug where the `--exit-code` code flag was not returning the correct exit code when calling commands indirectly (#1266, #1270 by @pd93).
+- Fixed a `nil` panic when a dependency was commented out or left empty (#1263 by @neomantra).
+
 ## v3.27.1 - 2023-06-30
 
-- Fix panic when a `.env` directory (not file) is present on current directory ([#1244](https://github.com/go-task/task/issues/1244), [#1245](https://github.com/go-task/task/issues/1245) by [@pd93](https://github.com/pd93)).
+- Fix panic when a `.env` directory (not file) is present on current directory (#1244, #1245 by @pd93).
 
 ## v3.27.0 - 2023-06-29
 
-- Allow Taskfiles starting with lowercase characters ([#947](https://github.com/go-task/task/issues/947), [#1221](https://github.com/go-task/task/issues/1221) by [@pd93](https://github.com/pd93)).
+- Allow Taskfiles starting with lowercase characters (#947, #1221 by @pd93).
   - e.g. `taskfile.yml`, `taskfile.yaml`, `taskfile.dist.yml` & `taskfile.dist.yaml`
-- Bug fixes were made to the [npm installation method](https://taskfile.dev/installation/#npm). ([#1190](https://github.com/go-task/task/issues/1190), by [@sounisi5011](https://github.com/sounisi5011)).
-- Added the [gentle force experiment](https://taskfile.dev/experiments) as a draft ([#1200](https://github.com/go-task/task/issues/1200), [#1216](https://github.com/go-task/task/issues/1216) by [@pd93](https://github.com/pd93)).
-- Added an `--experiments` flag to allow you to see which experiments are enabled ([#1242](https://github.com/go-task/task/issues/1242) by [@pd93](https://github.com/pd93)).
-- Added ability to specify which variables are required in a task ([#1203](https://github.com/go-task/task/issues/1203), [#1204](https://github.com/go-task/task/issues/1204) by [@benc](https://github.com/benc)-uk).
+- Bug fixes were made to the [npm installation method](https://taskfile.dev/installation/#npm). (#1190, by @sounisi5011).
+- Added the [gentle force experiment](https://taskfile.dev/experiments/gentle-force) as a draft (#1200, #1216 by @pd93).
+- Added an `--experiments` flag to allow you to see which experiments are enabled (#1242 by @pd93).
+- Added ability to specify which variables are required in a task (#1203, #1204 by @benc-uk).
 
 ## v3.26.0 - 2023-06-10
 
-- Only rewrite checksum files in `.task` if the checksum has changed ([#1185](https://github.com/go-task/task/issues/1185), [#1194](https://github.com/go-task/task/issues/1194) by [@deviantintegral](https://github.com/deviantintegral)).
-- Added [experiments documentation](https://taskfile.dev/experiments) to the website ([#1198](https://github.com/go-task/task/issues/1198) by [@pd93](https://github.com/pd93)).
-- Deprecated `version: 2` schema. This will be removed in the next major release ([#1197](https://github.com/go-task/task/issues/1197), [#1198](https://github.com/go-task/task/issues/1198), [#1199](https://github.com/go-task/task/issues/1199) by [@pd93](https://github.com/pd93)).
-- Added a new `prompt:` prop to set a warning prompt to be shown before running a potential dangurous task ([#100](https://github.com/go-task/task/issues/100), [#1163](https://github.com/go-task/task/issues/1163) by [@MaxCheetham](https://github.com/MaxCheetham), [Documentation](https://taskfile.dev/usage/#warning-prompts)).
-- Added support for single command task syntax. With this change, it's now possible to declare just `cmd:` in a task, avoiding the more complex `cmds: []` when you have only a single command for that task ([#1130](https://github.com/go-task/task/issues/1130), [#1131](https://github.com/go-task/task/issues/1131) by [@timdp](https://github.com/timdp)).
+- Only rewrite checksum files in `.task` if the checksum has changed (#1185,
+
+  # 1194 by @deviantintegral).
+- Added [experiments documentation](https://taskfile.dev/experiments) to the website (#1198 by @pd93).
+- Deprecated `version: 2` schema. This will be removed in the next major release (#1197, #1198, #1199 by @pd93).
+- Added a new `prompt:` prop to set a warning prompt to be shown before running a potential dangurous task (#100, #1163 by @MaxCheetham, [Documentation](https://taskfile.dev/usage/#warning-prompts)).
+- Added support for single command task syntax. With this change, it's now possible to declare just `cmd:` in a task, avoiding the more complex `cmds: []` when you have only a single command for that task (#1130, #1131 by @timdp).
 
 ## v3.25.0 - 2023-05-22
 
-- Support `silent:` when calling another tasks ([#680](https://github.com/go-task/task/issues/680), [#1142](https://github.com/go-task/task/issues/1142) by [@danquah](https://github.com/danquah)).
-- Improve PowerShell completion script ([#1168](https://github.com/go-task/task/issues/1168) by [@trim21](https://github.com/trim21)).
-- Add more languages to the website menu and show translation progress percentage ([#1173](https://github.com/go-task/task/issues/1173) by [@misitebao](https://github.com/misitebao)).
-- Starting on this release, official binaries for FreeBSD will be available to download ([#1068](https://github.com/go-task/task/issues/1068) by [@andreynering](https://github.com/andreynering)).
-- Fix some errors being unintendedly supressed ([#1134](https://github.com/go-task/task/issues/1134) by [@clintmod](https://github.com/clintmod)).
-- Fix a nil pointer error when `version` is omitted from a Taskfile ([#1148](https://github.com/go-task/task/issues/1148), [#1149](https://github.com/go-task/task/issues/1149) by [@pd93](https://github.com/pd93)).
-- Fix duplicate error message when a task does not exists ([#1141](https://github.com/go-task/task/issues/1141), [#1144](https://github.com/go-task/task/issues/1144) by [@pd93](https://github.com/pd93)).
+- Support `silent:` when calling another tasks (#680, #1142 by @danquah).
+- Improve PowerShell completion script (#1168 by @trim21).
+- Add more languages to the website menu and show translation progress percentage (#1173 by @misitebao).
+- Starting on this release, official binaries for FreeBSD will be available to download (#1068 by @andreynering).
+- Fix some errors being unintendedly supressed (#1134 by @clintmod).
+- Fix a nil pointer error when `version` is omitted from a Taskfile (#1148,
+
+  # 1149 by @pd93).
+- Fix duplicate error message when a task does not exists (#1141, #1144 by @pd93).
 
 ## v3.24.0 - 2023-04-15
 
-- Fix Fish shell completion for tasks with aliases ([#1113](https://github.com/go-task/task/issues/1113) by [@patricksjackson](https://github.com/patricksjackson)).
-- The default branch was renamed from `master` to `main` ([#1049](https://github.com/go-task/task/issues/1049), [#1048](https://github.com/go-task/task/issues/1048) by [@pd93](https://github.com/pd93)).
-- Fix bug where "up-to-date" logs were not being omitted for silent tasks ([#546](https://github.com/go-task/task/issues/546), [#1107](https://github.com/go-task/task/issues/1107) by [@danquah](https://github.com/danquah)).
-- Add `.hg` (Mercurial) to the list of ignored directories when using `--watch` ([#1098](https://github.com/go-task/task/issues/1098) by [@misery](https://github.com/misery)).
-- More improvements to the release tool ([#1096](https://github.com/go-task/task/issues/1096) by [@pd93](https://github.com/pd93)).
-- Enforce [gofumpt](https://github.com/mvdan/gofumpt) linter ([#1099](https://github.com/go-task/task/issues/1099) by [@pd93](https://github.com/pd93))
-- Add `--sort` flag for use with `--list` and `--list-all` ([#946](https://github.com/go-task/task/issues/946), [#1105](https://github.com/go-task/task/issues/1105) by [@pd93](https://github.com/pd93)).
-- Task now has [custom exit codes](https://taskfile.dev/api/#exit-codes) depending on the error ([#1114](https://github.com/go-task/task/issues/1114) by [@pd93](https://github.com/pd93)).
+- Fix Fish shell completion for tasks with aliases (#1113 by @patricksjackson).
+- The default branch was renamed from `master` to `main` (#1049, #1048 by @pd93).
+- Fix bug where "up-to-date" logs were not being omitted for silent tasks (#546,
+
+  # 1107 by @danquah).
+- Add `.hg` (Mercurial) to the list of ignored directories when using `--watch` (#1098 by @misery).
+- More improvements to the release tool (#1096 by @pd93).
+- Enforce [gofumpt](https://github.com/mvdan/gofumpt) linter (#1099 by @pd93)
+- Add `--sort` flag for use with `--list` and `--list-all` (#946, #1105 by @pd93).
+- Task now has [custom exit codes](https://taskfile.dev/api/#exit-codes) depending on the error (#1114 by @pd93).
 
 ## v3.23.0 - 2023-03-26
 
-Task now has an [official extension for Visual Studio Code](https://marketplace.visualstudio.com/items?itemName=task.vscode-task) contributed by [@pd93](https://github.com/pd93)! :tada: The extension is maintained in a [new repository](https://github.com/go-task/vscode-task) under the `go-task` organization. We're looking to gather feedback from the community so please give it a go and let us know what you think via a [discussion](https://github.com/go-task/vscode-task/discussions), [issue](https://github.com/go-task/vscode-task/issues) or on our [Discord](https://discord.gg/6TY36E39UK)!
+Task now has an [official extension for Visual Studio Code](https://marketplace.visualstudio.com/items?itemName=task.vscode-task) contributed by @pd93! :tada: The extension is maintained in a [new repository](https://github.com/go-task/vscode-task) under the `go-task` organization. We're looking to gather feedback from the community so please give it a go and let us know what you think via a [discussion](https://github.com/go-task/vscode-task/discussions), [issue](https://github.com/go-task/vscode-task/issues) or on our [Discord](https://discord.gg/6TY36E39UK)!
 
 > **NOTE:** The extension _requires_ v3.23.0 to be installed in order to work.
 
-- The website was integrated with [Crowdin](https://crowdin.com/project/taskfile) to allow the community to contribute with translations! [Chinese](https://taskfile.dev/zh-Hans/) is the first language available ([#1057](https://github.com/go-task/task/issues/1057), [#1058](https://github.com/go-task/task/issues/1058) by [@misitebao](https://github.com/misitebao)).
-- Added task location data to the `--json` flag output ([#1056](https://github.com/go-task/task/issues/1056) by [@pd93](https://github.com/pd93))
-- Change the name of the file generated by `task --init` from `Taskfile.yaml` to `Taskfile.yml` ([#1062](https://github.com/go-task/task/issues/1062) by [@misitebao](https://github.com/misitebao)).
-- Added new `splitArgs` template function (`{{splitArgs "foo bar 'foo bar baz'"}}`) to ensure string is split as arguments ([#1040](https://github.com/go-task/task/issues/1040), [#1059](https://github.com/go-task/task/issues/1059) by [@dhanusaputra](https://github.com/dhanusaputra)).
-- Fix the value of `{{.CHECKSUM}}` variable in status ([#1076](https://github.com/go-task/task/issues/1076), [#1080](https://github.com/go-task/task/issues/1080) by [@pd93](https://github.com/pd93)).
-- Fixed deep copy implementation ([#1072](https://github.com/go-task/task/issues/1072) by [@pd93](https://github.com/pd93))
-- Created a tool to assist with releases ([#1086](https://github.com/go-task/task/issues/1086) by [@pd93](https://github.com/pd93)).
+- The website was integrated with [Crowdin](https://crowdin.com/project/taskfile) to allow the community to contribute with translations! [Chinese](https://taskfile.dev/zh-Hans/) is the first language available (#1057, #1058 by @misitebao).
+- Added task location data to the `--json` flag output (#1056 by @pd93)
+- Change the name of the file generated by `task --init` from `Taskfile.yaml` to `Taskfile.yml` (#1062 by @misitebao).
+- Added new `splitArgs` template function (`{{splitArgs "foo bar 'foo bar baz'"}}`) to ensure string is split as arguments (#1040, #1059 by @dhanusaputra).
+- Fix the value of `{{.CHECKSUM}}` variable in status (#1076, #1080 by @pd93).
+- Fixed deep copy implementation (#1072 by @pd93)
+- Created a tool to assist with releases (#1086 by @pd93).
 
 ## v3.22.0 - 2023-03-10
 
-- Add a brand new `--global` (`-g`) flag that will run a Taskfile from your `$HOME` directory. This is useful to have automation that you can run from anywhere in your system! ([Documentation](https://taskfile.dev/usage/#running-a-global-taskfile), [#1029](https://github.com/go-task/task/issues/1029) by [@andreynering](https://github.com/andreynering)).
-- Add ability to set `error_only: true` on the `group` output mode. This will instruct Task to only print a command output if it returned with a non-zero exit code ([#664](https://github.com/go-task/task/issues/664), [#1022](https://github.com/go-task/task/issues/1022) by [@jaedle](https://github.com/jaedle)).
-- Fixed bug where `.task/checksum` file was sometimes not being created when task also declares a `status:` ([#840](https://github.com/go-task/task/issues/840), [#1035](https://github.com/go-task/task/issues/1035) by [@harelwa](https://github.com/harelwa), [#1037](https://github.com/go-task/task/issues/1037) by [@pd93](https://github.com/pd93)).
-- Refactored and decoupled fingerprinting from the main Task executor ([#1039](https://github.com/go-task/task/issues/1039) by [@pd93](https://github.com/pd93)).
-- Fixed deadlock issue when using `run: once` ([#715](https://github.com/go-task/task/issues/715), [#1025](https://github.com/go-task/task/issues/1025) by [@theunrepentantgeek](https://github.com/theunrepentantgeek)).
+- Add a brand new `--global` (`-g`) flag that will run a Taskfile from your `$HOME` directory. This is useful to have automation that you can run from anywhere in your system! ([Documentation](https://taskfile.dev/usage/#running-a-global-taskfile), #1029 by @andreynering).
+- Add ability to set `error_only: true` on the `group` output mode. This will instruct Task to only print a command output if it returned with a non-zero exit code (#664, #1022 by @jaedle).
+- Fixed bug where `.task/checksum` file was sometimes not being created when task also declares a `status:` (#840, #1035 by @harelwa, #1037 by @pd93).
+- Refactored and decoupled fingerprinting from the main Task executor (#1039 by @pd93).
+- Fixed deadlock issue when using `run: once` (#715, #1025 by @theunrepentantgeek).
 
 ## v3.21.0 - 2023-02-22
 
-- Added new `TASK_VERSION` special variable ([#990](https://github.com/go-task/task/issues/990), [#1014](https://github.com/go-task/task/issues/1014) by [@ja1code](https://github.com/ja1code)).
-- Fixed a bug where tasks were sometimes incorrectly marked as internal ([#1007](https://github.com/go-task/task/issues/1007) by [@pd93](https://github.com/pd93)).
-- Update to Go 1.20 (bump minimum version to 1.19) ([#1010](https://github.com/go-task/task/issues/1010) by [@pd93](https://github.com/pd93))
-- Added environment variable `FORCE_COLOR` support to force color output. Usefull for environments without TTY ([#1003](https://github.com/go-task/task/issues/1003) by [@automation](https://github.com/automation)-stack)
+- Added new `TASK_VERSION` special variable (#990, #1014 by @ja1code).
+- Fixed a bug where tasks were sometimes incorrectly marked as internal (#1007 by @pd93).
+- Update to Go 1.20 (bump minimum version to 1.19) (#1010 by @pd93)
+- Added environment variable `FORCE_COLOR` support to force color output. Usefull for environments without TTY (#1003 by @automation-stack)
 
 ## v3.20.0 - 2023-01-14
 
-- Improve behavior and performance of status checking when using the `timestamp` mode ([#976](https://github.com/go-task/task/issues/976), [#977](https://github.com/go-task/task/issues/977) by [@aminya](https://github.com/aminya)).
-- Performance optimizations were made for large Taskfiles ([#982](https://github.com/go-task/task/issues/982) by [@pd93](https://github.com/pd93)).
-- Add ability to configure options for the [`set`](https://www.gnu.org/software/bash/manual/html_node/The-Set-Builtin.html) and [`shopt`](https://www.gnu.org/software/bash/manual/html_node/The-Shopt-Builtin.html) builtins ([#908](https://github.com/go-task/task/issues/908), [#929](https://github.com/go-task/task/issues/929) by [@pd93](https://github.com/pd93), [Documentation](http://taskfile.dev/usage/#set-and-shopt)).
-- Add new `platforms:` attribute to `task` and `cmd`, so it's now possible to choose in which platforms that given task or command will be run on. Possible values are operating system (GOOS), architecture (GOARCH) or a combination of the two. Example: `platforms: [linux]`, `platforms: [amd64]` or `platforms: [linux/amd64]`. Other platforms will be skipped ([#978](https://github.com/go-task/task/issues/978), [#980](https://github.com/go-task/task/issues/980) by [@leaanthony](https://github.com/leaanthony)).
+- Improve behavior and performance of status checking when using the `timestamp` mode (#976, #977 by @aminya).
+- Performance optimizations were made for large Taskfiles (#982 by @pd93).
+- Add ability to configure options for the [`set`](https://www.gnu.org/software/bash/manual/html_node/The-Set-Builtin.html) and [`shopt`](https://www.gnu.org/software/bash/manual/html_node/The-Shopt-Builtin.html) builtins (#908, #929 by @pd93, [Documentation](http://taskfile.dev/usage/#set-and-shopt)).
+- Add new `platforms:` attribute to `task` and `cmd`, so it's now possible to choose in which platforms that given task or command will be run on. Possible values are operating system (GOOS), architecture (GOARCH) or a combination of the two. Example: `platforms: [linux]`, `platforms: [amd64]` or `platforms: [linux/amd64]`. Other platforms will be skipped (#978, #980 by @leaanthony).
 
 ## v3.19.1 - 2022-12-31
 
-- Small bug fix: closing `Taskfile.yml` once we're done reading it ([#963](https://github.com/go-task/task/issues/963), [#964](https://github.com/go-task/task/issues/964) by [@HeCorr](https://github.com/HeCorr)).
-- Fixes a bug in v2 that caused a panic when using a `Taskfile_{{OS}}.yml` file ([#961](https://github.com/go-task/task/issues/961), [#971](https://github.com/go-task/task/issues/971) by [@pd93](https://github.com/pd93)).
-- Fixed a bug where watch intervals set in the Taskfile were not being respected ([#969](https://github.com/go-task/task/issues/969), [#970](https://github.com/go-task/task/issues/970) by [@pd93](https://github.com/pd93))
-- Add `--json` flag (alias `-j`) with the intent to improve support for code editors and add room to other possible integrations. This is basic for now, but we plan to add more info in the near future ([#936](https://github.com/go-task/task/issues/936) by [@davidalpert](https://github.com/davidalpert), [#764](https://github.com/go-task/task/issues/764)).
+- Small bug fix: closing `Taskfile.yml` once we're done reading it (#963, #964 by @HeCorr).
+- Fixes a bug in v2 that caused a panic when using a `Taskfile_{{OS}}.yml` file (#961, #971 by @pd93).
+- Fixed a bug where watch intervals set in the Taskfile were not being respected (#969, #970 by @pd93)
+- Add `--json` flag (alias `-j`) with the intent to improve support for code editors and add room to other possible integrations. This is basic for now, but we plan to add more info in the near future (#936 by @davidalpert, #764).
 
 ## v3.19.0 - 2022-12-05
 
-- Installation via npm now supports [pnpm](https://pnpm.io/) as well ([go-task/go-npm\[#2\](https://github.com/go-task/task/issues/2)](https://github.com/go-task/go-npm/issues/2), [go-task/go-npm\[#3\](https://github.com/go-task/task/issues/3)](https://github.com/go-task/go-npm/pull/3)).
-- It's now possible to run Taskfiles from subdirectories! A new `USER_WORKING_DIR` special variable was added to add even more flexibility for monorepos ([#289](https://github.com/go-task/task/issues/289), [#920](https://github.com/go-task/task/issues/920)).
-- Add task-level `dotenv` support ([#389](https://github.com/go-task/task/issues/389), [#904](https://github.com/go-task/task/issues/904)).
-- It's now possible to use global level variables on `includes` ([#942](https://github.com/go-task/task/issues/942), [#943](https://github.com/go-task/task/issues/943)).
-- The website got a brand new [translation to Chinese](https://task-zh.readthedocs.io/zh_CN/latest/) by [\[@DeronW\](https://github.com/DeronW)](https://github.com/DeronW). Thanks!
+- Installation via npm now supports [pnpm](https://pnpm.io/) as well ([go-task/go-npm#2](https://github.com/go-task/go-npm/issues/2), [go-task/go-npm#3](https://github.com/go-task/go-npm/pull/3)).
+- It's now possible to run Taskfiles from subdirectories! A new `USER_WORKING_DIR` special variable was added to add even more flexibility for monorepos (#289, #920).
+- Add task-level `dotenv` support (#389, #904).
+- It's now possible to use global level variables on `includes` (#942, #943).
+- The website got a brand new [translation to Chinese](https://task-zh.readthedocs.io/zh_CN/latest/) by [@DeronW](https://github.com/DeronW). Thanks!
 
 ## v3.18.0 - 2022-11-12
 
-- Show aliases on `task --list --silent` (`task --ls`). This means that aliases will be completed by the completion scripts ([#919](https://github.com/go-task/task/issues/919)).
-- Tasks in the root Taskfile will now be displayed first in `--list`/`--list-all` output ([#806](https://github.com/go-task/task/issues/806), [#890](https://github.com/go-task/task/issues/890)).
-- It's now possible to call a `default` task in an included Taskfile by using just the namespace. For example: `docs:default` is now automatically aliased to `docs` ([#661](https://github.com/go-task/task/issues/661), [#815](https://github.com/go-task/task/issues/815)).
+- Show aliases on `task --list --silent` (`task --ls`). This means that aliases will be completed by the completion scripts (#919).
+- Tasks in the root Taskfile will now be displayed first in `--list`/`--list-all` output (#806, #890).
+- It's now possible to call a `default` task in an included Taskfile by using just the namespace. For example: `docs:default` is now automatically aliased to `docs` (#661, #815).
 
 ## v3.17.0 - 2022-10-14
 
-- Add a "Did you mean ...?" suggestion when a task does not exits another one with a similar name is found ([#867](https://github.com/go-task/task/issues/867), [#880](https://github.com/go-task/task/issues/880)).
-- Now YAML parse errors will print which Taskfile failed to parse ([#885](https://github.com/go-task/task/issues/885), [#887](https://github.com/go-task/task/issues/887)).
-- Add ability to set `aliases` for tasks and namespaces ([#268](https://github.com/go-task/task/issues/268), [#340](https://github.com/go-task/task/issues/340), [#879](https://github.com/go-task/task/issues/879)).
-- Improvements to Fish shell completion ([#897](https://github.com/go-task/task/issues/897)).
-- Added ability to set a different watch interval by setting `interval: '500ms'` or using the `--interval=500ms` flag ([#813](https://github.com/go-task/task/issues/813), [#865](https://github.com/go-task/task/issues/865)).
-- Add colored output to `--list`, `--list-all` and `--summary` flags ([#845](https://github.com/go-task/task/issues/845), [#874](https://github.com/go-task/task/issues/874)).
-- Fix unexpected behavior where `label:` was being shown instead of the task name on `--list` ([#603](https://github.com/go-task/task/issues/603), [#877](https://github.com/go-task/task/issues/877)).
+- Add a "Did you mean ...?" suggestion when a task does not exits another one with a similar name is found (#867, #880).
+- Now YAML parse errors will print which Taskfile failed to parse (#885, #887).
+- Add ability to set `aliases` for tasks and namespaces (#268, #340, #879).
+- Improvements to Fish shell completion (#897).
+- Added ability to set a different watch interval by setting `interval: '500ms'` or using the `--interval=500ms` flag (#813, #865).
+- Add colored output to `--list`, `--list-all` and `--summary` flags (#845,
+
+  # 874).
+- Fix unexpected behavior where `label:` was being shown instead of the task name on `--list` (#603, #877).
 
 ## v3.16.0 - 2022-09-29
 
-- Add `npm` as new installation method: `npm i -g [@go](https://github.com/go)-task/cli` ([#870](https://github.com/go-task/task/issues/870), [#871](https://github.com/go-task/task/issues/871), [npm package](https://www.npmjs.com/package/[@go](https://github.com/go)-task/cli)).
-- Add support to marking tasks and includes as internal, which will hide them from `--list` and `--list-all` ([#818](https://github.com/go-task/task/issues/818)).
+- Add `npm` as new installation method: `npm i -g @go-task/cli` (#870, #871, [npm package](https://www.npmjs.com/package/@go-task/cli)).
+- Add support to marking tasks and includes as internal, which will hide them from `--list` and `--list-all` (#818).
 
 ## v3.15.2 - 2022-09-08
 
-- Fix error when using variable in `env:` introduced in the previous release ([#858](https://github.com/go-task/task/issues/858), [#866](https://github.com/go-task/task/issues/866)).
-- Fix handling of `CLI_ARGS` (`--`) in Bash completion ([#863](https://github.com/go-task/task/issues/863)).
-- On zsh completion, add ability to replace `--list-all` with `--list` as already possible on the Bash completion ([#861](https://github.com/go-task/task/issues/861)).
+- Fix error when using variable in `env:` introduced in the previous release (#858, #866).
+- Fix handling of `CLI_ARGS` (`--`) in Bash completion (#863).
+- On zsh completion, add ability to replace `--list-all` with `--list` as already possible on the Bash completion (#861).
 
 ## v3.15.0 - 2022-09-03
 
-- Add new special variables `ROOT_DIR` and `TASKFILE_DIR`. This was a highly requested feature ([#215](https://github.com/go-task/task/issues/215), [#857](https://github.com/go-task/task/issues/857), [Documentation](https://taskfile.dev/api/#special-variables)).
-- Follow symlinks on `sources` ([#826](https://github.com/go-task/task/issues/826), [#831](https://github.com/go-task/task/issues/831)).
-- Improvements and fixes to Bash completion ([#835](https://github.com/go-task/task/issues/835), [#844](https://github.com/go-task/task/issues/844)).
+- Add new special variables `ROOT_DIR` and `TASKFILE_DIR`. This was a highly requested feature (#215, #857, [Documentation](https://taskfile.dev/api/#special-variables)).
+- Follow symlinks on `sources` (#826, #831).
+- Improvements and fixes to Bash completion (#835, #844).
 
 ## v3.14.1 - 2022-08-03
 
-- Always resolve relative include paths relative to the including Taskfile ([#822](https://github.com/go-task/task/issues/822), [#823](https://github.com/go-task/task/issues/823)).
-- Fix ZSH and PowerShell completions to consider all tasks instead of just the public ones (those with descriptions) ([#803](https://github.com/go-task/task/issues/803)).
+- Always resolve relative include paths relative to the including Taskfile (#822, #823).
+- Fix ZSH and PowerShell completions to consider all tasks instead of just the public ones (those with descriptions) (#803).
 
 ## v3.14.0 - 2022-07-08
 
 - Add ability to override the `.task` directory location with the `TASK_TEMP_DIR` environment variable.
-- Allow to override Task colors using environment variables: `TASK_COLOR_RESET`, `TASK_COLOR_BLUE`, `TASK_COLOR_GREEN`, `TASK_COLOR_CYAN`, `TASK_COLOR_YELLOW`, `TASK_COLOR_MAGENTA` and `TASK_COLOR_RED` ([#568](https://github.com/go-task/task/issues/568), [#792](https://github.com/go-task/task/issues/792)).
-- Fixed bug when using the `output: group` mode where STDOUT and STDERR were being print in separated blocks instead of in the right order ([#779](https://github.com/go-task/task/issues/779)).
-- Starting on this release, ARM architecture binaries are been released to Snap as well ([#795](https://github.com/go-task/task/issues/795)).
+- Allow to override Task colors using environment variables: `TASK_COLOR_RESET`, `TASK_COLOR_BLUE`, `TASK_COLOR_GREEN`, `TASK_COLOR_CYAN`, `TASK_COLOR_YELLOW`, `TASK_COLOR_MAGENTA` and `TASK_COLOR_RED` (#568, #792).
+- Fixed bug when using the `output: group` mode where STDOUT and STDERR were being print in separated blocks instead of in the right order (#779).
+- Starting on this release, ARM architecture binaries are been released to Snap as well (#795).
 - i386 binaries won't be available anymore on Snap because Ubuntu removed the support for this architecture.
-- Upgrade mvdan.cc/sh, which fixes a bug with associative arrays ([#785](https://github.com/go-task/task/issues/785), [mvdan/sh\[#884\](https://github.com/go-task/task/issues/884)](https://github.com/mvdan/sh/issues/884), [mvdan/sh\[#893\](https://github.com/go-task/task/issues/893)](https://github.com/mvdan/sh/pull/893)).
+- Upgrade mvdan.cc/sh, which fixes a bug with associative arrays (#785, [mvdan/sh#884](https://github.com/mvdan/sh/issues/884), [mvdan/sh#893](https://github.com/mvdan/sh/pull/893)).
 
 ## v3.13.0 - 2022-06-13
 
-- Added `-n` as an alias to `--dry` ([#776](https://github.com/go-task/task/issues/776), [#777](https://github.com/go-task/task/issues/777)).
-- Fix behavior of interrupt (SIGINT, SIGTERM) signals. Task will now give time for the processes running to do cleanup work ([#458](https://github.com/go-task/task/issues/458), [#479](https://github.com/go-task/task/issues/479), [#728](https://github.com/go-task/task/issues/728), [#769](https://github.com/go-task/task/issues/769)).
-- Add new `--exit-code` (`-x`) flag that will pass-through the exit form the command being ran ([#755](https://github.com/go-task/task/issues/755)).
+- Added `-n` as an alias to `--dry` (#776, #777).
+- Fix behavior of interrupt (SIGINT, SIGTERM) signals. Task will now give time for the processes running to do cleanup work (#458, #479, #728, #769).
+- Add new `--exit-code` (`-x`) flag that will pass-through the exit form the command being ran (#755).
 
 ## v3.12.1 - 2022-05-10
 
-- Fixed bug where, on Windows, variables were ending with `\r` because we were only removing the final `\n` but not `\r\n` ([#717](https://github.com/go-task/task/issues/717)).
+- Fixed bug where, on Windows, variables were ending with `\r` because we were only removing the final `\n` but not `\r\n` (#717).
 
 ## v3.12.0 - 2022-03-31
 
-- The `--list` and `--list-all` flags can now be combined with the `--silent` flag to print the task names only, without their description ([#691](https://github.com/go-task/task/issues/691)).
-- Added support for multi-level inclusion of Taskfiles. This means that included Taskfiles can also include other Taskfiles. Before this was limited to one level ([#390](https://github.com/go-task/task/issues/390), [#623](https://github.com/go-task/task/issues/623), [#656](https://github.com/go-task/task/issues/656)).
-- Add ability to specify vars when including a Taskfile. [Check out the documentation](https://taskfile.dev/#/usage?id=vars-of-included-taskfiles) for more information ([#677](https://github.com/go-task/task/issues/677)).
+- The `--list` and `--list-all` flags can now be combined with the `--silent` flag to print the task names only, without their description (#691).
+- Added support for multi-level inclusion of Taskfiles. This means that included Taskfiles can also include other Taskfiles. Before this was limited to one level (#390, #623, #656).
+- Add ability to specify vars when including a Taskfile. [Check out the documentation](https://taskfile.dev/#/usage?id=vars-of-included-taskfiles) for more information (#677).
 
 ## v3.11.0 - 2022-02-19
 
-- Task now supports printing begin and end messages when using the `group` output mode, useful for grouping tasks in CI systems. [Check out the documentation](http://taskfile.dev/#/usage?id=output-syntax) for more information ([#647](https://github.com/go-task/task/issues/647), [#651](https://github.com/go-task/task/issues/651)).
-- Add `Taskfile.dist.yml` and `Taskfile.dist.yaml` to the supported file name list. [Check out the documentation](https://taskfile.dev/#/usage?id=supported-file-names) for more information ([#498](https://github.com/go-task/task/issues/498), [#666](https://github.com/go-task/task/issues/666)).
+- Task now supports printing begin and end messages when using the `group` output mode, useful for grouping tasks in CI systems. [Check out the documentation](http://taskfile.dev/#/usage?id=output-syntax) for more information (#647, #651).
+- Add `Taskfile.dist.yml` and `Taskfile.dist.yaml` to the supported file name list. [Check out the documentation](https://taskfile.dev/#/usage?id=supported-file-names) for more information (#498, #666).
 
 ## v3.10.0 - 2022-01-04
 
-- A new `--list-all` (alias `-a`) flag is now available. It's similar to the exiting `--list` (`-l`) but prints all tasks, even those without a description ([#383](https://github.com/go-task/task/issues/383), [#401](https://github.com/go-task/task/issues/401)).
-- It's now possible to schedule cleanup commands to run once a task finishes with the `defer:` keyword ([Documentation](https://taskfile.dev/#/usage?id=doing-task-cleanup-with-defer), [#475](https://github.com/go-task/task/issues/475), [#626](https://github.com/go-task/task/issues/626)).
-- Remove long deprecated and undocumented `$` variable prefix and `^` command prefix ([#642](https://github.com/go-task/task/issues/642), [#644](https://github.com/go-task/task/issues/644), [#645](https://github.com/go-task/task/issues/645)).
-- Add support for `.yaml` extension (as an alternative to `.yml`). This was requested multiple times throughout the years. Enjoy! ([#183](https://github.com/go-task/task/issues/183), [#184](https://github.com/go-task/task/issues/184), [#369](https://github.com/go-task/task/issues/369), [#584](https://github.com/go-task/task/issues/584), [#621](https://github.com/go-task/task/issues/621)).
-- Fixed error when computing a variable when the task directory do not exist yet ([#481](https://github.com/go-task/task/issues/481), [#579](https://github.com/go-task/task/issues/579)).
+- A new `--list-all` (alias `-a`) flag is now available. It's similar to the exiting `--list` (`-l`) but prints all tasks, even those without a description (#383, #401).
+- It's now possible to schedule cleanup commands to run once a task finishes with the `defer:` keyword ([Documentation](https://taskfile.dev/#/usage?id=doing-task-cleanup-with-defer),
+
+  # 475, #626).
+- Remove long deprecated and undocumented `$` variable prefix and `^` command prefix (#642, #644, #645).
+- Add support for `.yaml` extension (as an alternative to `.yml`). This was requested multiple times throughout the years. Enjoy! (#183, #184, #369, #584,
+
+  # 621).
+- Fixed error when computing a variable when the task directory do not exist yet (#481, #579).
 
 ## v3.9.2 - 2021-12-02
 
-- Upgrade [mvdan/sh](https://github.com/mvdan/sh) which contains a fix a for a important regression on Windows ([#619](https://github.com/go-task/task/issues/619), [mvdan/sh\[#768\](https://github.com/go-task/task/issues/768)](https://github.com/mvdan/sh/issues/768), [mvdan/sh\[#769\](https://github.com/go-task/task/issues/769)](https://github.com/mvdan/sh/pull/769)).
+- Upgrade [mvdan/sh](https://github.com/mvdan/sh) which contains a fix a for a important regression on Windows (#619, [mvdan/sh#768](https://github.com/mvdan/sh/issues/768), [mvdan/sh#769](https://github.com/mvdan/sh/pull/769)).
 
 ## v3.9.1 - 2021-11-28
 
-- Add logging in verbose mode for when a task starts and finishes ([#533](https://github.com/go-task/task/issues/533), [#588](https://github.com/go-task/task/issues/588)).
-- Fix an issue with preconditions and context errors ([#597](https://github.com/go-task/task/issues/597), [#598](https://github.com/go-task/task/issues/598)).
-- Quote each `{{.CLI_ARGS}}` argument to prevent one with spaces to become many ([#613](https://github.com/go-task/task/issues/613)).
-- Fix nil pointer when `cmd:` was left empty ([#612](https://github.com/go-task/task/issues/612), [#614](https://github.com/go-task/task/issues/614)).
+- Add logging in verbose mode for when a task starts and finishes (#533, #588).
+- Fix an issue with preconditions and context errors (#597, #598).
+- Quote each `{{.CLI_ARGS}}` argument to prevent one with spaces to become many (#613).
+- Fix nil pointer when `cmd:` was left empty (#612, #614).
 - Upgrade [mvdan/sh](https://github.com/mvdan/sh) which contains two relevant fixes:
-  - Fix quote of empty strings in `shellQuote` ([#609](https://github.com/go-task/task/issues/609), [mvdan/sh\[#763\](https://github.com/go-task/task/issues/763)](https://github.com/mvdan/sh/issues/763)).
-  - Fix issue of wrong environment variable being picked when there's another very similar one ([#586](https://github.com/go-task/task/issues/586), [mvdan/sh\[#745\](https://github.com/go-task/task/issues/745)](https://github.com/mvdan/sh/pull/745)).
-- Install shell completions automatically when installing via Homebrew ([#264](https://github.com/go-task/task/issues/264), [#592](https://github.com/go-task/task/issues/592), [go-task/homebrew-tap\[#2\](https://github.com/go-task/task/issues/2)](https://github.com/go-task/homebrew-tap/pull/2)).
+  - Fix quote of empty strings in `shellQuote` (#609, [mvdan/sh#763](https://github.com/mvdan/sh/issues/763)).
+  - Fix issue of wrong environment variable being picked when there's another very similar one (#586, [mvdan/sh#745](https://github.com/mvdan/sh/pull/745)).
+- Install shell completions automatically when installing via Homebrew (#264, #592, [go-task/homebrew-tap#2](https://github.com/go-task/homebrew-tap/pull/2)).
 
 ## v3.9.0 - 2021-10-02
 
-- A new `shellQuote` function was added to the template system (`{{shellQuote "a string"}}`) to ensure a string is safe for use in shell ([mvdan/sh\[#727\](https://github.com/go-task/task/issues/727)](https://github.com/mvdan/sh/pull/727), [mvdan/sh\[#737\](https://github.com/go-task/task/issues/737)](https://github.com/mvdan/sh/pull/737), [Documentation](https://pkg.go.dev/mvdan.cc/sh/v3[@v3](https://github.com/v3).4.0/syntax#Quote))
+- A new `shellQuote` function was added to the template system (`{{shellQuote "a string"}}`) to ensure a string is safe for use in shell ([mvdan/sh#727](https://github.com/mvdan/sh/pull/727), [mvdan/sh#737](https://github.com/mvdan/sh/pull/737), [Documentation](https://pkg.go.dev/mvdan.cc/sh/v3@v3.4.0/syntax#Quote))
 - In this version [mvdan.cc/sh](https://github.com/mvdan/sh) was upgraded with some small fixes and features
-  - The `read -p` flag is now supported ([#314](https://github.com/go-task/task/issues/314), [mvdan/sh\[#551\](https://github.com/go-task/task/issues/551)](https://github.com/mvdan/sh/issues/551), [mvdan/sh\[#772\](https://github.com/go-task/task/issues/772)](https://github.com/mvdan/sh/pull/722))
-  - The `pwd -P` and `pwd -L` flags are now supported ([#553](https://github.com/go-task/task/issues/553), [mvdan/sh\[#724\](https://github.com/go-task/task/issues/724)](https://github.com/mvdan/sh/issues/724), [mvdan/sh\[#728\](https://github.com/go-task/task/issues/728)](https://github.com/mvdan/sh/pull/728))
-  - The `$GID` environment variable is now correctly being set ([#561](https://github.com/go-task/task/issues/561), [mvdan/sh\[#723\](https://github.com/go-task/task/issues/723)](https://github.com/mvdan/sh/pull/723))
+  - The `read -p` flag is now supported (#314, [mvdan/sh#551](https://github.com/mvdan/sh/issues/551), [mvdan/sh#772](https://github.com/mvdan/sh/pull/722))
+  - The `pwd -P` and `pwd -L` flags are now supported (#553, [mvdan/sh#724](https://github.com/mvdan/sh/issues/724), [mvdan/sh#728](https://github.com/mvdan/sh/pull/728))
+  - The `$GID` environment variable is now correctly being set (#561, [mvdan/sh#723](https://github.com/mvdan/sh/pull/723))
 
 ## v3.8.0 - 2021-09-26
 
-- Add `interactive: true` setting to improve support for interactive CLI apps ([#217](https://github.com/go-task/task/issues/217), [#563](https://github.com/go-task/task/issues/563)).
-- Fix some `nil` errors ([#534](https://github.com/go-task/task/issues/534), [#573](https://github.com/go-task/task/issues/573)).
-- Add ability to declare an included Taskfile as optional ([#519](https://github.com/go-task/task/issues/519), [#552](https://github.com/go-task/task/issues/552)).
-- Add support for including Taskfiles in the home directory by using `~` ([#539](https://github.com/go-task/task/issues/539), [#557](https://github.com/go-task/task/issues/557)).
+- Add `interactive: true` setting to improve support for interactive CLI apps (#217, #563).
+- Fix some `nil` errors (#534, #573).
+- Add ability to declare an included Taskfile as optional (#519, #552).
+- Add support for including Taskfiles in the home directory by using `~` (#539, #557).
 
 ## v3.7.3 - 2021-09-04
 
-- Add official support to Apple M1 ([#564](https://github.com/go-task/task/issues/564), [#567](https://github.com/go-task/task/issues/567)).
+- Add official support to Apple M1 (#564, #567).
 - Our [official Homebrew tap](https://github.com/go-task/homebrew-tap) will support more platforms, including Apple M1
 
 ## v3.7.0 - 2021-07-31
 
-- Add `run:` setting to control if tasks should run multiple times or not. Available options are `always` (the default), `when_changed` (if a variable modified the task) and `once` (run only once no matter what). This is a long time requested feature. Enjoy! ([#53](https://github.com/go-task/task/issues/53), [#359](https://github.com/go-task/task/issues/359)).
+- Add `run:` setting to control if tasks should run multiple times or not. Available options are `always` (the default), `when_changed` (if a variable modified the task) and `once` (run only once no matter what). This is a long time requested feature. Enjoy! (#53, #359).
 
 ## v3.6.0 - 2021-07-10
 
-- Allow using both `sources:` and `status:` in the same task ([#411](https://github.com/go-task/task/issues/411), [#427](https://github.com/go-task/task/issues/427), [#477](https://github.com/go-task/task/issues/477)).
-- Small optimization and bug fix: don't compute variables if not needed for `dotenv:` ([#517](https://github.com/go-task/task/issues/517)).
+- Allow using both `sources:` and `status:` in the same task (#411, #427, #477).
+- Small optimization and bug fix: don't compute variables if not needed for `dotenv:` (#517).
 
 ## v3.5.0 - 2021-07-04
 
-- Add support for interpolation in `dotenv:` ([#433](https://github.com/go-task/task/issues/433), [#434](https://github.com/go-task/task/issues/434), [#453](https://github.com/go-task/task/issues/453)).
+- Add support for interpolation in `dotenv:` (#433, #434, #453).
 
 ## v3.4.3 - 2021-05-30
 
-- Add support for the `NO_COLOR` environment variable. ([#459](https://github.com/go-task/task/issues/459), [fatih/color\[#137\](https://github.com/go-task/task/issues/137)](https://github.com/fatih/color/pull/137)).
-- Fix bug where sources were not considering the right directory in `--watch` mode ([#484](https://github.com/go-task/task/issues/484), [#485](https://github.com/go-task/task/issues/485)).
+- Add support for the `NO_COLOR` environment variable. (#459, [fatih/color#137](https://github.com/fatih/color/pull/137)).
+- Fix bug where sources were not considering the right directory in `--watch` mode (#484, #485).
 
 ## v3.4.2 - 2021-04-23
 
-- On watch, report which file failed to read ([#472](https://github.com/go-task/task/issues/472)).
-- Do not try to catch SIGKILL signal, which are not actually possible ([#476](https://github.com/go-task/task/issues/476)).
-- Improve version reporting when building Task from source using Go Modules ([#462](https://github.com/go-task/task/issues/462), [#473](https://github.com/go-task/task/issues/473)).
+- On watch, report which file failed to read (#472).
+- Do not try to catch SIGKILL signal, which are not actually possible (#476).
+- Improve version reporting when building Task from source using Go Modules (#462, #473).
 
 ## v3.4.1 - 2021-04-17
 
-- Improve error reporting when parsing YAML: in some situations where you would just see an generic error, you'll now see the actual error with more detail: the YAML line the failed to parse, for example ([#467](https://github.com/go-task/task/issues/467)).
-- A JSON Schema was published [here](https://json.schemastore.org/taskfile.json) and is automatically being used by some editors like Visual Studio Code ([#135](https://github.com/go-task/task/issues/135)).
-- Print task name before the command in the log output ([#398](https://github.com/go-task/task/issues/398)).
+- Improve error reporting when parsing YAML: in some situations where you would just see an generic error, you'll now see the actual error with more detail: the YAML line the failed to parse, for example (#467).
+- A JSON Schema was published [here](https://json.schemastore.org/taskfile.json) and is automatically being used by some editors like Visual Studio Code (#135).
+- Print task name before the command in the log output (#398).
 
 ## v3.3.0 - 2021-03-20
 
-- Add support for delegating CLI arguments to commands with `--` and a special `CLI_ARGS` variable ([#327](https://github.com/go-task/task/issues/327)).
-- Add a `--concurrency` (alias `-C`) flag, to limit the number of tasks that run concurrently. This is useful for heavy workloads. ([#345](https://github.com/go-task/task/issues/345)).
+- Add support for delegating CLI arguments to commands with `--` and a special `CLI_ARGS` variable (#327).
+- Add a `--concurrency` (alias `-C`) flag, to limit the number of tasks that run concurrently. This is useful for heavy workloads. (#345).
 
 ## v3.2.2 - 2021-01-12
 
-- Improve performance of `--list` and `--summary` by skipping running shell variables for these flags ([#332](https://github.com/go-task/task/issues/332)).
-- Fixed a bug where an environment in a Taskfile was not always overridable by the system environment ([#425](https://github.com/go-task/task/issues/425)).
-- Fixed environment from .env files not being available as variables ([#379](https://github.com/go-task/task/issues/379)).
-- The install script is now working for ARM platforms ([#428](https://github.com/go-task/task/issues/428)).
+- Improve performance of `--list` and `--summary` by skipping running shell variables for these flags (#332).
+- Fixed a bug where an environment in a Taskfile was not always overridable by the system environment (#425).
+- Fixed environment from .env files not being available as variables (#379).
+- The install script is now working for ARM platforms (#428).
 
 ## v3.2.1 - 2021-01-09
 
-- Fixed some bugs and regressions regarding dynamic variables and directories ([#426](https://github.com/go-task/task/issues/426)).
+- Fixed some bugs and regressions regarding dynamic variables and directories (#426).
 - The [slim-sprig](https://github.com/go-task/slim-sprig) package was updated with the upstream [sprig](https://github.com/Masterminds/sprig).
 
 ## v3.2.0 - 2021-01-07
 
-- Fix the `.task` directory being created in the task directory instead of the Taskfile directory ([#247](https://github.com/go-task/task/issues/247)).
-- Fix a bug where dynamic variables (those declared with `sh:`) were not running in the task directory when the task has a custom dir or it was in an included Taskfile ([#384](https://github.com/go-task/task/issues/384)).
-- The watch feature (via the `--watch` flag) got a few different bug fixes and should be more stable now ([#423](https://github.com/go-task/task/issues/423), [#365](https://github.com/go-task/task/issues/365)).
+- Fix the `.task` directory being created in the task directory instead of the Taskfile directory (#247).
+- Fix a bug where dynamic variables (those declared with `sh:`) were not running in the task directory when the task has a custom dir or it was in an included Taskfile (#384).
+- The watch feature (via the `--watch` flag) got a few different bug fixes and should be more stable now (#423, #365).
 
 ## v3.1.0 - 2021-01-03
 
-- Fix a bug when the checksum up-to-date resolution is used by a task with a custom `label:` attribute ([#412](https://github.com/go-task/task/issues/412)).
-- Starting from this release, we're releasing official ARMv6 and ARM64 binaries for Linux ([#375](https://github.com/go-task/task/issues/375), [#418](https://github.com/go-task/task/issues/418)).
-- Task now respects the order of declaration of included Taskfiles when evaluating variables declaring by them ([#393](https://github.com/go-task/task/issues/393)).
-- `set -e` is now automatically set on every command. This was done to fix an issue where multiline string commands wouldn't really fail unless the sentence was in the last line ([#403](https://github.com/go-task/task/issues/403)).
+- Fix a bug when the checksum up-to-date resolution is used by a task with a custom `label:` attribute (#412).
+- Starting from this release, we're releasing official ARMv6 and ARM64 binaries for Linux (#375, #418).
+- Task now respects the order of declaration of included Taskfiles when evaluating variables declaring by them (#393).
+- `set -e` is now automatically set on every command. This was done to fix an issue where multiline string commands wouldn't really fail unless the sentence was in the last line (#403).
 
 ## v3.0.1 - 2020-12-26
 
-- Allow use as a library by moving the required packages out of the `internal` directory ([#358](https://github.com/go-task/task/issues/358)).
-- Do not error if a specified dotenv file does not exist ([#378](https://github.com/go-task/task/issues/378), [#385](https://github.com/go-task/task/issues/385)).
-- Fix panic when you have empty tasks in your Taskfile ([#338](https://github.com/go-task/task/issues/338), [#362](https://github.com/go-task/task/issues/362)).
+- Allow use as a library by moving the required packages out of the `internal` directory (#358).
+- Do not error if a specified dotenv file does not exist (#378, #385).
+- Fix panic when you have empty tasks in your Taskfile (#338, #362).
 
 ## v3.0.0 - 2020-08-16
 
-- On `v3`, all CLI variables will be considered global variables ([#336](https://github.com/go-task/task/issues/336), [#341](https://github.com/go-task/task/issues/341))
-- Add support to `.env` like files ([#324](https://github.com/go-task/task/issues/324), [#356](https://github.com/go-task/task/issues/356)).
-- Add `label:` to task so you can override the task name in the logs ([\[#321\](https://github.com/go-task/task/issues/321)](https://github.com/go-task/task/issues/321]), [#337](https://github.com/go-task/task/issues/337)).
-- Refactor how variables work on version 3 ([#311](https://github.com/go-task/task/issues/311)).
+- On `v3`, all CLI variables will be considered global variables (#336, #341)
+- Add support to `.env` like files (#324, #356).
+- Add `label:` to task so you can override the task name in the logs (#321,
+
+  # 337).
+- Refactor how variables work on version 3 (#311).
 - Disallow `expansions` on v3 since it has no effect.
 - `Taskvars.yml` is not automatically included anymore.
 - `Taskfile_{{OS}}.yml` is not automatically included anymore.
 - Allow interpolation on `includes`, so you can manually include a Taskfile based on operation system, for example.
-- Expose `.TASK` variable in templates with the task name ([#252](https://github.com/go-task/task/issues/252)).
-- Implement short task syntax ([#194](https://github.com/go-task/task/issues/194), [#240](https://github.com/go-task/task/issues/240)).
-- Added option to make included Taskfile run commands on its own directory ([#260](https://github.com/go-task/task/issues/260), [#144](https://github.com/go-task/task/issues/144))
-- Taskfiles in version 1 are not supported anymore ([#237](https://github.com/go-task/task/issues/237)).
-- Added global `method:` option. With this option, you can set a default method to all tasks in a Taskfile ([#246](https://github.com/go-task/task/issues/246)).
-- Changed default method from `timestamp` to `checksum` ([#246](https://github.com/go-task/task/issues/246)).
-- New magic variables are now available when using `status:`: `.TIMESTAMP` which contains the greatest modification date from the files listed in `sources:`, and `.CHECKSUM`, which contains a checksum of all files listed in `status:`. This is useful for manual checking when using external, or even remote, artifacts when using `status:` ([#216](https://github.com/go-task/task/issues/216)).
-- We're now using [slim-sprig](https://github.com/go-task/slim-sprig) instead of [sprig](https://github.com/Masterminds/sprig), which allowed a file size reduction of about 22% ([#219](https://github.com/go-task/task/issues/219)).
-- We now use some colors on Task output to better distinguish message types - commands are green, errors are red, etc ([#207](https://github.com/go-task/task/issues/207)).
+- Expose `.TASK` variable in templates with the task name (#252).
+- Implement short task syntax (#194, #240).
+- Added option to make included Taskfile run commands on its own directory (#260, #144)
+- Taskfiles in version 1 are not supported anymore (#237).
+- Added global `method:` option. With this option, you can set a default method to all tasks in a Taskfile (#246).
+- Changed default method from `timestamp` to `checksum` (#246).
+- New magic variables are now available when using `status:`: `.TIMESTAMP` which contains the greatest modification date from the files listed in `sources:`, and `.CHECKSUM`, which contains a checksum of all files listed in `status:`. This is useful for manual checking when using external, or even remote, artifacts when using `status:` (#216).
+- We're now using [slim-sprig](https://github.com/go-task/slim-sprig) instead of [sprig](https://github.com/Masterminds/sprig), which allowed a file size reduction of about 22% (#219).
+- We now use some colors on Task output to better distinguish message types - commands are green, errors are red, etc (#207).
 
 ## v2.8.1 - 2020-05-20
 
-- Fix error code for the `--help` flag ([#300](https://github.com/go-task/task/issues/300), [#330](https://github.com/go-task/task/issues/330)).
-- Print version to stdout instead of stderr ([#299](https://github.com/go-task/task/issues/299), [#329](https://github.com/go-task/task/issues/329)).
-- Supress `context` errors when using the `--watch` flag ([#313](https://github.com/go-task/task/issues/313), [#317](https://github.com/go-task/task/issues/317)).
-- Support templating on description ([#276](https://github.com/go-task/task/issues/276), [#283](https://github.com/go-task/task/issues/283)).
+- Fix error code for the `--help` flag (#300, #330).
+- Print version to stdout instead of stderr (#299, #329).
+- Supress `context` errors when using the `--watch` flag (#313, #317).
+- Support templating on description (#276, #283).
 
 ## v2.8.0 - 2019-12-07
 
-- Add `--parallel` flag (alias `-p`) to run tasks given by the command line in parallel ([#266](https://github.com/go-task/task/issues/266)).
+- Add `--parallel` flag (alias `-p`) to run tasks given by the command line in parallel (#266).
 - Fixed bug where calling the `task` CLI only informing global vars would not execute the `default` task.
 - Add hability to silent all tasks by adding `silent: true` a the root of the Taskfile.
 
 ## v2.7.1 - 2019-11-10
 
-- Fix error being raised when `exit 0` was called ([#251](https://github.com/go-task/task/issues/251)).
+- Fix error being raised when `exit 0` was called (#251).
 
 ## v2.7.0 - 2019-09-22
 
-- Fixed panic bug when assigning a global variable ([#229](https://github.com/go-task/task/issues/229), [#243](https://github.com/go-task/task/issues/243)).
-- A task with `method: checksum` will now re-run if generated files are deleted ([#228](https://github.com/go-task/task/issues/228), [#238](https://github.com/go-task/task/issues/238)).
+- Fixed panic bug when assigning a global variable (#229, #243).
+- A task with `method: checksum` will now re-run if generated files are deleted (#228, #238).
 
 ## v2.6.0 - 2019-07-21
 
 - Fixed some bugs regarding minor version checks on `version:`.
-- Add `preconditions:` to task ([#205](https://github.com/go-task/task/issues/205)).
-- Create directory informed on `dir:` if it doesn't exist ([#209](https://github.com/go-task/task/issues/209), [#211](https://github.com/go-task/task/issues/211)).
-- We now have a `--taskfile` flag (alias `-t`), which can be used to run another Taskfile (other than the default `Taskfile.yml`) ([#221](https://github.com/go-task/task/issues/221)).
-- It's now possible to install Task using Homebrew on Linux ([go-task/homebrew-tap\[#1\](https://github.com/go-task/task/issues/1)](https://github.com/go-task/homebrew-tap/pull/1)).
+- Add `preconditions:` to task (#205).
+- Create directory informed on `dir:` if it doesn't exist (#209, #211).
+- We now have a `--taskfile` flag (alias `-t`), which can be used to run another Taskfile (other than the default `Taskfile.yml`) (#221).
+- It's now possible to install Task using Homebrew on Linux ([go-task/homebrew-tap#1](https://github.com/go-task/homebrew-tap/pull/1)).
 
 ## v2.5.2 - 2019-05-11
 
-- Reverted YAML upgrade due issues with CRLF on Windows ([#201](https://github.com/go-task/task/issues/201), [go-yaml/yaml\[#450\](https://github.com/go-task/task/issues/450)](https://github.com/go-yaml/yaml/issues/450)).
-- Allow setting global variables through the CLI ([#192](https://github.com/go-task/task/issues/192)).
+- Reverted YAML upgrade due issues with CRLF on Windows (#201, [go-yaml/yaml#450](https://github.com/go-yaml/yaml/issues/450)).
+- Allow setting global variables through the CLI (#192).
 
 ## 2.5.1 - 2019-04-27
 
-- Fixed some issues with interactive command line tools, where sometimes the output were not being shown, and similar issues ([#114](https://github.com/go-task/task/issues/114), [#190](https://github.com/go-task/task/issues/190), [#200](https://github.com/go-task/task/issues/200)).
+- Fixed some issues with interactive command line tools, where sometimes the output were not being shown, and similar issues (#114, #190, #200).
 - Upgraded [go-yaml/yaml](https://github.com/go-yaml/yaml) from v2 to v3.
 
 ## v2.5.0 - 2019-03-16
 
 - We moved from the taskfile.org domain to the new fancy taskfile.dev domain. While stuff is being redirected, we strongly recommend to everyone that use [this install script](https://taskfile.dev/#/installation?id=install-script) to use the new taskfile.dev domain on scripts from now on.
-- Fixed to the ZSH completion ([#182](https://github.com/go-task/task/issues/182)).
-- Add [`--summary` flag along with `summary:` task attribute](https://taskfile.org/#/usage?id=display-summary-of-task) ([#180](https://github.com/go-task/task/issues/180)).
+- Fixed to the ZSH completion (#182).
+- Add [`--summary` flag along with `summary:` task attribute](https://taskfile.org/#/usage?id=display-summary-of-task) (#180).
 
 ## v2.4.0 - 2019-02-21
 
-- Allow calling a task of the root Taskfile from an included Taskfile by prefixing it with `:` ([#161](https://github.com/go-task/task/issues/161), [#172](https://github.com/go-task/task/issues/172)).
-- Add flag to override the `output` option ([#173](https://github.com/go-task/task/issues/173)).
-- Fix bug where Task was persisting the new checksum on the disk when the Dry Mode is enabled ([#166](https://github.com/go-task/task/issues/166)).
-- Fix file timestamp issue when the file name has spaces ([#176](https://github.com/go-task/task/issues/176)).
-- Mitigating path expanding issues on Windows ([#170](https://github.com/go-task/task/issues/170)).
+- Allow calling a task of the root Taskfile from an included Taskfile by prefixing it with `:` (#161, #172).
+- Add flag to override the `output` option (#173).
+- Fix bug where Task was persisting the new checksum on the disk when the Dry Mode is enabled (#166).
+- Fix file timestamp issue when the file name has spaces (#176).
+- Mitigating path expanding issues on Windows (#170).
 
 ## v2.3.0 - 2019-01-02
 
-- On Windows, Task can now be installed using [Scoop](https://scoop.sh/) ([#152](https://github.com/go-task/task/issues/152)).
-- Fixed issue with file/directory globing ([#153](https://github.com/go-task/task/issues/153)).
-- Added ability to globally set environment variables ([#138](https://github.com/go-task/task/issues/138), [#159](https://github.com/go-task/task/issues/159)).
+- On Windows, Task can now be installed using [Scoop](https://scoop.sh/) (#152).
+- Fixed issue with file/directory globing (#153).
+- Added ability to globally set environment variables (#138, #159).
 
 ## v2.2.1 - 2018-12-09
 
-- This repository now uses Go Modules ([#143](https://github.com/go-task/task/issues/143)). We'll still keep the `vendor` directory in sync for some time, though;
-- Fixing a bug when the Taskfile has no tasks but includes another Taskfile ([#150](https://github.com/go-task/task/issues/150));
-- Fix a bug when calling another task or a dependency in an included Taskfile ([#151](https://github.com/go-task/task/issues/151)).
+- This repository now uses Go Modules (#143). We'll still keep the `vendor` directory in sync for some time, though;
+- Fixing a bug when the Taskfile has no tasks but includes another Taskfile (#150);
+- Fix a bug when calling another task or a dependency in an included Taskfile (#151).
 
 ## v2.2.0 - 2018-10-25
 
-- Added support for [including other Taskfiles](https://taskfile.org/#/usage?id=including-other-taskfiles) ([#98](https://github.com/go-task/task/issues/98))
-  - This should be considered experimental. For now, only including local files is supported, but support for including remote Taskfiles is being discussed. If you have any feedback, please comment on [#98](https://github.com/go-task/task/issues/98).
+- Added support for [including other Taskfiles](https://taskfile.org/#/usage?id=including-other-taskfiles) (#98)
+  - This should be considered experimental. For now, only including local files is supported, but support for including remote Taskfiles is being discussed. If you have any feedback, please comment on #98.
 - Task now have a dedicated documentation site: https://taskfile.org
   - Thanks to [Docsify](https://docsify.js.org/) for making this pretty easy. To check the source code, just take a look at the [docs](https://github.com/go-task/task/tree/main/docs) directory of this repository. Contributions to the documentation is really appreciated.
 
 ## v2.1.1 - 2018-09-17
 
 - Fix suggestion to use `task --init` not being shown anymore (when a `Taskfile.yml` is not found)
-- Fix error when using checksum method and no file exists for a source glob ([#131](https://github.com/go-task/task/issues/131))
-- Fix signal handling when the `--watch` flag is given ([#132](https://github.com/go-task/task/issues/132))
+- Fix error when using checksum method and no file exists for a source glob (#131)
+- Fix signal handling when the `--watch` flag is given (#132)
 
 ## v2.1.0 - 2018-08-19
 
-- Add a `ignore_error` option to task and command ([#123](https://github.com/go-task/task/issues/123))
-- Add a dry run mode (`--dry` flag) ([#126](https://github.com/go-task/task/issues/126))
+- Add a `ignore_error` option to task and command (#123)
+- Add a dry run mode (`--dry` flag) (#126)
 
 ## v2.0.3 - 2018-06-24
 
-- Expand environment variables on "dir", "sources" and "generates" ([#116](https://github.com/go-task/task/issues/116))
-- Fix YAML merging syntax ([#112](https://github.com/go-task/task/issues/112))
-- Add ZSH completion ([#111](https://github.com/go-task/task/issues/111))
+- Expand environment variables on "dir", "sources" and "generates" (#116)
+- Fix YAML merging syntax (#112)
+- Add ZSH completion (#111)
 - Implement new `output` option. Please check out the [documentation](https://github.com/go-task/task#output-syntax)
 
 ## v2.0.2 - 2018-05-01
 
-- Fix merging of YAML anchors ([#112](https://github.com/go-task/task/issues/112))
+- Fix merging of YAML anchors (#112)
 
 ## v2.0.1 - 2018-03-11
 
@@ -400,36 +479,36 @@ Version 2.0.0 is here, with a new Taskfile format.
 
 Please, make sure to read the [Taskfile versions](https://github.com/go-task/task/blob/main/TASKFILE_VERSIONS.md) document, since it describes in depth what changed for this version.
 
-- New Taskfile version 2 ([#77](https://github.com/go-task/task/issues/77))
-- Possibility to have global variables in the `Taskfile.yml` instead of `Taskvars.yml` ([#66](https://github.com/go-task/task/issues/66))
+- New Taskfile version 2 (#77)
+- Possibility to have global variables in the `Taskfile.yml` instead of `Taskvars.yml` (#66)
 - Small improvements and fixes
 
 ## v1.4.4 - 2017-11-19
 
-- Handle SIGINT and SIGTERM ([#75](https://github.com/go-task/task/issues/75));
+- Handle SIGINT and SIGTERM (#75);
 - List: print message with there's no task with description;
-- Expand home dir ("~" symbol) on paths ([#74](https://github.com/go-task/task/issues/74));
+- Expand home dir ("~" symbol) on paths (#74);
 - Add Snap as an installation method;
 - Move examples to its own repo;
 - Watch: also walk on tasks called on on "cmds", and not only on "deps";
-- Print logs to stderr instead of stdout ([#68](https://github.com/go-task/task/issues/68));
+- Print logs to stderr instead of stdout (#68);
 - Remove deprecated `set` keyword;
 - Add checksum based status check, alternative to timestamp based.
 
 ## v1.4.3 - 2017-09-07
 
-- Allow assigning variables to tasks at run time via CLI ([#33](https://github.com/go-task/task/issues/33))
-- Added suport for multiline variables from sh ([#64](https://github.com/go-task/task/issues/64))
-- Fixes env: remove square braces and evaluate shell ([#62](https://github.com/go-task/task/issues/62))
+- Allow assigning variables to tasks at run time via CLI (#33)
+- Added suport for multiline variables from sh (#64)
+- Fixes env: remove square braces and evaluate shell (#62)
 - Watch: change watch library and few fixes and improvements
-- When use watching, cancel and restart long running process on file change ([#59](https://github.com/go-task/task/issues/59) and [#60](https://github.com/go-task/task/issues/60))
+- When use watching, cancel and restart long running process on file change (#59 and #60)
 
 ## v1.4.2 - 2017-07-30
 
 - Flag to set directory of execution
 - Always echo command if is verbose mode
 - Add silent mode to disable echoing of commands
-- Fixes and improvements of variables ([#56](https://github.com/go-task/task/issues/56))
+- Fixes and improvements of variables (#56)
 
 ## v1.4.1 - 2017-07-15
 
@@ -437,28 +516,28 @@ Please, make sure to read the [Taskfile versions](https://github.com/go-task/tas
   - `VAR: {sh: echo Hello}` instead of `VAR: $echo Hello`
 - Add `--list` (or `-l`) flag to print existing tasks
 - OS specific Taskvars file (e.g. `Taskvars_windows.yml`, `Taskvars_linux.yml`, etc)
-- Consider task up-to-date on equal timestamps ([#49](https://github.com/go-task/task/issues/49))
-- Allow absolute path in generates section ([#48](https://github.com/go-task/task/issues/48))
-- Bugfix: allow templating when calling deps ([#42](https://github.com/go-task/task/issues/42))
+- Consider task up-to-date on equal timestamps (#49)
+- Allow absolute path in generates section (#48)
+- Bugfix: allow templating when calling deps (#42)
 - Fix panic for invalid task in cyclic dep detection
-- Better error output for dynamic variables in Taskvars.yml ([#41](https://github.com/go-task/task/issues/41))
+- Better error output for dynamic variables in Taskvars.yml (#41)
 - Allow template evaluation in parameters
 
 ## v1.4.0 - 2017-07-06
 
 - Cache dynamic variables
 - Add verbose mode (`-v` flag)
-- Support to task parameters (overriding vars) ([#31](https://github.com/go-task/task/issues/31)) ([#32](https://github.com/go-task/task/issues/32))
-- Print command, also when "set:" is specified ([#35](https://github.com/go-task/task/issues/35))
-- Improve task command help text ([#35](https://github.com/go-task/task/issues/35))
+- Support to task parameters (overriding vars) (#31) (#32)
+- Print command, also when "set:" is specified (#35)
+- Improve task command help text (#35)
 
 ## v1.3.1 - 2017-06-14
 
-- Fix glob not working on commands ([#28](https://github.com/go-task/task/issues/28))
+- Fix glob not working on commands (#28)
 - Add ExeExt template function
 - Add `--init` flag to create a new Taskfile
-- Add status option to prevent task from running ([#27](https://github.com/go-task/task/issues/27))
-- Allow interpolation on `generates` and `sources` attributes ([#26](https://github.com/go-task/task/issues/26))
+- Add status option to prevent task from running (#27)
+- Allow interpolation on `generates` and `sources` attributes (#26)
 
 ## v1.3.0 - 2017-04-24
 
@@ -476,18 +555,18 @@ Please, make sure to read the [Taskfile versions](https://github.com/go-task/tas
 - Watch a task (experimental)
 - Possibility to call another task
 - Fix "=" not being reconized in variables/environment variables
-- Tasks can now have a description, and help will print them ([#10](https://github.com/go-task/task/issues/10))
+- Tasks can now have a description, and help will print them (#10)
 - Task dependencies now run concurrently
-- Support for a default task ([#16](https://github.com/go-task/task/issues/16))
+- Support for a default task (#16)
 
 ## v1.1.0 - 2017-03-08
 
-- Support for YAML, TOML and JSON ([#1](https://github.com/go-task/task/issues/1))
-- Support running command in another directory ([#4](https://github.com/go-task/task/issues/4))
+- Support for YAML, TOML and JSON (#1)
+- Support running command in another directory (#4)
 - `--force` or `-f` flag to force execution of task even when it's up-to-date
-- Detection of cyclic dependencies ([#5](https://github.com/go-task/task/issues/5))
-- Support for variables ([#6](https://github.com/go-task/task/issues/6), [#9](https://github.com/go-task/task/issues/9), [#14](https://github.com/go-task/task/issues/14))
-- Operation System specific commands and variables ([#13](https://github.com/go-task/task/issues/13))
+- Detection of cyclic dependencies (#5)
+- Support for variables (#6, #9, #14)
+- Operation System specific commands and variables (#13)
 
 ## v1.0.0 - 2017-02-28
 

docs/i18n/fr-FR/docusaurus-plugin-content-docs/current/community.md

@@ -1,6 +1,6 @@
 ---
 slug: /community/
-sidebar_position: 10
+sidebar_position: 9
 ---
 
 # Communauté
@@ -9,7 +9,7 @@ Certains travaux d'amélioration de l'écosystème Task sont réalisés par la c
 
 ## Traductions
 
-We use [Crowdin](https://crowdin.com/project/taskfile) to translate our document.
+Nous utilisons [Crowdin](https://crowdin.com/project/taskfile) pour traduire nos documents.
 
 ## Intégrations
 
@@ -19,8 +19,8 @@ Un grand nombre de nos intégrations sont apportées et maintenues par la commun
 
 Certaines méthodes d'installation sont maintenues par un tiers :
 
-- [Actions GitHub](https://github.com/arduino/setup-task) par [@arduino](https://github.com/arduino)
-- [AUR](https://aur.archlinux.org/packages/go-task-bin) par [@carlsmedstad](https://github.com/carlsmedstad)
+- [GitHub Actions](https://github.com/arduino/setup-task) by @arduino
+- [AUR](https://aur.archlinux.org/packages/go-task-bin) by @carlsmedstad
 - [Scoop](https://github.com/ScoopInstaller/Main/blob/master/bucket/task.json)
 - [Fedora](https://packages.fedoraproject.org/pkgs/golang-github-task/go-task/)
 - [NixOS](https://github.com/NixOS/nixpkgs/blob/master/pkgs/development/tools/go-task/default.nix)

docs/i18n/fr-FR/docusaurus-plugin-content-docs/current/contributing.md

@@ -41,9 +41,9 @@ To run Task for Visual Studio Code, you can open the project in VSCode and hit F
 
 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 docs` (requires `nodejs` & `yarn`). All content is written in Markdown and is located in the `docs/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.md) is necessary. This document contains descriptions and examples of how to use Task features. If you're adding a new feature, try to find an appropriate place to add a new section. If you're updating an existing feature, ensure that the documentation and any examples are up-to-date. Ensure that any examples follow the [Taskfile Styleguide](./styleguide.md).
+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 features. If you're adding a new feature, try to find an appropriate place to add a new section. If you're updating an existing feature, ensure that the documentation and any examples are up-to-date. Ensure that any examples follow the [Taskfile Styleguide](/styleguide).
 
-If you added a new field, command or flag, ensure that you add it to the [API Reference](./api_reference.md). New fields also need to be added to the [JSON Schema][json-schema]. The descriptions for fields in the API reference and the schema should match.
+If you added a new field, command or flag, ensure that you add it to the [API Reference](/api). New fields also need to be added to the [JSON Schema][json-schema]. The descriptions for fields in the API reference and the schema should match.
 
 ### Writing tests
 
@@ -72,7 +72,7 @@ If you're not sure how to format your commit message, check out [Conventional Co
 
 Take a look at the list of [open issues for Task][task-open-issues] or [Task for Visual Studio Code][vscode-task-open-issues]. We have a [good first issue][good-first-issue] label for simpler issues that are ideal for first time contributions.
 
-All kinds of contributions are welcome, whether its a typo fix or a shiny new feature. You can also contribute by upvoting/commenting on issues, helping to answer questions or contributing to other [community projects](./community.md).
+All kinds of contributions are welcome, whether its a typo fix or a shiny new feature. You can also contribute by upvoting/commenting on issues, helping to answer questions or contributing to other [community projects](/community).
 
 > I'm stuck, where can I get help?
 

docs/i18n/fr-FR/docusaurus-plugin-content-docs/current/deprecations/deprecations.md

@@ -0,0 +1,12 @@
+---
+slug: /deprecations/
+sidebar_position: 7
+---
+
+# Dépréciations
+
+Au fur et à mesure que Task évolue, certaines de ses fonctionnalités peuvent se montrer obsolètes. Cela peut être dû au fait qu'elles ne sont plus utiles, parce qu'une autre fonctionnalité l'a remplacée ou à cause d'un changement dans la façon dont la tâche fonctionne.
+
+Lorsque cela se produit, nous marquons la fonctionnalité comme obsolète. Cela signifie que sera supprimé dans une future version de Task. La fonctionnalité continuera de fonctionner en attendant, mais il vous est fortement recommandé de ne plus l'utiliser et de planifier un plan de migration pour changer toutes les tâches pouvant l'utiliser.
+
+Vous pouvez afficher une liste complète des dépréciations actives dans la section "Dépréciations" de la barre latérale.

docs/i18n/fr-FR/docusaurus-plugin-content-docs/current/deprecations/template.md

@@ -0,0 +1,22 @@
+---
+#This is a template for an experiments documentation
+#Copy this page and fill in the details as necessary
+title: '--- Template ---'
+sidebar_position: -1 #Always push to the top
+draft: true #Hide in production
+---
+
+# \{Name of Deprecated Feature\} (#\{Issue\})
+
+:::warning
+
+This deprecation breaks the following functionality:
+
+- \{list any existing functionality that will be broken by this deprecation\}
+- \{if there are no breaking changes, remove this admonition\}
+
+:::
+
+\{Short description of the feature/behavior and why it is being deprecated\}
+
+\{Short explanation of any replacement features/behaviors and how users should migrate to it\}

docs/i18n/fr-FR/docusaurus-plugin-content-docs/current/deprecations/version_2_schema.md

@@ -0,0 +1,25 @@
+---
+slug: /deprecations/version-2-schema/
+---
+
+# Version 2 Schema (#1197)
+
+:::warning
+
+This deprecation breaks the following functionality:
+
+- Any Taskfiles that use the version 2 schema
+- `Taskvar.yml` files
+
+:::
+
+The Taskfile version 2 schema was introduced in March 2018 and replaced by version 3 in August 2019. In May 2023 [we published a deprecation notice][deprecation-notice] for the version 2 schema on the basis that the vast majority of users had already upgraded to version 3 and removing support for version 2 would allow us to tidy up the codebase and focus on new functionality instead.
+
+In December 2023, the final version of Task that supports the version 2 schema ([v3.33.0][v3.33.0]) was published and all legacy code was removed from Task's main branch. To use a more recent version of Task, you will need to ensure that your Taskfile uses the version 3 schema instead. A list of changes between version 2 and version 3 are available in the [Task v3 Release Notes][v3.0.0].
+
+<!-- prettier-ignore-start -->
+
+<!-- prettier-ignore-end -->
+[v3.0.0]: https://github.com/go-task/task/releases/tag/v3.0.0
+[v3.33.0]: https://github.com/go-task/task/releases/tag/v3.33.0
+[deprecation-notice]: https://github.com/go-task/task/issues/1197

docs/i18n/fr-FR/docusaurus-plugin-content-docs/current/donate.md

@@ -1,6 +1,6 @@
 ---
 slug: /donate/
-sidebar_position: 15
+sidebar_position: 16
 ---
 
 # Faire un don
@@ -13,7 +13,7 @@ Les entreprises qui font un don d'au moins 50$/mois seront présentées comme un
 
 ## Sponsors GitHub
 
-La façon préférée de faire un don aux mainteneurs du projet est d'utiliser les sponsors GitHub. Utilisez simplement le lien suivant pour faire votre don :
+La façon préférée de faire un don aux mainteneurs du projet est d'utiliser les sponsors GitHub. Vous pouvez utiliser le lien suivant pour faire votre don. We suggest a 50/50 split to each maintainer of the total amount you plan to donate to the project.
 
 - [@andreynering](https://github.com/sponsors/andreynering)
 - [@pd93](https://github.com/sponsors/pd93)

docs/i18n/fr-FR/docusaurus-plugin-content-docs/current/experiments/any_variables.md

@@ -0,0 +1,206 @@
+---
+slug: /experiments/any-variables/
+---
+
+# Any Variables (#1415)
+
+:::caution
+
+All experimental features are subject to breaking changes and/or removal _at any
+time_. We strongly recommend that you do not use these features in a production
+environment. They are intended for testing and feedback only.
+
+:::
+
+:::warning
+
+This experiment breaks the following functionality:
+
+- Dynamically defined variables (using the `sh` keyword)
+
+:::
+
+:::info
+
+To enable this experiment, set the environment variable:
+`TASK_X_ANY_VARIABLES=1`. Check out [our guide to enabling experiments
+][enabling-experiments] for more information.
+
+:::
+
+Currently, Task only supports string variables. This experiment allows you to
+specify and use the following variable types:
+
+- `string`
+- `bool`
+- `int`
+- `float`
+- `array`
+- `map`
+
+This allows you to have a lot more flexibility in how you use variables in
+Task's templating engine. For example:
+
+Evaluating booleans:
+
+```yaml
+version: 3
+
+tasks:
+  foo:
+    vars:
+      BOOL: false
+    cmds:
+      - '{{if .BOOL}}echo foo{{end}}'
+```
+
+Arithmetic:
+
+```yaml
+version: 3
+
+tasks:
+  foo:
+    vars:
+      INT: 10
+      FLOAT: 3.14159
+    cmds:
+      - 'echo {{add .INT .FLOAT}}'
+```
+
+Ranging:
+
+```yaml
+version: 3
+
+tasks:
+  foo:
+    vars:
+      ARRAY: [1, 2, 3]
+    cmds:
+      - 'echo {{range .ARRAY}}{{.}}{{end}}'
+```
+
+There are many more templating functions which can be used with the new types of
+variables. For a full list, see the [slim-sprig][slim-sprig] documentation.
+
+## Looping over variables
+
+Previously, you would have to use a delimiter separated string to loop over an
+arbitrary list of items in a variable and split them by using the `split` subkey
+to specify the delimiter:
+
+```yaml
+version: 3
+
+tasks:
+  foo:
+    vars:
+      LIST: 'foo,bar,baz'
+    cmds:
+      - for:
+          var: LIST
+          split: ','
+        cmd: echo {{.ITEM}}
+```
+
+Because this experiment adds support for "collection-type" variables, the `for`
+keyword has been updated to support looping over arrays directly:
+
+```yaml
+version: 3
+
+tasks:
+  foo:
+    vars:
+      LIST: [foo, bar, baz]
+    cmds:
+      - for:
+          var: LIST
+        cmd: echo {{.ITEM}}
+```
+
+This also works for maps. When looping over a map we also make an additional
+`{{.KEY}}` variable availabe that holds the string value of the map key.
+Remember that maps are unordered, so the order in which the items are looped
+over is random:
+
+```yaml
+version: 3
+
+tasks:
+  foo:
+    vars:
+      MAP:
+        KEY_1:
+          SUBKEY: sub_value_1
+        KEY_2:
+          SUBKEY: sub_value_2
+        KEY_3:
+          SUBKEY: sub_value_3
+    cmds:
+      - for:
+          var: MAP
+        cmd: echo {{.KEY}} {{.ITEM.SUBKEY}}
+```
+
+String splitting is still supported and remember that for simple cases, you have
+always been able to loop over an array without using variables at all:
+
+```yaml
+version: 3
+
+tasks:
+  foo:
+    cmds:
+      - for: [foo, bar, baz]
+        cmd: echo {{.ITEM}}
+```
+
+## Migration
+
+Taskfiles with dynamically defined variables via the `sh` subkey will no longer
+work with this experiment enabled. In order to keep using dynamically defined
+variables, you will need to migrate your Taskfile to use the new syntax.
+
+Previously, you might have defined a dynamic variable like this:
+
+```yaml
+version: 3
+
+task:
+  foo:
+    vars:
+      CALCULATED_VAR:
+        sh: 'echo hello'
+    cmds:
+      - 'echo {{.CALCULATED_VAR}}'
+```
+
+With this experiment enabled, you will need to remove the `sh` subkey and define
+your command as a string that begins with a `$`. This will instruct Task to
+interpret the string as a command instead of a literal value and the variable
+will be populated with the output of the command. For example:
+
+```yaml
+version: 3
+
+task:
+  foo:
+    vars:
+      CALCULATED_VAR: '$echo hello'
+    cmds:
+      - 'echo {{.CALCULATED_VAR}}'
+```
+
+If your current Taskfile contains a string variable that begins with a `$`, you
+will now need to escape the `$` with a backslash (`\`) to stop Task from
+executing it as a command.
+
+<!-- prettier-ignore-start -->
+
+[enabling-experiments]: /experiments/#enabling-experiments
+
+[slim-sprig]: https://go-task.github.io/slim-sprig/
+
+<!-- prettier-ignore-end -->

docs/i18n/fr-FR/docusaurus-plugin-content-docs/current/experiments/any_variables.mdx

@@ -0,0 +1,162 @@
+---
+slug: /experiments/any-variables/
+---
+
+# Any Variables
+
+-   Issue: #1415
+-   Environment variable: `TASK_X_ANY_VARIABLES=1`
+-   Breaks:
+    -   Dynamically defined variables (using the `sh` keyword)
+
+Currently, Task only supports string variables. This experiment allows you to
+specify and use the following variable types:
+
+-   `string`
+-   `bool`
+-   `int`
+-   `float`
+-   `array`
+-   `map`
+
+This allows you to have a lot more flexibility in how you use variables in
+Task's templating engine. For example:
+
+Evaluating booleans:
+
+```yaml
+version: 3
+
+tasks:
+  foo:
+    vars:
+      BOOL: false
+    cmds:
+      - '{{if .BOOL}}echo foo{{end}}'
+```
+
+Arithmetic:
+
+```yaml
+version: 3
+
+tasks:
+  foo:
+    vars:
+      INT: 10
+      FLOAT: 3.14159
+    cmds:
+      - 'echo {{add .INT .FLOAT}}'
+```
+
+Ranging:
+
+```yaml
+version: 3
+
+tasks:
+  foo:
+    vars:
+      ARRAY: [1, 2, 3]
+    cmds:
+      - 'echo {{range .ARRAY}}{{.}}{{end}}'
+```
+
+There are many more templating functions which can be used with the new types of
+variables. For a full list, see the
+[slim-sprig][slim-sprig] documentation.
+
+## Looping over variables
+
+Previously, you would have to use a delimiter separated string to loop over an
+arbitrary list of items in a variable and split them by using the `split` subkey
+to specify the delimiter:
+
+```yaml
+version: 3
+
+tasks:
+  foo:
+    vars:
+      LIST: 'foo,bar,baz'
+    cmds:
+      - for:
+          var: LIST
+          split: ','
+        cmd: echo {{.ITEM}}
+```
+
+Because this experiment adds support for array variables, the `for` keyword has
+been updated to support looping over arrays directly:
+
+```yaml
+version: 3
+
+tasks:
+  foo:
+    vars:
+      LIST: [foo, bar, baz]
+    cmds:
+      - for:
+          var: LIST
+        cmd: echo {{.ITEM}}
+```
+
+String splitting is still supported and remember that for simple cases, you have
+always been able to loop over an array without using variables at all:
+
+```yaml
+version: 3
+
+tasks:
+  foo:
+    cmds:
+      - for: [foo, bar, baz]
+        cmd: echo {{.ITEM}}
+```
+
+## Migration
+
+Taskfiles with dynamically defined variables via the `sh` subkey will no longer
+work with this experiment enabled. In order to keep using dynamically defined
+variables, you will need to migrate your Taskfile to use the new syntax.
+
+Previously, you might have defined a dynamic variable like this:
+
+```yaml
+version: 3
+
+task:
+  foo:
+    vars:
+      CALCULATED_VAR:
+        sh: 'echo hello'
+    cmds:
+      - 'echo {{.CALCULATED_VAR}}'
+```
+
+With this experiment enabled, you will need to remove the `sh` subkey and define
+your command as a string that begins with a `$`. This will instruct Task to
+interpret the string as a command instead of a literal value and the variable
+will be populated with the output of the command. For example:
+
+```yaml
+version: 3
+
+task:
+  foo:
+    vars:
+      CALCULATED_VAR: '$echo hello'
+    cmds:
+      - 'echo {{.CALCULATED_VAR}}'
+```
+
+If your current Taskfile contains a string variable that begins with a `$`, you
+will now need to escape the `$` with a backslash (`\`) to stop Task from
+executing it as a command.
+
+<!-- prettier-ignore-start -->
+
+[slim-sprig]: https://go-task.github.io/slim-sprig/
+
+<!-- prettier-ignore-end -->

docs/i18n/fr-FR/docusaurus-plugin-content-docs/current/experiments/experiments.md

@@ -1,26 +1,29 @@
 ---
 slug: /experiments/
-sidebar_position: 5
+sidebar_position: 6
 ---
 
-# Experiments
+# Expérimentations
 
 :::caution
 
-All experimental features are subject to breaking changes and/or removal _at any time_. We strongly recommend that you do not use these features in a production environment. They are intended for testing and feedback only.
+Toutes les fonctionnalités expérimentales sont sujettes à des changements brisant la fonctionnalité et/ou à la suppression de cette dernière _à tout moment _. Nous vous recommandons fortement de ne pas utiliser ces fonctionnalités dans en production. Ils sont seulement destinés à être testés et obtenir des retours dessus.
 
 :::
 
-In order to allow Task to evolve quickly, we roll out breaking changes to minor versions behind experimental flags. This allows us to gather feedback on breaking changes before committing to a major release. This document describes the current set of experimental features and the deprecated feature that they are intended to replace.
+Afin de permettre à Task d'évoluer rapidement, nous déployons des changements cassants sur des versions mineures activables par des options expérimentales. Cela nous permet d'obtenir des retours sur des changements brisants des fonctionnalités avant de les livrer dans une version majeure. Ce document décrit l'ensemble actuel de fonctionnalités expérimentales et leur statut dans le [workflow](#workflow).
 
-You can enable an experimental feature by:
+Vous pouvez consulter une liste complète des expérimentations en cours dans la section "Expérimentations" de la barre latérale .
 
-1. Using the relevant environment variable in front of a task command. For example, `TASK_X_{FEATURE}=1 task {my-task}`. This is intended for one-off invocations of Task to test out experimental features.
-1. Using the relevant environment variable in your "dotfiles" (e.g. `.bashrc`, `.zshrc` etc.). This is intended for permanently enabling experimental features in your environment.
-1. Creating a `.env` file in the same directory as your root Taskfile that contains the relevant environment variables. e.g.
+## Enabling Experiments
 
-```shell
-# .env
+You can enable an experimental feature by doing one of the following:
+
+1. Utiliser la variable d'environnement pertinente devant une commande Task. Par exemple, `TASK_X_{FEATURE}=1 task {my-task}`. Ceci est prévu pour faire appel à une expérimentation durant une seule commande Task afin de tester une fonctionnalité expérimentale.
+1. Utiliser la variable d'environnement pertinente dans vos "dotfiles" (par exemple `.bashrc`, `.zshrc` etc.). Ceci est destiné à l'activation permanente des fonctionnalités expérimentales dans votre environnement.
+1. Création d'un fichier `.env` dans le même répertoire que votre fichier Taskfile contenant les variables d'environnement pertinentes pour vos tests. This allows you to enable an experimental feature at a project level. For example:
+
+```shell title=".env"
 TASK_X_FEATURE=1
 ```
 
@@ -28,43 +31,49 @@ TASK_X_FEATURE=1
 
 Each section below details an experiment or deprecation and explains what the flags/environment variables to enable the experiment are and how the feature's behavior will change. It will also explain what you need to do to migrate any existing Taskfiles to the new behavior.
 
-<!-- EXPERIMENT TEMPLATE - Include sections as necessary...
+## Workflow
 
-### ![experiment] {Feature} ([#{issue}](https://github.com/go-task/task/issues/{issue})), ...)
+Experiments are a way for us to test out new features in Task before committing to them in a major release. Because this concept is built around the idea of feedback from our community, we have built a workflow for the process of introducing these changes. This ensures that experiments are given the attention and time that they need and that we are getting the best possible results out of them.
 
-- Environment variable: `TASK_X_{feature}`
-- Deprecates: {list any existing functionality that will be deprecated by this experiment}
-- Breaks: {list any existing functionality that will be broken by this experiment}
+The sections below describe the various stages that an experiment must go through from its proposal all the way to being released in a major version of Task.
 
-{Short description of the feature}
+### 1. Proposal
 
-{Short explanation of how users should migrate to the new behavior}
+All experimental features start with a proposal in the form of a GitHub issue. If the maintainers decide that an issue has enough support and is a breaking change or is complex/controversial enough to require user feedback, then the issue will be marked with the ![proposal][] label. At this point, the issue becomes a proposal and a period of consultation begins. During this period, we request that users provide feedback on the proposal and how it might effect their use of Task. It is up to the discretion of the maintainers to decide how long this period lasts.
 
--->
+### 2. Draft
 
-### ![deprecated][] Version 2 Schema ([#1197][deprecate-version-2-schema])
+Once a proposal's consultation ends, a contributor may pick up the work and begin the initial implementation. Once a PR is opened, the maintainers will ensure that it meets the requirements for an experimental feature (i.e. flags are in the right format etc) and merge the feature. Once this code is released, the status will be updated via the ![draft][] label. This indicates that an implementation is now available for use in a release and the experiment is open for feedback.
 
-The Taskfile v2 schema was introduced in March 2018 and replaced by version 3 in August the following year. Users have had a long time to update and so we feel that it is time to tidy up the codebase and focus on new functionality instead.
+:::note
 
-This notice does not mean that we are immediately removing support for version 2 schemas. However, support will not be extended to future major releases and we _strongly recommend_ that anybody still using a version 2 schema upgrades to version 3 as soon as possible.
+During the draft period, major changes to the implementation may be made based on the feedback received from users. There are _no stability guarantees_ and experimental features may be abandoned _at any time_.
 
-A list of changes between version 2 and version 3 are available in the [Task v3 Release Notes][version-3-release-notes].
+:::
 
-### ![experiment][] Gentle Force ([#1200](https://github.com/go-task/task/issues/1200))
+### 3. Candidate
 
-- Environment variable: `TASK_X_FORCE=1`
-- Breaks: `--force` flag
+Once an acceptable level of consensus has been reached by the community and feedback/changes are less frequent/significant, the status may be updated via the ![candidate][] label. This indicates that a proposal is _likely_ to accepted and will enter a period for final comments and minor changes.
 
-The `--force` flag currently forces _all_ tasks to run regardless of the status checks. This can be useful, but we have found that most of the time users only expect the direct task they are calling to be forced and _not_ all of its dependant tasks.
+### 4. Stable
 
-This experiment changes the `--force` flag to only force the directly called task. All dependant tasks will have their statuses checked as normal and will only run if Task considers them to be out of date. A new `--force-all` flag will also be added to maintain the current behavior for users that need this functionality.
+Once a suitable amount of time has passed with no changes or feedback, an experiment will be given the ![stable][] label. At this point, the functionality will be treated like any other feature in Task and any changes _must_ be backward compatible. This allows users to migrate to the new functionality without having to worry about anything breaking in future releases. This provides the best experience for users migrating to a new major version.
 
-If you want to migrate, but continue to force all dependant tasks to run, you should replace all uses of the `--force` flag with `--force-all`. Alternatively, if you want to adopt the new behavior, you can continue to use the `--force` flag as you do now!
+### 5. Released
+
+When making a new major release of Task, all experiments marked as ![stable][] will move to ![released][] and their behaviors will become the new default in Task. Experiments in an earlier stage (i.e. not stable) cannot be released and so will continue to be experiments in the new version.
+
+### Abandoned / Superseded
+
+If an experiment is unsuccessful at any point then it will be given the ![abandoned][] or ![superseded][] labels depending on which is more suitable. These experiments will be removed from Task.
 
 <!-- prettier-ignore-start -->
 
 <!-- prettier-ignore-end -->
-[deprecate-version-2-schema]: https://github.com/go-task/task/issues/1197
-[version-3-release-notes]: https://github.com/go-task/task/releases/tag/v3.0.0
-[deprecated]: https://img.shields.io/badge/deprecated-red
-[experiment]: https://img.shields.io/badge/experiment-yellow
+[proposal]: https://img.shields.io/badge/experiment:%20proposal-purple
+[draft]: https://img.shields.io/badge/experiment:%20draft-purple
+[candidate]: https://img.shields.io/badge/experiment:%20candidate-purple
+[stable]: https://img.shields.io/badge/experiment:%20stable-purple
+[released]: https://img.shields.io/badge/experiment:%20released-purple
+[abandoned]: https://img.shields.io/badge/experiment:%20abandoned-purple
+[superseded]: https://img.shields.io/badge/experiment:%20superseded-purple

docs/i18n/fr-FR/docusaurus-plugin-content-docs/current/experiments/gentle_force.md

@@ -0,0 +1,36 @@
+---
+slug: /experiments/gentle-force/
+---
+
+# Gentle Force (#1200)
+
+:::caution
+
+All experimental features are subject to breaking changes and/or removal _at any time_. We strongly recommend that you do not use these features in a production environment. They are intended for testing and feedback only.
+
+:::
+
+:::warning
+
+This experiment breaks the following functionality:
+
+- The `--force` flag
+
+:::
+
+:::info
+
+To enable this experiment, set the environment variable: `TASK_X_FORCE=1`. Check out [our guide to enabling experiments ][enabling-experiments] for more information.
+
+:::
+
+The `--force` flag currently forces _all_ tasks to run regardless of the status checks. This can be useful, but we have found that most of the time users only expect the direct task they are calling to be forced and _not_ all of its dependant tasks.
+
+This experiment changes the `--force` flag to only force the directly called task. All dependant tasks will have their statuses checked as normal and will only run if Task considers them to be out of date. A new `--force-all` flag will also be added to maintain the current behavior for users that need this functionality.
+
+If you want to migrate, but continue to force all dependant tasks to run, you should replace all uses of the `--force` flag with `--force-all`. Alternatively, if you want to adopt the new behavior, you can continue to use the `--force` flag as you do now!
+
+<!-- prettier-ignore-start -->
+
+<!-- prettier-ignore-end -->
+[enabling-experiments]: /experiments/#enabling-experiments

docs/i18n/fr-FR/docusaurus-plugin-content-docs/current/experiments/remote_taskfiles.md

@@ -0,0 +1,66 @@
+---
+slug: /experiments/remote-taskfiles/
+---
+
+# Remote Taskfiles (#1317)
+
+:::caution
+
+All experimental features are subject to breaking changes and/or removal _at any time_. We strongly recommend that you do not use these features in a production environment. They are intended for testing and feedback only.
+
+:::
+
+:::info
+
+To enable this experiment, set the environment variable: `TASK_X_REMOTE_TASKFILES=1`. Check out [our guide to enabling experiments ][enabling-experiments] for more information.
+
+:::
+
+This experiment allows you to specify a remote Taskfile URL when including a Taskfile. For example:
+
+```yaml
+version: '3'
+
+includes:
+  my-remote-namespace: https://raw.githubusercontent.com/my-org/my-repo/main/Taskfile.yml
+```
+
+This works exactly the same way that including a local file does. Any tasks in the remote Taskfile will be available to run from your main Taskfile via the namespace `my-remote-namespace`. For example, if the remote file contains the following:
+
+```yaml
+version: '3'
+
+tasks:
+  hello:
+    silent: true
+    cmds:
+      - echo "Hello from the remote Taskfile!"
+```
+
+and you run `task my-remote-namespace:hello`, it will print the text: "Hello from the remote Taskfile!" to your console.
+
+## Security
+
+Running commands from sources that you do not control is always a potential security risk. For this reason, we have added some checks when using remote Taskfiles:
+
+1. When running a task from a remote Taskfile for the first time, Task will print a warning to the console asking you to check that you are sure that you trust the source of the Taskfile. If you do not accept the prompt, then Task will exit with code `104` (not trusted) and nothing will run. If you accept the prompt, the remote Taskfile will run and further calls to the remote Taskfile will not prompt you again.
+2. Whenever you run a remote Taskfile, Task will create and store a checksum of the file that you are running. If the checksum changes, then Task will print another warning to the console to inform you that the contents of the remote file has changed. If you do not accept the prompt, then Task will exit with code `104` (not trusted) and nothing will run. If you accept the prompt, the checksum will be updated and the remote Taskfile will run.
+
+Sometimes you need to run Task in an environment that does not have an interactive terminal, so you are not able to accept a prompt. In these cases you are able to tell task to accept these prompts automatically by using the `--yes` flag. Before enabling this flag, you should:
+
+1. Be sure that you trust the source and contents of the remote Taskfile.
+2. Consider using a pinned version of the remote Taskfile (e.g. A link containing a commit hash) to prevent Task from automatically accepting a prompt that says a remote Taskfile has changed.
+
+Task currently supports both `http` and `https` URLs. However, the `http` requests will not execute by default unless you run the task with the `--insecure` flag. This is to protect you from accidentally running a remote Taskfile that is hosted on and unencrypted connection. Sources that are not protected by TLS are vulnerable to [man-in-the-middle attacks][man-in-the-middle-attacks] and should be avoided unless you know what you are doing.
+
+## Caching & Running Offline
+
+Whenever you run a remote Taskfile, the latest copy will be downloaded from the internet and cached locally. If for whatever reason, you lose access to the internet, you will still be able to run your tasks by specifying the `--offline` flag. This will tell Task to use the latest cached version of the file instead of trying to download it. You are able to use the `--download` flag to update the cached version of the remote files without running any tasks.
+
+By default, Task will timeout requests to download remote files after 10 seconds and look for a cached copy instead. This timeout can be configured by setting the `--timeout` flag and specifying a duration. For example, `--timeout 5s` will set the timeout to 5 seconds.
+
+<!-- prettier-ignore-start -->
+
+<!-- prettier-ignore-end -->
+[enabling-experiments]: /experiments/#enabling-experiments
+[man-in-the-middle-attacks]: https://en.wikipedia.org/wiki/Man-in-the-middle_attack

docs/i18n/fr-FR/docusaurus-plugin-content-docs/current/experiments/template.md

@@ -0,0 +1,39 @@
+---
+#This is a template for an experiments documentation
+#Copy this page and fill in the details as necessary
+title: '--- Template ---'
+sidebar_position: -1 #Always push to the top
+draft: true #Hide in production
+---
+
+# \{Name of Experiment\} (#\{Issue\})
+
+:::caution
+
+All experimental features are subject to breaking changes and/or removal _at any time_. We strongly recommend that you do not use these features in a production environment. They are intended for testing and feedback only.
+
+:::
+
+:::warning
+
+This experiment breaks the following functionality:
+
+- \{list any existing functionality that will be broken by this experiment\}
+- \{if there are no breaking changes, remove this admonition\}
+
+:::
+
+:::info
+
+To enable this experiment, set the environment variable: `TASK_X_{feature}=1`. Check out [our guide to enabling experiments ][enabling-experiments] for more information.
+
+:::
+
+\{Short description of the feature\}
+
+\{Short explanation of how users should migrate to the new behavior\}
+
+<!-- prettier-ignore-start -->
+
+<!-- prettier-ignore-end -->
+[enabling-experiments]: /experiments/#enabling-experiments

docs/i18n/fr-FR/docusaurus-plugin-content-docs/current/faq.md

@@ -1,6 +1,6 @@
 ---
 slug: /faq/
-sidebar_position: 7
+sidebar_position: 15
 ---
 
 # FAQ
@@ -78,7 +78,7 @@ The default shell on Windows (`cmd` and `powershell`) do not have commands like
 
 We want to make improvements to this part of Task and the issues below track this work. Constructive comments and contributions are very welcome!
 
-- [#197](https://github.com/go-task/task/issues/197)
+- #197
 - [mvdan/sh#93](https://github.com/mvdan/sh/issues/93)
 - [mvdan/sh#97](https://github.com/mvdan/sh/issues/97)
 

docs/i18n/fr-FR/docusaurus-plugin-content-docs/current/installation.md

@@ -17,7 +17,7 @@ If you're on macOS or Linux and have [Homebrew][homebrew] installed, getting Tas
 brew install go-task/tap/go-task
 ```
 
-The above Formula is [maintained by ourselves](https://github.com/go-task/homebrew-tap/blob/master/Formula/go-task.rb).
+The above Formula is [maintained by ourselves](https://github.com/go-task/homebrew-tap/blob/main/Formula/go-task.rb).
 
 Recently, Task was also made available [on the official Homebrew repository](https://formulae.brew.sh/formula/go-task), so you also have that option if you prefer:
 

docs/i18n/fr-FR/docusaurus-plugin-content-docs/current/integrations.md

@@ -1,6 +1,6 @@
 ---
 slug: /integrations/
-sidebar_position: 6
+sidebar_position: 8
 ---
 
 # Integrations
@@ -24,7 +24,7 @@ To get autocompletion and validation for your Taskfile, see the [Schema](#schema
 
 ## Schema
 
-This was initially created by [@KROSF](https://github.com/KROSF) in [this Gist](https://gist.github.com/KROSF/c5435acf590acd632f71bb720f685895) and is now officially maintained in [this file](https://github.com/go-task/task/blob/main/docs/static/schema.json) and made available at https://taskfile.dev/schema.json. This schema can be used to validate Taskfiles and provide autocompletion in many code editors:
+This was initially created by @KROSF in [this Gist](https://gist.github.com/KROSF/c5435acf590acd632f71bb720f685895) and is now officially maintained in [this file](https://github.com/go-task/task/blob/main/docs/static/schema.json) and made available at https://taskfile.dev/schema.json. This schema can be used to validate Taskfiles and provide autocompletion in many code editors:
 
 ### Visual Studio Code
 
@@ -55,8 +55,8 @@ You can find more information on this in the [YAML language server project](http
 
 In addition to our official integrations, there is an amazing community of developers who have created their own integrations for Task:
 
-- [Sublime Text Plugin](https://packagecontrol.io/packages/Taskfile) [[source](https://github.com/biozz/sublime-taskfile)] by [@biozz](https://github.com/biozz)
-- [IntelliJ Plugin](https://plugins.jetbrains.com/plugin/17058-taskfile) [[source](https://github.com/lechuckroh/task-intellij-plugin)] by [@lechuckroh](https://github.com/lechuckroh)
+- [Sublime Text Plugin](https://packagecontrol.io/packages/Taskfile) [[source](https://github.com/biozz/sublime-taskfile)] by @biozz
+- [IntelliJ Plugin](https://plugins.jetbrains.com/plugin/17058-taskfile) [[source](https://github.com/lechuckroh/task-intellij-plugin)] by @lechuckroh
 - [mk](https://github.com/pycontribs/mk) command line tool recognizes Taskfiles natively.
 
 If you have made something that integrates with Task, please feel free to open a PR to add it to this list.

docs/i18n/fr-FR/docusaurus-plugin-content-docs/current/intro.md

@@ -14,7 +14,7 @@ Task est un exécuteur de tâches / de build qui vise à être plus simple et fa
 
 Comme il est écrit en [Go][go], Task n'est qu'un binaire unique et n'a aucune dépendance. Cela signifie que vous n'avez pas besoin d'une installation compliquée simplement pour utiliser un outil de build.
 
-Une fois [installé](installation.md), il vous suffit de décrire vos tâches de build en utilisant un simple schéma [YAML][yaml] dans un fichier appelé `Taskfile.yml`:
+Once [installed](/installation), you just need to describe your build tasks using a simple [YAML][yaml] schema in a file called `Taskfile.yml`:
 
 ```yaml title="Taskfile.yml"
 version: '3'
@@ -32,21 +32,11 @@ L'exemple ci-dessus n'est que le début, vous pouvez jeter un coup d'œil au [gu
 
 ## Fonctionnalités
 
-- [Installation facile](installation.md): il suffit de télécharger un seul binaire, ajoutez le à `$PATH` et vous avez terminé ! Ou vous pouvez également installer en utilisant [Homebrew][homebrew], [Snapcraft][snapcraft] ou [Scoop][scoop] si vous le souhaitez.
-- Disponible sur les CIs: en ajoutant [cette commande simple](installation.md#install-script) à installer sur votre script CI, vous êtes prêt à utiliser Task dans le cadre de votre pipeline CI ;
+- [Easy installation](/installation): just download a single binary, add to `$PATH` and you're done! Ou vous pouvez également installer en utilisant [Homebrew][homebrew], [Snapcraft][snapcraft] ou [Scoop][scoop] si vous le souhaitez.
+- Available on CIs: by adding [this simple command](/installation#install-script) to install on your CI script and you're ready to use Task as part of your CI pipeline;
 - Multi-plateforme : alors que la plupart des outils de compilation ne fonctionnent bien que sous Linux ou macOS, Task prend également en charge Windows grâce à [cet interpréteur shell pour Go][sh].
 - Idéal pour la génération de code : vous pouvez facilement [empêcher une tâche de s'exécuter](/usage#prevent-unnecessary-work) si un ensemble donné de fichiers n'ont pas changé depuis le dernier lancement (basé soit sur son horodatage soit son contenu).
 
-## Sponsors Or
-
-<div class="gold-sponsors">
-
-| [Appwrite](https://appwrite.io/?utm_source=taskfile.dev&utm_medium=website&utm_campaign=task_oss_fund)                       |
-| ---------------------------------------------------------------------------------------------------------------------------- |
-| [![Appwrite](/img/appwrite.svg)](https://appwrite.io/?utm_source=taskfile.dev&utm_medium=website&utm_campaign=task_oss_fund) |
-
-</div>
-
 <!-- prettier-ignore-start -->
 
 <!-- prettier-ignore-end -->

docs/i18n/fr-FR/docusaurus-plugin-content-docs/current/releasing.md

@@ -26,6 +26,10 @@ The [snap package][snappackage] requires to manual steps to release a new versio
 - Updating the current version on [snapcraft.yaml][snapcraftyaml].
 - Moving both `amd64`, `armhf` and `arm64` new artifacts to the stable channel on the [Snapcraft dashboard][snapcraftdashboard].
 
+# winget
+
+winget also requires manual steps to be completed. By running `task goreleaser:test` locally, manifest files will be generated on `dist/winget/manifests/t/Task/Task/v{version}`. [Upload the manifest directory into this fork](https://github.com/go-task/winget-pkgs/tree/master/manifests/t/Task/Task) and open a pull request into [this repository](https://github.com/microsoft/winget-pkgs).
+
 # Scoop
 
 Scoop is a command-line package manager for the Windows operating system. Scoop package manifests are maintained by the community. Scoop owners usually take care of updating versions there by editing [this file](https://github.com/ScoopInstaller/Main/blob/master/bucket/task.json). If you think its Task version is outdated, open an issue to let us know.
@@ -39,8 +43,8 @@ Nix is a community owned installation method. Nix package maintainers usually ta
 <!-- prettier-ignore-end -->
 [goreleaser]: https://goreleaser.com/
 [homebrewtap]: https://github.com/go-task/homebrew-tap
-[gotaskrb]: https://github.com/go-task/homebrew-tap/blob/master/Formula/go-task.rb
+[gotaskrb]: https://github.com/go-task/homebrew-tap/blob/main/Formula/go-task.rb
 [packagejson]: https://github.com/go-task/task/blob/main/package.json#L3
 [snappackage]: https://github.com/go-task/snap
-[snapcraftyaml]: https://github.com/go-task/snap/blob/master/snap/snapcraft.yaml#L2
+[snapcraftyaml]: https://github.com/go-task/snap/blob/main/snap/snapcraft.yaml#L2
 [snapcraftdashboard]: https://snapcraft.io/task/releases

docs/i18n/fr-FR/docusaurus-plugin-content-docs/current/styleguide.md

@@ -1,6 +1,6 @@
 ---
 slug: /styleguide/
-sidebar_position: 8
+sidebar_position: 10
 ---
 
 # Guide de style
@@ -9,19 +9,6 @@ Ceci est le guide officiel du style Task pour les fichiers `Taskfile.yml`. Ce gu
 
 Il contient des directives générales, mais elles ne doivent pas nécessairement être strictement respectées. N'hésitez pas à procéder différemment si vous en avez le besoin ou que vous le souhaitez. Aussi, n'hésitez pas à [ouvrir une issue](https://github. com/go-task/task/issues/new/choose) ou [faire une pull request](https://github. com/go-task/task/compare) pour améliorer ce guide.
 
-## Utiliser `Taskfile.yml` et non `taskfile.yml`
-
-```yaml
-# bad
-taskfile.yml
-
-
-# good
-Taskfile.yml
-```
-
-C'est important, surtout pour les utilisateurs Linux. Windows et MacOS ont un système de fichiers insensibles à la casse, donc `taskfile.yml` fonctionnera, même si ce n'est pas officiellement supporté. Sur Linux, uniquement `Taskfile.yml` fonctionnera.
-
 ## Utiliser les mots-clés dans l'ordre correct
 
 - `version:`
@@ -208,10 +195,10 @@ tasks:
 
 C'est aussi fait automatiquement quand vous incluez des Taskfiles.
 
-## Prefer external scripts over complex multi-line commands
+## Préférer les scripts externes à des commandes complexes à plusieurs lignes
 
 ```yaml
-# bad
+# Incorrect
 version: '3'
 
 tasks:
@@ -223,7 +210,7 @@ tasks:
           echo "some other complex logic"
         done'
 
-# good
+# Correct
 version: '3'
 
 tasks:

docs/i18n/fr-FR/docusaurus-plugin-content-docs/current/taskfile_versions.md

@@ -1,30 +1,30 @@
 ---
 slug: /taskfile-versions/
-sidebar_position: 14
+sidebar_position: 5
 ---
 
-# Taskfile Versions
+# Versions Taskfile
 
-The Taskfile syntax and features changed with time. This document explains what changed on each version and how to upgrade your Taskfile.
+La syntaxe et les fonctionnalités du fichier Taskfile changent avec le temps. Ce document explique quels sont les changments pour chacune des versions et comment vous pouvez mettre à jour votre Taskfile.
 
-## What the Taskfile version mean
+## Qu'est-ce que la version de Taskfile signifie
 
-The Taskfile version follows the Task version. E.g. the change to Taskfile version `2` means that Task `v2.0.0` should be release to support it.
+La version de Taskfile suit la version de Task. Par exemple : Le changement pour la version `2` dans Taskfile signifie que la version `v2.0.0` de Task doit être publiée pour pouvoir le supporter.
 
-The `version:` key on Taskfile accepts a semver string, so either `2`, `2.0` or `2.0.0` is accepted. If you choose to use `2.0` Task will not enable future `2.1` features, but if you choose to use `2`, then any `2.x.x` features will be available, but not `3.0.0+`.
+Le paramètrre `version:` dans Taskfile accepte une version suivant la nomenclature semver. Donc `2`, `2.0` et `2.0.0` sont acceptés. Si vous choisissez d'utiliser la version `2.0`, Task ne va pas activer les fonctionnalités des versions `2.1` et celles d'après. Mais si vous choississez d'utiliser la version `2`, alors toutes les fonctionnalités des versions `2.x.x` seront disponibles, et non celles des versions `3.0.0` et celles d'après.
 
-## Version 3 ![latest](https://img.shields.io/badge/latest-brightgreen)
+## Version 3 ![Dernier](https://img.shields.io/badge/latest-brightgreen)
 
-These are some major changes done on `v3`:
+Voici quelques modifications majeures effectuées sur `v3`:
 
-- Task's output will now be colored
-- Added support for `.env` like files
-- Added `label:` setting to task so one can override how the task name appear in the logs
-- A global `method:` was added to allow setting the default method, and Task's default changed to `checksum`
-- Two magic variables were added when using `status:`: `CHECKSUM` and `TIMESTAMP` which contains, respectively, the md5 checksum and greatest modification timestamp of the files listed on `sources:`
-- Also, the `TASK` variable is always available with the current task name
-- CLI variables are always treated as global variables
-- Added `dir:` option to `includes` to allow choosing on which directory an included Taskfile will run:
+- Les logs de Task dans le terminal sont colorés
+- Ajout du support des fichiers `.env` et similaires
+- Ajout du paramètre `label:` dans les tâches pour que l'on puisse renommer la tâche dans les logs
+- Le paramètre global `method:` a été ajouté pour permettre de définir la méthode par défault, et la valeur par défaut de Task a été changée pour `checksum`
+- Deux variables magiques ont été ajoutées lors de l'utilisation de `status:`: `CHECKSUM` et `TIMESTAMP` qui contiennent respectivement le checksum XXH3 et le plus récent timestamp de modification des fichiers répertoriés dans `sources:`
+- Aussi, la variable `TASK` est toujours disponible avec le nom de la tâche courante
+- Les variables CLI sont toujours traitées comme des variables globales
+- Ajout de l'option `dir:` dans `includes` pour permettre de choisir dans quel dossier un Taskfile doit être exécuté :
 
 ```yaml
 includes:
@@ -33,7 +33,7 @@ includes:
     dir: ./docs
 ```
 
-- Implemented short task syntax. All below syntaxes are equivalent:
+- Implémentation de syntaxes courtes. Toutes les syntaxes ci-dessous sont équivalentes:
 
 ```yaml
 version: '3'
@@ -59,21 +59,21 @@ tasks:
   print: echo "Hello, World!"
 ```
 
-- There was a major refactor on how variables are handled. They're now easier to understand. The `expansions:` setting was removed as it became unnecessary. This is the order in which Task will process variables, each level can see the variables set by the previous one and override those.
-  - Environment variables
-  - Global + CLI variables
-  - Call variables
-  - Task variables
+- Il y a eu une réécriture majeure sur la manière dont les variables sont gérées. C'est maintenant plus simple à comprendre. Les paramètres `expansions:` ont été retirées vu qu'ils n'étaient plus nécessaires. C'est l'ordre dans lequel Task va traiter les variables, chaque niveau peut voir les variables définies par la précédente et les remplacer.
+  - Variables d'environnement
+  - Variables globales + CLI
+  - Variables d'appel
+  - Variables Task
 
 ## Version 2.6
 
 :::caution
 
-v2 schema support is [deprecated][deprecate-version-2-schema] and will be removed in a future release.
+v2 schemas are [no longer supported by the latest version of Task][deprecate-version-2-schema].
 
 :::
 
-Version 2.6 comes with `preconditions` stanza in tasks.
+La version 2.6 vient avec des `preconditions` dans les tâches.
 
 ```yaml
 version: '2'
@@ -92,11 +92,11 @@ Please check the [documentation][includes]
 
 :::caution
 
-v2 schema support is [deprecated][deprecate-version-2-schema] and will be removed in a future release.
+v2 schemas are [no longer supported by the latest version of Task][deprecate-version-2-schema].
 
 :::
 
-Version 2.2 comes with a global `includes` options to include other Taskfiles:
+La version 2.2 est fournie avec une option globale `includes` pour inclure d'autres Taskfiles :
 
 ```yaml
 version: '2'
@@ -110,7 +110,7 @@ includes:
 
 :::caution
 
-v2 schema support is [deprecated][deprecate-version-2-schema] and will be removed in a future release.
+v2 schemas are [no longer supported by the latest version of Task][deprecate-version-2-schema].
 
 :::
 
@@ -151,11 +151,11 @@ tasks:
 
 :::caution
 
-v2 schema support is [deprecated][deprecate-version-2-schema] and will be removed in a future release.
+v2 schemas are [no longer supported by the latest version of Task][deprecate-version-2-schema].
 
 :::
 
-At version 2, we introduced the `version:` key, to allow us to evolve Task with new features without breaking existing Taskfiles. The new syntax is as follows:
+À la version 2, nous avons introduit le paramètre `version:` pour nous permettre d'évoluer vers de nouvelles fonctionnalités avec sans casser les fichiers de tâches existants. La nouvelle syntaxe est la suivante:
 
 ```yaml
 version: '2'
@@ -166,7 +166,7 @@ tasks:
       - echo "Hello, World!"
 ```
 
-Version 2 allows you to write global variables directly in the Taskfile, if you don't want to create a `Taskvars.yml`:
+La version 2 vous permet d'écrire des variables globales directement dans le fichier Taskfile, si vous ne voulez pas créer un fichier `Taskvars.yml`:
 
 ```yaml
 version: '2'
@@ -180,15 +180,15 @@ tasks:
       - echo "{{.GREETING}}"
 ```
 
-The variable priority order changed to the following:
+A présent, l'ordre de priorité des variables est :
 
-1. Task variables
-2. Call variables
-3. Taskfile variables
-4. Taskvars file variables
-5. Environment variables
+1. Variables Task
+2. Variables d'appel
+3. Variables Taskfile
+4. Variables du fichier Taskvars
+5. Variables d'environnement
 
-A new global option was added to configure the number of variables expansions (which default to 2):
+Une nouvelle option globale a été ajoutée pour configurer le nombre d'extensions de variables (par défaut 2):
 
 ```yaml
 version: '2'
@@ -212,11 +212,11 @@ tasks:
 
 :::caution
 
-v1 schema support was removed in Task >= v3.0.0.
+Le support du schéma v1 a été supprimé de Task >= v3.0.0.
 
 :::
 
-In the first version of the `Taskfile`, the `version:` key was not available, because the tasks was in the root of the YAML document. Like this:
+Dans la première version du `Taskfile`, le champ `version:` n'était pas disponible, parce que les tâches étaient à la racine du document YAML. Comme ceci:
 
 ```yaml
 echo:
@@ -224,17 +224,17 @@ echo:
     - echo "Hello, World!"
 ```
 
-The variable priority order was also different:
+L'ordre de priorité de la variable était également différent :
 
-1. Call variables
-2. Environment
-3. Task variables
-4. `Taskvars.yml` variables
+1. Variables d'appel
+2. Variables d'environnement
+3. Variables Task
+4. Variables `Taskvars.yml`
 
 <!-- prettier-ignore-start -->
 
 <!-- prettier-ignore-end -->
-[output]: usage.md#output-syntax
-[ignore_errors]: usage.md#ignore-errors
-[includes]: usage.md#including-other-taskfiles
-[deprecate-version-2-schema]: https://github.com/go-task/task/issues/1197
+[deprecate-version-2-schema]: /deprecations/version-2-schema/
+[output]: /usage#output-syntax
+[ignore_errors]: /usage#ignore-errors
+[includes]: /usage#including-other-taskfiles

docs/i18n/fr-FR/docusaurus-plugin-content-docs/current/usage.md

@@ -567,9 +567,23 @@ tasks:
       - public/bundle.css
 ```
 
-`sources` and `generates` can be files or file patterns. When given, Task will compare the checksum of the source files to determine if it's necessary to run the task. If not, it will just print a message like `Task "js" is up to date`.
+`sources` and `generates` can be files or glob patterns. When given, Task will compare the checksum of the source files to determine if it's necessary to run the task. If not, it will just print a message like `Task "js" is up to date`.
 
-If you prefer this check to be made by the modification timestamp of the files, instead of its checksum (content), just set the `method` property to `timestamp`.
+`exclude:` can also be used to exclude files from fingerprinting. Sources are evaluated in order, so `exclude:` must come after the positive glob it is negating.
+
+```yaml
+version: '3'
+
+tasks:
+  css:
+    sources:
+      - mysources/**/*.css
+      - exclude: mysources/ignoreme.css
+    generates:
+      - public/bundle.css
+```
+
+If you prefer these check to be made by the modification timestamp of the files, instead of its checksum (content), just set the `method` property to `timestamp`.
 
 ```yaml
 version: '3'
@@ -764,7 +778,7 @@ Environmental variables are also checked.
 Syntax:
 
 ```yaml
-requires: 
+requires:
   vars: [] # Array of strings
 ```
 
@@ -785,7 +799,7 @@ tasks:
       - 'docker build . -t {{.IMAGE_NAME}}:{{.IMAGE_TAG}}'
 
     # Make sure these variables are set before running
-    requires: 
+    requires:
       vars: [IMAGE_NAME, IMAGE_TAG]
 ```
 
@@ -863,6 +877,162 @@ tasks:
 
 This works for all types of variables.
 
+## Looping over values
+
+As of v3.28.0, Task allows you to loop over certain values and execute a command for each. There are a number of ways to do this depending on the type of value you want to loop over.
+
+### Looping over a static list
+
+The simplest kind of loop is an explicit one. This is useful when you want to loop over a set of values that are known ahead of time.
+
+```yaml
+version: '3'
+
+tasks:
+  default:
+    cmds:
+      - for: ['foo.txt', 'bar.txt']
+        cmd: cat {{ .ITEM }}
+```
+
+### Looping over your task's sources
+
+You are also able to loop over the sources of your task:
+
+```yaml
+version: '3'
+
+tasks:
+  default:
+    sources:
+      - foo.txt
+      - bar.txt
+    cmds:
+      - for: sources
+        cmd: cat {{ .ITEM }}
+```
+
+This will also work if you use globbing syntax in your sources. For example, if you specify a source for `*.txt`, the loop will iterate over all files that match that glob.
+
+Source paths will always be returned as paths relative to the task directory. If you need to convert this to an absolute path, you can use the built-in `joinPath` function. There are some [special variables](/api/#special-variables) that you may find useful for this.
+
+```yaml
+version: '3'
+
+tasks:
+  default:
+    vars:
+      MY_DIR: /path/to/dir
+    dir: '{{.MY_DIR}}'
+    sources:
+      - foo.txt
+      - bar.txt
+    cmds:
+      - for: sources
+        cmd: cat {{joinPath .MY_DIR .ITEM}}
+```
+
+### Looping over variables
+
+To loop over the contents of a variable, you simply need to specify the variable you want to loop over. By default, variables will be split on any whitespace characters.
+
+```yaml
+version: '3'
+
+tasks:
+  default:
+    vars:
+      MY_VAR: foo.txt bar.txt
+    cmds:
+      - for: { var: MY_VAR }
+        cmd: cat {{.ITEM}}
+```
+
+If you need to split on a different character, you can do this by specifying the `split` property:
+
+```yaml
+version: '3'
+
+tasks:
+  default:
+    vars:
+      MY_VAR: foo.txt,bar.txt
+    cmds:
+      - for: { var: MY_VAR, split: ',' }
+        cmd: cat {{.ITEM}}
+```
+
+All of this also works with dynamic variables!
+
+```yaml
+version: '3'
+
+tasks:
+  default:
+    vars:
+      MY_VAR:
+        sh: find -type f -name '*.txt'
+    cmds:
+      - for: { var: MY_VAR }
+        cmd: cat {{.ITEM}}
+```
+
+### Renaming variables
+
+If you want to rename the iterator variable to make it clearer what the value contains, you can do so by specifying the `as` property:
+
+```yaml
+version: '3'
+
+tasks:
+  default:
+    vars:
+      MY_VAR: foo.txt bar.txt
+    cmds:
+      - for: { var: MY_VAR, as: FILE }
+        cmd: cat {{.FILE}}
+```
+
+### Looping over tasks
+
+Because the `for` property is defined at the `cmds` level, you can also use it alongside the `task` keyword to run tasks multiple times with different variables.
+
+```yaml
+version: '3'
+
+tasks:
+  default:
+    cmds:
+      - for: [foo, bar]
+        task: my-task
+        vars:
+          FILE: '{{.ITEM}}'
+
+  my-task:
+    cmds:
+      - echo '{{.FILE}}'
+```
+
+Or if you want to run different tasks depending on the value of the loop:
+
+```yaml
+version: '3'
+
+tasks:
+  default:
+    cmds:
+      - for: [foo, bar]
+        task: task-{{.ITEM}}
+
+  task-foo:
+    cmds:
+      - echo 'foo'
+
+  task-bar:
+    cmds:
+      - echo 'bar'
+```
+
 ## Forwarding CLI arguments to commands
 
 If `--` is given in the CLI, all following parameters are added to a special `.CLI_ARGS` variable. This is useful to forward arguments to another command.
@@ -1128,7 +1298,7 @@ tasks:
 task: "This is a dangerous command... Do you want to continue?" [y/N]
 ```
 
-Warning prompts are called before executing a task. If a prompt is denied Task will exit with [exit code](api_reference.md#exit-codes) 205. If approved, Task will continue as normal.
+Warning prompts are called before executing a task. If a prompt is denied Task will exit with [exit code](/api#exit-codes) 205. If approved, Task will continue as normal.
 
 ```bash
 ❯ task example
@@ -1425,6 +1595,29 @@ With the flags `--watch` or `-w` task will watch for file changes and run the ta
 
 The default watch interval is 5 seconds, but it's possible to change it by either setting `interval: '500ms'` in the root of the Taskfile passing it as an argument like `--interval=500ms`.
 
+Also, it's possible to set `watch: true` in a given task and it'll automatically run in watch mode:
+
+```yaml
+version: '3'
+
+interval: 500ms
+
+tasks:
+  build:
+    desc: Builds the Go application
+    watch: true
+    sources:
+      - '**/*.go'
+    cmds:
+      - go build  # ...
+```
+
+:::info
+
+Note that when setting `watch: true` to a task, it'll only run in watch mode when running from the CLI via `task my-watch-task`, but won't run in watch mode if called by another task, either directly or as a dependency.
+
+:::
+
 <!-- prettier-ignore-start -->
 
 <!-- prettier-ignore-end -->

docs/i18n/ja-JP/code.json

@@ -1,54 +1,54 @@
 {
   "theme.ErrorPageContent.title": {
-    "message": "This page crashed.",
+    "message": "ページがクラッシュしました。",
     "description": "The title of the fallback page when the page crashed"
   },
   "theme.ErrorPageContent.tryAgain": {
-    "message": "Try again",
+    "message": "もう一度お試しください",
     "description": "The label of the button to try again when the page crashed"
   },
   "theme.NotFound.title": {
-    "message": "Page Not Found",
+    "message": "ページが見つかりませんでした",
     "description": "The title of the 404 page"
   },
   "theme.NotFound.p1": {
-    "message": "We could not find what you were looking for.",
+    "message": "お探しのページが見つかりませんでした。",
     "description": "The first paragraph of the 404 page"
   },
   "theme.NotFound.p2": {
-    "message": "Please contact the owner of the site that linked you to the original URL and let them know their link is broken.",
+    "message": "アクセスを試みたのURLをリンクしたサイトの管理者に連絡して、そのリンクが壊れていることを知らせてください。",
     "description": "The 2nd paragraph of the 404 page"
   },
   "theme.admonition.note": {
-    "message": "note",
+    "message": "メモ",
     "description": "The default label used for the Note admonition (:::note)"
   },
   "theme.admonition.tip": {
-    "message": "tip",
+    "message": "ヒント",
     "description": "The default label used for the Tip admonition (:::tip)"
   },
   "theme.admonition.danger": {
-    "message": "danger",
+    "message": "危険",
     "description": "The default label used for the Danger admonition (:::danger)"
   },
   "theme.admonition.info": {
-    "message": "info",
+    "message": "お知らせ",
     "description": "The default label used for the Info admonition (:::info)"
   },
   "theme.admonition.caution": {
-    "message": "caution",
+    "message": "注意",
     "description": "The default label used for the Caution admonition (:::caution)"
   },
   "theme.BackToTopButton.buttonAriaLabel": {
-    "message": "Scroll back to top",
+    "message": "ページ上部へ戻る",
     "description": "The ARIA label for the back to top button"
   },
   "theme.blog.archive.title": {
-    "message": "Archive",
+    "message": "アーカイブ",
     "description": "The page & hero title of the blog archive page"
   },
   "theme.blog.archive.description": {
-    "message": "Archive",
+    "message": "アーカイブ",
     "description": "The page & hero description of the blog archive page"
   },
   "theme.blog.paginator.navAriaLabel": {
@@ -195,7 +195,7 @@
     "description": "The ARIA label for copy code blocks button"
   },
   "theme.CodeBlock.copy": {
-    "message": "Copy",
+    "message": "コピー",
     "description": "The copy button label on code blocks"
   },
   "theme.CodeBlock.wordWrapToggle": {

docs/i18n/ja-JP/docusaurus-plugin-content-blog/2023-09-02-introducing-experiments.md

@@ -0,0 +1,93 @@
+---
+title: Introducing Experiments
+description: A look at where task is, where it's going and how we're going to get there.
+slug: task-in-2023
+authors:
+  - pd93
+tags:
+  - experiments
+  - breaking-changes
+  - roadmap
+  - v4
+image: https://i.imgur.com/mErPwqL.png
+hide_table_of_contents: false
+---
+
+Lately, Task has been growing extremely quickly and I've found myself thinking a lot about the future of the project and how we continue to evolve and grow. I'm not much of a writer, but I think one of the things we could do better is to communicate these kinds of thoughts to the community. So, with that in mind, this is the first (hopefully of many) blog posts talking about Task and what we're up to.
+
+<!--truncate-->
+
+## :calendar: So, what have we been up to?
+
+Over the past 12 months or so, [@andreynering][] (Author and maintainer of the project) and I ([@pd93][]) have been working in our spare time to maintain and improve v3 of Task and we've made some amazing progress. Here are just some of the things we've released in that time:
+
+- An official [extension for VS Code][vscode-task].
+- Internal Tasks ([#818](https://github.com/go-task/task/pull/818)).
+- Task aliases ([#879](https://github.com/go-task/task/pull/879)).
+- Looping over tasks ([#1220](https://github.com/go-task/task/pull/1200)).
+- A series of refactors to the core codebase to make it more maintainable and extensible.
+- Loads of bug fixes and improvements.
+- An integration with [Crowdin][crowdin]. Work is in progress on making our docs available in **7 new languages** (Special thanks to all our translators for the huge help with this!).
+- And much, much more! :sparkles:
+
+We're also working on adding some really exciting and highly requested features to Task such as having the ability to run remote Taskfiles ([#1317](https://github.com/go-task/task/issues/1317)).
+
+None of this would have been possible without the [150 or so (and growing) contributors][contributors] to the project, numerous sponsors and a passionate community of users. Together we have more than doubled the number of GitHub stars to over 8400 :star: since the beginning of 2022 and this continues to accelerate. We can't thank you all enough for your help and support! :rocket:
+
+[![Star History Chart](https://api.star-history.com/svg?repos=go-task/task&type=Date)](https://star-history.com/#go-task/task&Date)
+
+## What's next? :thinking:
+
+It's extremely motivating to see so many people using and loving Task. However, in this time we've also seen an increase in the number of issues and feature requests. In particular, issues that require some kind of breaking change to Task. This isn't a bad thing, but as we grow we need to be more responsible about how we address these changes in a way that ensures stability and compatibility for existing users and their Taskfiles.
+
+At this point you're probably thinking something like:
+
+> "But you use [semantic versioning][semver] - Just release a new major version with your breaking changes."
+
+And you'd be right... sort of. In theory, this sounds great, but the reality is that we don't have the time to commit to a major overhaul of Task in one big bang release. This would require a colossal amount of time and coordination and with full time jobs and personal lives to tend to, this is a difficult commitment to make. Smaller, more frequent major releases are also a significant inconvenience for users as they have to constantly keep up-to-date with our breaking changes. Fortunately, there is a better way.
+
+## What's going to change? :monocle:
+
+Going forwards, breaking changes will be allowed into _minor_ versions of Task as "experimental features". To access these features users will need opt-in by enabling feature flags. This will allow us to release new features slowly and gather feedback from the community before making them the default behavior in a future major release.
+
+To prepare users for the next major release, we will maintain a list of [deprecated features][deprecations] and [experiments][experiments] on our docs website and publish information on how to migrate to the new behavior.
+
+You can read the [full breaking change proposal][breaking-change-proposal] and view all the [current experiments and their status][experiments-project] on GitHub including the [Gentle Force][gentle-force-experiment] and [Remote Taskfiles][remote-taskfiles-experiment] experiments.
+
+## What will happen to v2/v3 features?
+
+v2 has been [officially deprecated][deprecate-version-2-schema]. If you're still using a Taskfile with `version: "2"` at the top we _strongly recommend_ that you upgrade as soon as possible. Removing v2 will allow us to tidy up the codebase and focus on new functionality instead.
+
+When v4 is released, we will continue to support v3 for a period of time (bug fixes etc). However, since we are moving from a backward-compatibility model to a forwards-compatibility model, **v4 itself will not be backwards compatible with v3**.
+
+## v4 When? :eyes:
+
+:man_shrugging: When it's ready.
+
+In all seriousness, we don't have a timeline for this yet. We'll be working on the most serious deficiencies of the v3 API first and regularly evaluating the state of the project. When we feel its in a good, stable place and we have a clear upgrade path for users and a number of stable experiments, we'll start to think about v4.
+
+## :wave: Final thoughts
+
+Task is growing fast and we're excited to see where it goes next. We hope that the steps we're taking to improve the project and our process will help us to continue to grow. As always, if you have any questions or feedback, we encourage you to comment on or open [issues][issues] and [discussions][discussions] on GitHub. Alternatively, you can join us on [Discord][discord].
+
+I plan to write more of these blog posts in the future on a variety of Task-related topics, so make sure to check in occasionally and see what we're up to!
+
+<!-- prettier-ignore-start -->
+
+<!-- prettier-ignore-end -->
+[vscode-task]: https://github.com/go-task/vscode-task
+[crowdin]: https://crowdin.com
+[contributors]: https://github.com/go-task/task/graphs/contributors
+[semver]: https://semver.org
+[breaking-change-proposal]: https://github.com/go-task/task/discussions/1191
+[@andreynering]: https://github.com/andreynering
+[@pd93]: https://github.com/pd93
+[experiments]: https://taskfile.dev/experiments
+[deprecations]: https://taskfile.dev/deprecations
+[deprecate-version-2-schema]: https://github.com/go-task/task/issues/1197
+[issues]: https://github.com/go-task/task/issues
+[discussions]: https://github.com/go-task/task/discussions
+[discord]: https://discord.gg/6TY36E39UK
+[experiments-project]: https://github.com/orgs/go-task/projects/1
+[gentle-force-experiment]: https://github.com/go-task/task/issues/1200
+[remote-taskfiles-experiment]: https://github.com/go-task/task/issues/1317

docs/i18n/ja-JP/docusaurus-plugin-content-blog/authors.yml

@@ -3,3 +3,8 @@ andreynering:
   title: Taskメンテナー
   url: https://github.com/andreynering
   image_url: https://github.com/andreynering.png
+pd93:
+  name: Pete Davison
+  title: Maintainer of Task
+  url: https://github.com/pd93
+  image_url: https://github.com/pd93.png