v3.33.1

chore(readme): fix typo on link
chore: changelog for #1437
2026-06-12 10:21:50 +00:00 · 2023-12-21 20:10:41 -03:00 · 2023-12-21 20:07:55 -03:00 · 2023-12-21 16:07:44 +00:00 · 2023-12-21 16:04:45 +00:00 · 2023-12-21 15:51:34 +00:00
262 changed files with 11979 additions and 6822 deletions
--- a/.github/ISSUE_TEMPLATE/config.yml
+++ b/.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
--- a/.github/workflows/lint.yml
+++ b/.github/workflows/lint.yml
@@ -14,11 +14,11 @@ jobs:
    steps:
      - uses: actions/setup-go@v3
        with:
-          go-version: 1.20.x
+          go-version: 1.21.x

      - uses: actions/checkout@v3

      - name: golangci-lint
        uses: golangci/golangci-lint-action@v3
        with:
-          version: v1.51.1
+          version: v1.55.2
--- a/.github/workflows/release.yml
+++ b/.github/workflows/release.yml
@@ -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}}
--- a/.github/workflows/test.yml
+++ b/.github/workflows/test.yml
@@ -13,7 +13,7 @@ jobs:
    name: Test
    strategy:
      matrix:
-        go-version: [1.19.x, 1.20.x]
+        go-version: [1.20.x, 1.21.x]
        platform: [ubuntu-latest, macos-latest, windows-latest]
    runs-on: ${{matrix.platform}}
    steps:
--- a/.gitignore
+++ b/.gitignore
@@ -21,7 +21,8 @@ dist/

 # editors
 .idea/
-.vscode/
+.vscode/*
+!.vscode/*-sample.json
 .fleet/

 # exuberant ctags
--- a/.goreleaser.yml
+++ b/.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}}"
--- a/.prettierignore
+++ b/.prettierignore
@@ -1 +0,0 @@
-docs/docs/changelog.md
--- a/.vscode/settings-sample.json
+++ b/.vscode/settings-sample.json
@@ -0,0 +1,5 @@
+{
+  "yaml.schemas": {
+    "./docs/static/schema.json": "Taskfile.yml"
+  }
+}
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -1,5 +1,90 @@
 # 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
@@ -25,7 +110,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 +540,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.
--- a/README.md
+++ b/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 -->
--- a/Taskfile.yml
+++ b/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
--- a/args/args.go
+++ b/args/args.go
@@ -8,7 +8,7 @@ import (

 // ParseV3 parses command line argument: tasks and global variables
 func ParseV3(args ...string) ([]taskfile.Call, *taskfile.Vars) {
-	var calls []taskfile.Call
+	calls := []taskfile.Call{}
 	globals := &taskfile.Vars{}

 	for _, arg := range args {
@@ -18,11 +18,7 @@ func ParseV3(args ...string) ([]taskfile.Call, *taskfile.Vars) {
 		}

 		name, value := splitVar(arg)
-		globals.Set(name, taskfile.Var{Static: value})
-	}
-
-	if len(calls) == 0 {
-		calls = append(calls, taskfile.Call{Task: "default", Direct: true})
+		globals.Set(name, taskfile.Var{Value: value})
 	}

 	return calls, globals
@@ -30,7 +26,7 @@ func ParseV3(args ...string) ([]taskfile.Call, *taskfile.Vars) {

 // ParseV2 parses command line argument: tasks and vars of each task
 func ParseV2(args ...string) ([]taskfile.Call, *taskfile.Vars) {
-	var calls []taskfile.Call
+	calls := []taskfile.Call{}
 	globals := &taskfile.Vars{}

 	for _, arg := range args {
@@ -41,20 +37,16 @@ func ParseV2(args ...string) ([]taskfile.Call, *taskfile.Vars) {

 		if len(calls) < 1 {
 			name, value := splitVar(arg)
-			globals.Set(name, taskfile.Var{Static: value})
+			globals.Set(name, taskfile.Var{Value: 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})
+			calls[len(calls)-1].Vars.Set(name, taskfile.Var{Value: value})
 		}
 	}

-	if len(calls) == 0 {
-		calls = append(calls, taskfile.Call{Task: "default", Direct: true})
-	}
-
 	return calls, globals
 }

--- a/args/args_test.go
+++ b/args/args_test.go
@@ -35,9 +35,9 @@ func TestArgsV3(t *testing.T) {
 			ExpectedGlobals: &taskfile.Vars{
 				OrderedMap: orderedmap.FromMapWithOrder(
 					map[string]taskfile.Var{
-						"FOO": {Static: "bar"},
-						"BAR": {Static: "baz"},
-						"BAZ": {Static: "foo"},
+						"FOO": {Value: "bar"},
+						"BAR": {Value: "baz"},
+						"BAZ": {Value: "foo"},
 					},
 					[]string{"FOO", "BAR", "BAZ"},
 				),
@@ -51,7 +51,7 @@ func TestArgsV3(t *testing.T) {
 			ExpectedGlobals: &taskfile.Vars{
 				OrderedMap: orderedmap.FromMapWithOrder(
 					map[string]taskfile.Var{
-						"CONTENT": {Static: "with some spaces"},
+						"CONTENT": {Value: "with some spaces"},
 					},
 					[]string{"CONTENT"},
 				),
@@ -66,34 +66,28 @@ func TestArgsV3(t *testing.T) {
 			ExpectedGlobals: &taskfile.Vars{
 				OrderedMap: orderedmap.FromMapWithOrder(
 					map[string]taskfile.Var{
-						"FOO": {Static: "bar"},
+						"FOO": {Value: "bar"},
 					},
 					[]string{"FOO"},
 				),
 			},
 		},
 		{
-			Args: nil,
-			ExpectedCalls: []taskfile.Call{
-				{Task: "default", Direct: true},
-			},
+			Args:          nil,
+			ExpectedCalls: []taskfile.Call{},
 		},
 		{
-			Args: []string{},
-			ExpectedCalls: []taskfile.Call{
-				{Task: "default", Direct: true},
-			},
+			Args:          []string{},
+			ExpectedCalls: []taskfile.Call{},
 		},
 		{
-			Args: []string{"FOO=bar", "BAR=baz"},
-			ExpectedCalls: []taskfile.Call{
-				{Task: "default", Direct: true},
-			},
+			Args:          []string{"FOO=bar", "BAR=baz"},
+			ExpectedCalls: []taskfile.Call{},
 			ExpectedGlobals: &taskfile.Vars{
 				OrderedMap: orderedmap.FromMapWithOrder(
 					map[string]taskfile.Var{
-						"FOO": {Static: "bar"},
-						"BAR": {Static: "baz"},
+						"FOO": {Value: "bar"},
+						"BAR": {Value: "baz"},
 					},
 					[]string{"FOO", "BAR"},
 				),
@@ -136,7 +130,7 @@ func TestArgsV2(t *testing.T) {
 					Vars: &taskfile.Vars{
 						OrderedMap: orderedmap.FromMapWithOrder(
 							map[string]taskfile.Var{
-								"FOO": {Static: "bar"},
+								"FOO": {Value: "bar"},
 							},
 							[]string{"FOO"},
 						),
@@ -149,8 +143,8 @@ func TestArgsV2(t *testing.T) {
 					Vars: &taskfile.Vars{
 						OrderedMap: orderedmap.FromMapWithOrder(
 							map[string]taskfile.Var{
-								"BAR": {Static: "baz"},
-								"BAZ": {Static: "foo"},
+								"BAR": {Value: "baz"},
+								"BAZ": {Value: "foo"},
 							},
 							[]string{"BAR", "BAZ"},
 						),
@@ -167,7 +161,7 @@ func TestArgsV2(t *testing.T) {
 					Vars: &taskfile.Vars{
 						OrderedMap: orderedmap.FromMapWithOrder(
 							map[string]taskfile.Var{
-								"CONTENT": {Static: "with some spaces"},
+								"CONTENT": {Value: "with some spaces"},
 							},
 							[]string{"CONTENT"},
 						),
@@ -184,34 +178,28 @@ func TestArgsV2(t *testing.T) {
 			ExpectedGlobals: &taskfile.Vars{
 				OrderedMap: orderedmap.FromMapWithOrder(
 					map[string]taskfile.Var{
-						"FOO": {Static: "bar"},
+						"FOO": {Value: "bar"},
 					},
 					[]string{"FOO"},
 				),
 			},
 		},
 		{
-			Args: nil,
-			ExpectedCalls: []taskfile.Call{
-				{Task: "default", Direct: true},
-			},
+			Args:          nil,
+			ExpectedCalls: []taskfile.Call{},
 		},
 		{
-			Args: []string{},
-			ExpectedCalls: []taskfile.Call{
-				{Task: "default", Direct: true},
-			},
+			Args:          []string{},
+			ExpectedCalls: []taskfile.Call{},
 		},
 		{
-			Args: []string{"FOO=bar", "BAR=baz"},
-			ExpectedCalls: []taskfile.Call{
-				{Task: "default", Direct: true},
-			},
+			Args:          []string{"FOO=bar", "BAR=baz"},
+			ExpectedCalls: []taskfile.Call{},
 			ExpectedGlobals: &taskfile.Vars{
 				OrderedMap: orderedmap.FromMapWithOrder(
 					map[string]taskfile.Var{
-						"FOO": {Static: "bar"},
-						"BAR": {Static: "baz"},
+						"FOO": {Value: "bar"},
+						"BAR": {Value: "baz"},
 					},
 					[]string{"FOO", "BAR"},
 				),
--- a/cmd/release/main.go
+++ b/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)
--- a/cmd/task/task.go
+++ b/cmd/task/task.go
@@ -53,6 +53,8 @@ var flags struct {
 	listJson    bool
 	taskSort    string
 	status      bool
+	noStatus    bool
+	insecure    bool
 	force       bool
 	forceAll    bool
 	watch       bool
@@ -71,6 +73,9 @@ var flags struct {
 	interval    time.Duration
 	global      bool
 	experiments bool
+	download    bool
+	offline     bool
+	timeout     time.Duration
 }

 func main() {
@@ -112,6 +117,8 @@ func run() error {
 	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.BoolVar(&flags.noStatus, "no-status", false, "Ignore status when listing tasks as JSON")
+	pflag.BoolVar(&flags.insecure, "insecure", false, "Forces Task to download Taskfiles over insecure connections.")
 	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.")
@@ -140,6 +147,13 @@ func run() error {
 		pflag.BoolVarP(&flags.forceAll, "force", "f", false, "Forces execution even when the task is up-to-date.")
 	}

+	// Remote Taskfiles experiment will adds the "download" and "offline" flags
+	if experiments.RemoteTaskfiles {
+		pflag.BoolVar(&flags.download, "download", false, "Downloads a cached version of a remote Taskfile.")
+		pflag.BoolVar(&flags.offline, "offline", false, "Forces Task to only use local or cached Taskfiles.")
+		pflag.DurationVar(&flags.timeout, "timeout", time.Second*10, "Timeout for downloading remote Taskfiles.")
+	}
+
 	pflag.Parse()

 	if flags.version {
@@ -173,6 +187,10 @@ func run() error {
 		return nil
 	}

+	if flags.download && flags.offline {
+		return errors.New("task: You can't set both --download and --offline flags")
+	}
+
 	if flags.global && flags.dir != "" {
 		log.Fatal("task: You can't set both --global and --dir")
 		return nil
@@ -216,12 +234,16 @@ func run() error {
 	e := task.Executor{
 		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,
 		Dir:         flags.dir,
-		Dry:         flags.dry,
+		Dry:         flags.dry || flags.status,
 		Entrypoint:  flags.entrypoint,
 		Summary:     flags.summary,
 		Parallel:    flags.parallel,
@@ -237,7 +259,7 @@ func run() error {
 		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
 	}
@@ -251,6 +273,12 @@ func run() error {
 		return err
 	}

+	// If the download flag is specified, we should stop execution as soon as
+	// taskfile is downloaded
+	if flags.download {
+		return nil
+	}
+
 	if listOptions.ShouldListTasks() {
 		foundTasks, err := e.ListTasks(listOptions)
 		if err != nil {
@@ -278,7 +306,13 @@ func run() error {
 		calls, globals = args.ParseV2(tasksAndVars...)
 	}

-	globals.Set("CLI_ARGS", taskfile.Var{Static: cliArgs})
+	// If there are no calls, run the default task instead
+	if len(calls) == 0 {
+		calls = append(calls, taskfile.Call{Task: "default", Direct: true})
+	}
+
+	globals.Set("CLI_ARGS", taskfile.Var{Value: cliArgs})
+	globals.Set("CLI_FORCE", taskfile.Var{Value: flags.force || flags.forceAll})
 	e.Taskfile.Vars.Merge(globals)

 	if !flags.watch {
--- a/docs/.prettierignore
+++ b/docs/.prettierignore
@@ -1 +0,0 @@
-docs/changelog.md
--- a/docs/babel.config.js
+++ b/docs/babel.config.js
@@ -1,3 +0,0 @@
-module.exports = {
-  presets: [require.resolve('@docusaurus/core/lib/babel/preset')],
-};
--- a/docs/babel.config.ts
+++ b/docs/babel.config.ts
@@ -0,0 +1,3 @@
+export default {
+  presets: ['@docusaurus/core/lib/babel/preset'],
+};
--- a/docs/blog/2023-09-02-introducing-experiments.md
+++ b/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 -->
--- a/docs/blog/authors.yml
+++ b/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
--- a/docs/constants.js
+++ b/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
-};
--- a/docs/constants.ts
+++ b/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';
--- a/docs/docs/api_reference.md
+++ b/docs/docs/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
+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,6 +126,7 @@ 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.                                                                                                              |
@@ -128,7 +134,7 @@ There are some special variables that is available on the templating system:
 | `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 +158,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). |
--- a/docs/docs/changelog.md
+++ b/docs/docs/changelog.md
--- a/docs/docs/community.md
+++ b/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)
--- a/docs/docs/contributing.md
+++ b/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?

--- a/docs/docs/deprecations/deprecations.md
+++ b/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.
--- a/docs/docs/deprecations/template.md
+++ b/docs/docs/deprecations/template.md
@@ -0,0 +1,18 @@
+---
+# 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: #\{issue\}
+- Breaks:
+  - \{list any existing functionality that will be broken by this experiment\}
+
+\{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\}
--- a/docs/docs/deprecations/version_2_schema.md
+++ b/docs/docs/deprecations/version_2_schema.md
@@ -0,0 +1,26 @@
+---
+slug: /deprecations/version-2-schema/
+---
+
+# Version 2 Schema
+
+- Issue: #1197
+- Breaks:
+  - Any Taskfiles that use the version 2 schema
+  - `Taskvar.yml` files
+
+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.
+
+A list of changes between version 2 and version 3 are available in the [Task v3
+Release Notes][version-3-release-notes].
+
+<!-- prettier-ignore-start -->
+[version-3-release-notes]: https://github.com/go-task/task/releases/tag/v3.0.0
+<!-- prettier-ignore-end -->
--- a/docs/docs/donate.md
+++ b/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)
--- a/docs/docs/experiments/any_variables.md
+++ b/docs/docs/experiments/any_variables.md
@@ -0,0 +1,183 @@
+---
+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 "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 -->
+[slim-sprig]: https://go-task.github.io/slim-sprig/
+<!-- prettier-ignore-end -->
--- a/docs/docs/experiments/experiments.md
+++ b/docs/docs/experiments/experiments.md
@@ -1,6 +1,6 @@
 ---
 slug: /experiments/
-sidebar_position: 5
+sidebar_position: 6
 ---

 # Experiments
@@ -16,8 +16,11 @@ 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.
+the current set of experimental features and their status in the
+[workflow](#workflow).
+
+You can view a full list of active experiments in the "Experiments" section of
+the sidebar.

 You can enable an experimental feature by:

@@ -42,59 +45,83 @@ 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 -->
-[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
+[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 -->
--- a/docs/docs/experiments/gentle_force.md
+++ b/docs/docs/experiments/gentle_force.md
@@ -0,0 +1,26 @@
+---
+slug: /experiments/gentle-force/
+---
+
+# Gentle Force
+
+- Issue: #1200
+- Environment variable: `TASK_X_FORCE=1`
+- Breaks:
+  - `--force` flag
+
+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!
--- a/docs/docs/experiments/remote_taskfiles.md
+++ b/docs/docs/experiments/remote_taskfiles.md
@@ -0,0 +1,91 @@
+---
+slug: /experiments/remote-taskfiles/
+---
+
+# Remote Taskfiles
+
+- Issue: #1317
+- Environment variable: `TASK_X_REMOTE_TASKFILES=1`
+
+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 -->
+[man-in-the-middle-attacks]: https://en.wikipedia.org/wiki/Man-in-the-middle_attack
+<!-- prettier-ignore-end -->
--- a/docs/docs/experiments/template.md
+++ b/docs/docs/experiments/template.md
@@ -0,0 +1,20 @@
+---
+# 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: #\{issue\}
+- Environment variable: `TASK_X_{feature}`
+- Breaks:
+  - \{list any existing functionality that will be broken by this experiment\}
+- Deprecations:
+  - \{link to any deprecation pages related to this experiment\}
+
+\{Short description of the feature\}
+
+\{Short explanation of how users should migrate to the new behavior\}
--- a/docs/docs/experiments/workflow.md
+++ b/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 -->
--- a/docs/docs/faq.md
+++ b/docs/docs/faq.md
@@ -1,6 +1,6 @@
 ---
 slug: /faq/
-sidebar_position: 7
+sidebar_position: 15
 ---

 # FAQ
@@ -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)

--- a/docs/docs/installation.md
+++ b/docs/docs/installation.md
@@ -19,7 +19,7 @@ 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),
--- a/docs/docs/integrations.md
+++ b/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.

--- a/docs/docs/intro.md
+++ b/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/
--- a/docs/docs/releasing.md
+++ b/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 -->
--- a/docs/docs/styleguide.md
+++ b/docs/docs/styleguide.md
@@ -1,6 +1,6 @@
 ---
 slug: /styleguide/
-sidebar_position: 8
+sidebar_position: 10
 ---

 # Styleguide
--- a/docs/docs/taskfile_versions.md
+++ b/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
@@ -102,10 +102,6 @@ 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
@@ -261,4 +257,7 @@ The variable priority order was also different:

 <!-- prettier-ignore-start -->
 [deprecate-version-2-schema]: https://github.com/go-task/task/issues/1197
+[output]: /usage#output-syntax
+[ignore_errors]: /usage#ignore-errors
+[includes]: /usage#including-other-taskfiles
 <!-- prettier-ignore-end -->
--- a/docs/docs/usage.md
+++ b/docs/docs/usage.md
@@ -642,11 +642,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`.

@@ -1001,9 +1017,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 +1059,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'
@@ -1466,7 +1481,7 @@ 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 exit with [exit code](/api#exit-codes) 205. If approved, Task
 will continue as normal.

 ```bash
@@ -1806,6 +1821,32 @@ 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 -->
 [gotemplate]: https://golang.org/pkg/text/template/
 <!-- prettier-ignore-end -->
--- a/docs/docusaurus.config.js
+++ b/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;
--- a/docs/docusaurus.config.ts
+++ b/docs/docusaurus.config.ts
@@ -0,0 +1,268 @@
+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
+    },
+    // 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;
--- a/docs/i18n/es-ES/docusaurus-plugin-content-blog/2023-09-02-introducing-experiments.md
+++ b/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_face:
+
+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? :face_with_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:
+
+:shrug: 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
--- a/docs/i18n/es-ES/docusaurus-plugin-content-blog/authors.yml
+++ b/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
--- a/docs/i18n/es-ES/docusaurus-plugin-content-docs/current/api_reference.md
+++ b/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             |
@@ -120,12 +125,13 @@ There are some special variables that is available on the templating system:
 | `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 +151,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 +260,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 +304,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                                                                                                  |
--- a/docs/i18n/es-ES/docusaurus-plugin-content-docs/current/changelog.md
+++ b/docs/i18n/es-ES/docusaurus-plugin-content-docs/current/changelog.md
@@ -1,10 +1,55 @@
 ---
 slug: /changelog/
-sidebar_position: 9
+sidebar_position: 14
 ---

 # Changelog

+## v3.32.0 - 2023-11-29
+
+- Added ability to exclude some files from `sources:` by using `exclude:` ([#225](https://github.com/go-task/task/issues/225), [#1324](https://github.com/go-task/task/issues/1324) by [@pd93](https://github.com/pd93) and [@andreynering](https://github.com/andreynering)).
+- The [Remote Taskfiles experiment](https://taskfile.dev/experiments/remote-taskfiles) now prefers remote files over cached ones by default ([#1317](https://github.com/go-task/task/issues/1317), [#1345](https://github.com/go-task/task/issues/1345) by [@pd93](https://github.com/pd93)).
+- Added `--timeout` flag to the [Remote Taskfiles experiment](https://taskfile.dev/experiments/remote-taskfiles) ([#1317](https://github.com/go-task/task/issues/1317), [#1345](https://github.com/go-task/task/issues/1345) by [@pd93](https://github.com/pd93)).
+- Fix bug where dynamic `vars:` and `env:` were being executed when they should actually be skipped by `platforms:` ([#1273](https://github.com/go-task/task/issues/1273), [#1377](https://github.com/go-task/task/issues/1377) by [@andreynering](https://github.com/andreynering)).
+- Fix `schema.json` to make `silent` valid in `cmds` that use `for` ([#1385](https://github.com/go-task/task/issues/1385), [#1386](https://github.com/go-task/task/issues/1386) by [@iainvm](https://github.com/iainvm)).
+- Add new `--no-status` flag to skip expensive status checks when running `task --list --json` ([#1348](https://github.com/go-task/task/issues/1348), [#1368](https://github.com/go-task/task/issues/1368) by [@amancevice](https://github.com/amancevice)).
+
+## v3.31.0 - 2023-10-07
+
+- Enabled the `--yes` flag for the [Remote Taskfiles experiment](https://taskfile.dev/experiments/remote-taskfiles) ([#1317](https://github.com/go-task/task/issues/1317), [#1344](https://github.com/go-task/task/issues/1344) by [@pd93](https://github.com/pd93)).
+- Add ability to set `watch: true` in a task to automatically run it in watch mode ([#231](https://github.com/go-task/task/issues/231), [#1361](https://github.com/go-task/task/issues/1361) by [@andreynering](https://github.com/andreynering)).
+- Fixed a bug on the watch mode where paths that contained `.git` (like `.github`), for example, were also being ignored ([#1356](https://github.com/go-task/task/issues/1356) by [@butuzov](https://github.com/butuzov)).
+- Fixed a nil pointer error when running a Taskfile with no contents ([#1341](https://github.com/go-task/task/issues/1341), [#1342](https://github.com/go-task/task/issues/1342) by [@pd93](https://github.com/pd93)).
+- Added a new [exit code](https://taskfile.dev/api/#exit-codes) (107) for when a Taskfile does not contain a schema version ([#1342](https://github.com/go-task/task/issues/1342) by [@pd93](https://github.com/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](https://github.com/go-task/task/issues/1321), [#1332](https://github.com/go-task/task/issues/1332)).
+- Fixed templating on descriptions on `task --list` ([#1343](https://github.com/go-task/task/issues/1343) by [@blackjid](https://github.com/blackjid)).
+- Fixed a bug where precondition errors were incorrectly being printed when task execution was aborted ([#1337](https://github.com/go-task/task/issues/1337), [#1338](https://github.com/go-task/task/issues/1338) by [@sylv](https://github.com/sylv)-io).
+
+## v3.30.1 - 2023-09-14
+
+- Fixed a regression where some special variables weren't being set correctly ([#1331](https://github.com/go-task/task/issues/1331), [#1334](https://github.com/go-task/task/issues/1334) by [@pd93](https://github.com/pd93)).
+
+## v3.30.0 - 2023-09-13
+
+- Prep work for Remote Taskfiles ([#1316](https://github.com/go-task/task/issues/1316) by [@pd93](https://github.com/pd93)).
+- Added the [Remote Taskfiles experiment](https://taskfile.dev/experiments/remote-taskfiles) as a draft ([#1152](https://github.com/go-task/task/issues/1152), [#1317](https://github.com/go-task/task/issues/1317) by [@pd93](https://github.com/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](https://github.com/go-task/task/issues/1325) by [@ReillyBrogan](https://github.com/ReillyBrogan)).
+
+## v3.29.1 - 2023-08-26
+
+- Update to Go 1.21 (bump minimum version to 1.20) ([#1302](https://github.com/go-task/task/issues/1302) by [@pd93](https://github.com/pd93))
+- Fix a missing a line break on log when using `--watch` mode ([#1285](https://github.com/go-task/task/issues/1285), [#1297](https://github.com/go-task/task/issues/1297) by [@FilipSolich](https://github.com/FilipSolich)).
+- Fix `defer` on JSON Schema ([#1288](https://github.com/go-task/task/issues/1288) by [@calvinmclean](https://github.com/calvinmclean) and [@andreynering](https://github.com/andreynering)).
+- Fix bug in usage of special variables like `{{.USER_WORKING_DIR}}` in combination with `includes` ([#1046](https://github.com/go-task/task/issues/1046), [#1205](https://github.com/go-task/task/issues/1205), [#1250](https://github.com/go-task/task/issues/1250), [#1293](https://github.com/go-task/task/issues/1293), [#1312](https://github.com/go-task/task/issues/1312), [#1274](https://github.com/go-task/task/issues/1274) by [@andarto](https://github.com/andarto), [#1309](https://github.com/go-task/task/issues/1309) by [@andreynering](https://github.com/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](https://github.com/go-task/task/issues/1305), [#1307](https://github.com/go-task/task/issues/1307) by [@visciang](https://github.com/visciang), [#1313](https://github.com/go-task/task/issues/1313) by [@andreynering](https://github.com/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](https://github.com/go-task/task/issues/82), [#1220](https://github.com/go-task/task/issues/1220) by [@pd93](https://github.com/pd93)).
+- Fixed variable propagation in multi-level includes ([#778](https://github.com/go-task/task/issues/778), [#996](https://github.com/go-task/task/issues/996), [#1256](https://github.com/go-task/task/issues/1256) by [@hudclark](https://github.com/hudclark)).
+- Fixed a bug where the `--exit-code` code flag was not returning the correct exit code when calling commands indirectly ([#1266](https://github.com/go-task/task/issues/1266), [#1270](https://github.com/go-task/task/issues/1270) by [@pd93](https://github.com/pd93)).
+- Fixed a `nil` panic when a dependency was commented out or left empty ([#1263](https://github.com/go-task/task/issues/1263) by [@neomantra](https://github.com/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)).
@@ -14,7 +59,7 @@ sidebar_position: 9
 - 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)).
  - 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 the [gentle force experiment](https://taskfile.dev/experiments/gentle-force) 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).

--- a/docs/i18n/es-ES/docusaurus-plugin-content-docs/current/community.md
+++ b/docs/i18n/es-ES/docusaurus-plugin-content-docs/current/community.md
@@ -1,6 +1,6 @@
 ---
 slug: /community/
-sidebar_position: 10
+sidebar_position: 9
 ---

 # Community
--- a/docs/i18n/es-ES/docusaurus-plugin-content-docs/current/deprecations/deprecations.md
+++ b/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.
--- a/docs/i18n/es-ES/docusaurus-plugin-content-docs/current/deprecations/template.md
+++ b/docs/i18n/es-ES/docusaurus-plugin-content-docs/current/deprecations/template.md
@@ -0,0 +1,17 @@
+---
+#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: [#{issue}](https://github.com/go-task/task/issues/{issue})
+- Breaks:
+  - {list any existing functionality that will be broken by this experiment}
+
+{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}
--- a/docs/i18n/es-ES/docusaurus-plugin-content-docs/current/deprecations/version_2_schema.md
+++ b/docs/i18n/es-ES/docusaurus-plugin-content-docs/current/deprecations/version_2_schema.md
@@ -0,0 +1,22 @@
+---
+slug: /deprecations/version-2-schema/
+---
+
+# Version 2 Schema
+
+- Issue: [#1197][deprecate-version-2-schema]
+- Breaks:
+  - Any Taskfiles that use the version 2 schema
+  - `Taskvar.yml` files
+
+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.
+
+A list of changes between version 2 and version 3 are available in the [Task v3 Release Notes][version-3-release-notes].
+
+<!-- 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
--- a/docs/i18n/es-ES/docusaurus-plugin-content-docs/current/donate.md
+++ b/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)
--- a/docs/i18n/es-ES/docusaurus-plugin-content-docs/current/experiments/experiments.md
+++ b/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,7 +11,9 @@ 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 view a full list of active experiments in the "Experiments" section of the sidebar.

 You can enable an experimental feature by:

@@ -28,43 +30,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
--- a/docs/i18n/es-ES/docusaurus-plugin-content-docs/current/experiments/gentle_force.md
+++ b/docs/i18n/es-ES/docusaurus-plugin-content-docs/current/experiments/gentle_force.md
@@ -0,0 +1,21 @@
+---
+slug: /experiments/gentle-force/
+---
+
+# Gentle Force
+
+- Issue: [#1200][gentle-force-experiment]
+- Environment variable: `TASK_X_FORCE=1`
+- Breaks:
+  - `--force` flag
+
+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 -->
+[gentle-force-experiment]: https://github.com/go-task/task/issues/1200
--- a/docs/i18n/es-ES/docusaurus-plugin-content-docs/current/experiments/remote_taskfiles.md
+++ b/docs/i18n/es-ES/docusaurus-plugin-content-docs/current/experiments/remote_taskfiles.md
@@ -0,0 +1,57 @@
+---
+slug: /experiments/remote-taskfiles/
+---
+
+# Remote Taskfiles
+
+- Issue: [#1317][remote-taskfiles-experiment]
+- Environment variable: `TASK_X_REMOTE_TASKFILES=1`
+
+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 -->
+[remote-taskfiles-experiment]: https://github.com/go-task/task/issues/1317
+[man-in-the-middle-attacks]: https://en.wikipedia.org/wiki/Man-in-the-middle_attack
--- a/docs/i18n/es-ES/docusaurus-plugin-content-docs/current/experiments/template.md
+++ b/docs/i18n/es-ES/docusaurus-plugin-content-docs/current/experiments/template.md
@@ -0,0 +1,20 @@
+---
+#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: [#{issue}](https://github.com/go-task/task/issues/{issue})
+- Environment variable: `TASK_X_{feature}`
+- Breaks:
+  - {list any existing functionality that will be broken by this experiment}
+- Deprecations:
+  - {link to any deprecation pages related to this experiment}
+
+{Short description of the feature}
+
+{Short explanation of how users should migrate to the new behavior}
--- a/docs/i18n/es-ES/docusaurus-plugin-content-docs/current/faq.md
+++ b/docs/i18n/es-ES/docusaurus-plugin-content-docs/current/faq.md
@@ -1,6 +1,6 @@
 ---
 slug: /faq/
-sidebar_position: 7
+sidebar_position: 15
 ---

 # FAQ
--- a/docs/i18n/es-ES/docusaurus-plugin-content-docs/current/installation.md
+++ b/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:

--- a/docs/i18n/es-ES/docusaurus-plugin-content-docs/current/integrations.md
+++ b/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.
--- a/docs/i18n/es-ES/docusaurus-plugin-content-docs/current/intro.md
+++ b/docs/i18n/es-ES/docusaurus-plugin-content-docs/current/intro.md
@@ -37,16 +37,6 @@ The above example is just the start, you can take a look at the [usage](/usage)
 - 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 -->
--- a/docs/i18n/es-ES/docusaurus-plugin-content-docs/current/releasing.md
+++ b/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
--- a/docs/i18n/es-ES/docusaurus-plugin-content-docs/current/styleguide.md
+++ b/docs/i18n/es-ES/docusaurus-plugin-content-docs/current/styleguide.md
@@ -1,6 +1,6 @@
 ---
 slug: /styleguide/
-sidebar_position: 8
+sidebar_position: 10
 ---

 # Styleguide
--- a/docs/i18n/es-ES/docusaurus-plugin-content-docs/current/taskfile_versions.md
+++ b/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:
--- a/docs/i18n/es-ES/docusaurus-plugin-content-docs/current/usage.md
+++ b/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.
@@ -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 -->
--- a/docs/i18n/fr-FR/docusaurus-plugin-content-blog/2023-09-02-introducing-experiments.md
+++ b/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_face:
+
+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? :face_with_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:
+
+:shrug: 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
--- a/docs/i18n/fr-FR/docusaurus-plugin-content-blog/authors.yml
+++ b/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
--- a/docs/i18n/fr-FR/docusaurus-plugin-content-docs/current/api_reference.md
+++ b/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             |
@@ -120,12 +125,13 @@ There are some special variables that is available on the templating system:
 | `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 +151,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 +260,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 +304,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                                                                                                  |
--- a/docs/i18n/fr-FR/docusaurus-plugin-content-docs/current/changelog.md
+++ b/docs/i18n/fr-FR/docusaurus-plugin-content-docs/current/changelog.md
@@ -1,10 +1,55 @@
 ---
 slug: /changelog/
-sidebar_position: 9
+sidebar_position: 14
 ---

 # Changelog

+## v3.32.0 - 2023-11-29
+
+- Added ability to exclude some files from `sources:` by using `exclude:` ([#225](https://github.com/go-task/task/issues/225), [#1324](https://github.com/go-task/task/issues/1324) by [@pd93](https://github.com/pd93) and [@andreynering](https://github.com/andreynering)).
+- The [Remote Taskfiles experiment](https://taskfile.dev/experiments/remote-taskfiles) now prefers remote files over cached ones by default ([#1317](https://github.com/go-task/task/issues/1317), [#1345](https://github.com/go-task/task/issues/1345) by [@pd93](https://github.com/pd93)).
+- Added `--timeout` flag to the [Remote Taskfiles experiment](https://taskfile.dev/experiments/remote-taskfiles) ([#1317](https://github.com/go-task/task/issues/1317), [#1345](https://github.com/go-task/task/issues/1345) by [@pd93](https://github.com/pd93)).
+- Fix bug where dynamic `vars:` and `env:` were being executed when they should actually be skipped by `platforms:` ([#1273](https://github.com/go-task/task/issues/1273), [#1377](https://github.com/go-task/task/issues/1377) by [@andreynering](https://github.com/andreynering)).
+- Fix `schema.json` to make `silent` valid in `cmds` that use `for` ([#1385](https://github.com/go-task/task/issues/1385), [#1386](https://github.com/go-task/task/issues/1386) by [@iainvm](https://github.com/iainvm)).
+- Add new `--no-status` flag to skip expensive status checks when running `task --list --json` ([#1348](https://github.com/go-task/task/issues/1348), [#1368](https://github.com/go-task/task/issues/1368) by [@amancevice](https://github.com/amancevice)).
+
+## v3.31.0 - 2023-10-07
+
+- Enabled the `--yes` flag for the [Remote Taskfiles experiment](https://taskfile.dev/experiments/remote-taskfiles) ([#1317](https://github.com/go-task/task/issues/1317), [#1344](https://github.com/go-task/task/issues/1344) by [@pd93](https://github.com/pd93)).
+- Add ability to set `watch: true` in a task to automatically run it in watch mode ([#231](https://github.com/go-task/task/issues/231), [#1361](https://github.com/go-task/task/issues/1361) by [@andreynering](https://github.com/andreynering)).
+- Fixed a bug on the watch mode where paths that contained `.git` (like `.github`), for example, were also being ignored ([#1356](https://github.com/go-task/task/issues/1356) by [@butuzov](https://github.com/butuzov)).
+- Fixed a nil pointer error when running a Taskfile with no contents ([#1341](https://github.com/go-task/task/issues/1341), [#1342](https://github.com/go-task/task/issues/1342) by [@pd93](https://github.com/pd93)).
+- Added a new [exit code](https://taskfile.dev/api/#exit-codes) (107) for when a Taskfile does not contain a schema version ([#1342](https://github.com/go-task/task/issues/1342) by [@pd93](https://github.com/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](https://github.com/go-task/task/issues/1321), [#1332](https://github.com/go-task/task/issues/1332)).
+- Fixed templating on descriptions on `task --list` ([#1343](https://github.com/go-task/task/issues/1343) by [@blackjid](https://github.com/blackjid)).
+- Fixed a bug where precondition errors were incorrectly being printed when task execution was aborted ([#1337](https://github.com/go-task/task/issues/1337), [#1338](https://github.com/go-task/task/issues/1338) by [@sylv](https://github.com/sylv)-io).
+
+## v3.30.1 - 2023-09-14
+
+- Fixed a regression where some special variables weren't being set correctly ([#1331](https://github.com/go-task/task/issues/1331), [#1334](https://github.com/go-task/task/issues/1334) by [@pd93](https://github.com/pd93)).
+
+## v3.30.0 - 2023-09-13
+
+- Prep work for Remote Taskfiles ([#1316](https://github.com/go-task/task/issues/1316) by [@pd93](https://github.com/pd93)).
+- Added the [Remote Taskfiles experiment](https://taskfile.dev/experiments/remote-taskfiles) as a draft ([#1152](https://github.com/go-task/task/issues/1152), [#1317](https://github.com/go-task/task/issues/1317) by [@pd93](https://github.com/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](https://github.com/go-task/task/issues/1325) by [@ReillyBrogan](https://github.com/ReillyBrogan)).
+
+## v3.29.1 - 2023-08-26
+
+- Update to Go 1.21 (bump minimum version to 1.20) ([#1302](https://github.com/go-task/task/issues/1302) by [@pd93](https://github.com/pd93))
+- Fix a missing a line break on log when using `--watch` mode ([#1285](https://github.com/go-task/task/issues/1285), [#1297](https://github.com/go-task/task/issues/1297) by [@FilipSolich](https://github.com/FilipSolich)).
+- Fix `defer` on JSON Schema ([#1288](https://github.com/go-task/task/issues/1288) by [@calvinmclean](https://github.com/calvinmclean) and [@andreynering](https://github.com/andreynering)).
+- Fix bug in usage of special variables like `{{.USER_WORKING_DIR}}` in combination with `includes` ([#1046](https://github.com/go-task/task/issues/1046), [#1205](https://github.com/go-task/task/issues/1205), [#1250](https://github.com/go-task/task/issues/1250), [#1293](https://github.com/go-task/task/issues/1293), [#1312](https://github.com/go-task/task/issues/1312), [#1274](https://github.com/go-task/task/issues/1274) by [@andarto](https://github.com/andarto), [#1309](https://github.com/go-task/task/issues/1309) by [@andreynering](https://github.com/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](https://github.com/go-task/task/issues/1305), [#1307](https://github.com/go-task/task/issues/1307) by [@visciang](https://github.com/visciang), [#1313](https://github.com/go-task/task/issues/1313) by [@andreynering](https://github.com/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](https://github.com/go-task/task/issues/82), [#1220](https://github.com/go-task/task/issues/1220) by [@pd93](https://github.com/pd93)).
+- Fixed variable propagation in multi-level includes ([#778](https://github.com/go-task/task/issues/778), [#996](https://github.com/go-task/task/issues/996), [#1256](https://github.com/go-task/task/issues/1256) by [@hudclark](https://github.com/hudclark)).
+- Fixed a bug where the `--exit-code` code flag was not returning the correct exit code when calling commands indirectly ([#1266](https://github.com/go-task/task/issues/1266), [#1270](https://github.com/go-task/task/issues/1270) by [@pd93](https://github.com/pd93)).
+- Fixed a `nil` panic when a dependency was commented out or left empty ([#1263](https://github.com/go-task/task/issues/1263) by [@neomantra](https://github.com/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)).
@@ -14,7 +59,7 @@ sidebar_position: 9
 - 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)).
  - 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 the [gentle force experiment](https://taskfile.dev/experiments/gentle-force) 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).

--- a/docs/i18n/fr-FR/docusaurus-plugin-content-docs/current/community.md
+++ b/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

--- a/docs/i18n/fr-FR/docusaurus-plugin-content-docs/current/deprecations/deprecations.md
+++ b/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.
--- a/docs/i18n/fr-FR/docusaurus-plugin-content-docs/current/deprecations/template.md
+++ b/docs/i18n/fr-FR/docusaurus-plugin-content-docs/current/deprecations/template.md
@@ -0,0 +1,17 @@
+---
+#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
+---
+
+# {Nom de la fonctionnalité obsolète}
+
+- Issue: [#{issue}](https://github.com/go-task/task/issues/{issue})
+- Breaks:
+  - {lister toutes les fonctionnalités qui vont être brisées par ce changement}
+
+{Description rapide de la fonctionnalité et de la raison de sa dépréciation}
+
+{Courte explication des fonctionnalités à utiliser à la place, et comment les utilisateurs peuvent migrer vers cette autre fonctionnalité}
--- a/docs/i18n/fr-FR/docusaurus-plugin-content-docs/current/deprecations/version_2_schema.md
+++ b/docs/i18n/fr-FR/docusaurus-plugin-content-docs/current/deprecations/version_2_schema.md
@@ -0,0 +1,22 @@
+---
+slug: /deprecations/version-2-schema/
+---
+
+# Version 2 Schema
+
+- Issue: [#1197][deprecate-version-2-schema]
+- Breaks:
+  - Any Taskfiles that use the version 2 schema
+  - `Taskvar.yml` files
+
+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.
+
+A list of changes between version 2 and version 3 are available in the [Task v3 Release Notes][version-3-release-notes].
+
+<!-- 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
--- a/docs/i18n/fr-FR/docusaurus-plugin-content-docs/current/donate.md
+++ b/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. Nous suggérons de donner 50% à chaque mainteneur du montant total que vous prévoyez de donner.

 - [@andreynering](https://github.com/sponsors/andreynering)
 - [@pd93](https://github.com/sponsors/pd93)
--- a/docs/i18n/fr-FR/docusaurus-plugin-content-docs/current/experiments/experiments.md
+++ b/docs/i18n/fr-FR/docusaurus-plugin-content-docs/current/experiments/experiments.md
@@ -1,23 +1,25 @@
 ---
 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.
+Vous pouvez activer une fonctionnalité expérimentale par:
+
+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. Par exemple :

 ```shell
 # .env
@@ -28,43 +30,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
--- a/docs/i18n/fr-FR/docusaurus-plugin-content-docs/current/experiments/gentle_force.md
+++ b/docs/i18n/fr-FR/docusaurus-plugin-content-docs/current/experiments/gentle_force.md
@@ -0,0 +1,21 @@
+---
+slug: /experiments/gentle-force/
+---
+
+# Gentle Force
+
+- Issue: [#1200][gentle-force-experiment]
+- Environment variable: `TASK_X_FORCE=1`
+- Breaks:
+  - `--force` flag
+
+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 -->
+[gentle-force-experiment]: https://github.com/go-task/task/issues/1200
--- a/docs/i18n/fr-FR/docusaurus-plugin-content-docs/current/experiments/remote_taskfiles.md
+++ b/docs/i18n/fr-FR/docusaurus-plugin-content-docs/current/experiments/remote_taskfiles.md
@@ -0,0 +1,57 @@
+---
+slug: /experiments/remote-taskfiles/
+---
+
+# Remote Taskfiles
+
+- Issue: [#1317][remote-taskfiles-experiment]
+- Environment variable: `TASK_X_REMOTE_TASKFILES=1`
+
+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 -->
+[remote-taskfiles-experiment]: https://github.com/go-task/task/issues/1317
+[man-in-the-middle-attacks]: https://en.wikipedia.org/wiki/Man-in-the-middle_attack
--- a/docs/i18n/fr-FR/docusaurus-plugin-content-docs/current/experiments/template.md
+++ b/docs/i18n/fr-FR/docusaurus-plugin-content-docs/current/experiments/template.md
@@ -0,0 +1,20 @@
+---
+#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: [#{issue}](https://github.com/go-task/task/issues/{issue})
+- Environment variable: `TASK_X_{feature}`
+- Breaks:
+  - {list any existing functionality that will be broken by this experiment}
+- Deprecations:
+  - {link to any deprecation pages related to this experiment}
+
+{Short description of the feature}
+
+{Short explanation of how users should migrate to the new behavior}
--- a/docs/i18n/fr-FR/docusaurus-plugin-content-docs/current/faq.md
+++ b/docs/i18n/fr-FR/docusaurus-plugin-content-docs/current/faq.md
@@ -1,6 +1,6 @@
 ---
 slug: /faq/
-sidebar_position: 7
+sidebar_position: 15
 ---

 # FAQ
--- a/docs/i18n/fr-FR/docusaurus-plugin-content-docs/current/installation.md
+++ b/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:

--- a/docs/i18n/fr-FR/docusaurus-plugin-content-docs/current/integrations.md
+++ b/docs/i18n/fr-FR/docusaurus-plugin-content-docs/current/integrations.md
@@ -1,6 +1,6 @@
 ---
 slug: /integrations/
-sidebar_position: 6
+sidebar_position: 8
 ---

 # Integrations
--- a/docs/i18n/fr-FR/docusaurus-plugin-content-docs/current/intro.md
+++ b/docs/i18n/fr-FR/docusaurus-plugin-content-docs/current/intro.md
@@ -37,16 +37,6 @@ L'exemple ci-dessus n'est que le début, vous pouvez jeter un coup d'œil au [gu
 - 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 -->
--- a/docs/i18n/fr-FR/docusaurus-plugin-content-docs/current/releasing.md
+++ b/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
--- a/docs/i18n/fr-FR/docusaurus-plugin-content-docs/current/styleguide.md
+++ b/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
@@ -208,10 +208,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 +223,7 @@ tasks:
          echo "some other complex logic"
        done'

-# good
+# Correct
 version: '3'

 tasks:
--- a/docs/i18n/fr-FR/docusaurus-plugin-content-docs/current/taskfile_versions.md
+++ b/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.
+Le support du schéma v2 est [déprécié][deprecate-version-2-schema] et sera retiré dans une future version.

 :::

-Version 2.6 comes with `preconditions` stanza in tasks.
+La version 2.6 vient avec des `preconditions` dans les tâches.

 ```yaml
 version: '2'
@@ -86,17 +86,17 @@ tasks:
      - aws s3 cp .env s3://myenvironment
 ```

-Please check the [documentation][includes]
+Veuillez consulter la [documentation][includes]

 ## Version 2.2

 :::caution

-v2 schema support is [deprecated][deprecate-version-2-schema] and will be removed in a future release.
+Le support du schéma v2 est [déprécié][deprecate-version-2-schema] et sera retiré dans une future version.

 :::

-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,11 +110,11 @@ includes:

 :::caution

-v2 schema support is [deprecated][deprecate-version-2-schema] and will be removed in a future release.
+Le support du schéma v2 est [déprécié][deprecate-version-2-schema] et sera retiré dans une future version.

 :::

-Version 2.1 includes a global `output` option, to allow having more control over how commands output are printed to the console (see [documentation][output] for more info):
+La version 2.1 inclut une option globale `output` permettant d'avoir plus de contrôle sur la manière dont les logs sont affichés dans la console (voir la [documentation][output] pour plus d'informations):

 ```yaml
 version: '2'
@@ -128,7 +128,7 @@ tasks:
  prefix: server
 ```

-From this version it's also possible to ignore errors of a command or task (check documentation [here][ignore_errors]):
+À partir de cette version, il est également possible d'ignorer les erreurs d'une commande ou d'une tâche (vérifiez la documentation [ici][ignore_errors] ) :

 ```yaml
 version: '2'
@@ -151,11 +151,11 @@ tasks:

 :::caution

-v2 schema support is [deprecated][deprecate-version-2-schema] and will be removed in a future release.
+Le support du schéma v2 est [déprécié][deprecate-version-2-schema] et sera retiré dans une future version.

 :::

-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,12 +224,12 @@ 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 -->

--- a/docs/i18n/fr-FR/docusaurus-plugin-content-docs/current/usage.md
+++ b/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.
@@ -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 -->
--- a/docs/i18n/ja-JP/code.json
+++ b/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": {
--- a/docs/i18n/ja-JP/docusaurus-plugin-content-blog/2023-09-02-introducing-experiments.md
+++ b/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_face:
+
+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? :face_with_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:
+
+:shrug: 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
--- a/docs/i18n/ja-JP/docusaurus-plugin-content-blog/authors.yml
+++ b/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
--- a/docs/i18n/ja-JP/docusaurus-plugin-content-docs/current.json
+++ b/docs/i18n/ja-JP/docusaurus-plugin-content-docs/current.json
@@ -1,6 +1,6 @@
 {
  "version.label": {
-    "message": "Next",
+    "message": "次へ",
    "description": "The label for version current"
  }
 }
--- a/docs/i18n/ja-JP/docusaurus-plugin-content-docs/current/api_reference.md
+++ b/docs/i18n/ja-JP/docusaurus-plugin-content-docs/current/api_reference.md
@@ -5,11 +5,11 @@ toc_min_heading_level: 2
 toc_max_heading_level: 5
 ---

-# API Reference
+# APIリファレンス

 ## CLI

-Task command line tool has the following syntax:
+Taskコマンドラインツールは以下のような構文を持っています:

 ```bash
 task [--flags] [tasks...] [-- CLI_ARGS...]
@@ -17,41 +17,41 @@ task [--flags] [tasks...] [-- CLI_ARGS...]

 :::tip

-If `--` is given, all remaning arguments will be assigned to a special `CLI_ARGS` variable
+`--`が渡されると、次に続く全てのパラメータは`CLI_ARGS`という特別な変数に格納されます

 :::

-| Short | Flag                        | Type     | Default                                      | Description                                                                                                                                                                                                    |
-| ----- | --------------------------- | -------- | -------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `-c`  | `--color`                   | `bool`   | `true`                                       | Colored output. Enabled by default. Set flag to `false` or use `NO_COLOR=1` to disable.                                                                                                                        |
-| `-C`  | `--concurrency`             | `int`    | `0`                                          | Limit number tasks to run concurrently. Zero means unlimited.                                                                                                                                                  |
-| `-d`  | `--dir`                     | `string` | Working directory                            | Sets directory of execution.                                                                                                                                                                                   |
-| `-n`  | `--dry`                     | `bool`   | `false`                                      | Compiles and prints tasks in the order that they would be run, without executing them.                                                                                                                         |
-| `-x`  | `--exit-code`               | `bool`   | `false`                                      | Pass-through the exit code of the task command.                                                                                                                                                                |
-| `-f`  | `--force`                   | `bool`   | `false`                                      | Forces execution even when the task is up-to-date.                                                                                                                                                             |
-| `-g`  | `--global`                  | `bool`   | `false`                                      | Runs global Taskfile, from `$HOME/Taskfile.{yml,yaml}`.                                                                                                                                                        |
-| `-h`  | `--help`                    | `bool`   | `false`                                      | Shows Task usage.                                                                                                                                                                                              |
-| `-i`  | `--init`                    | `bool`   | `false`                                      | Creates a new Taskfile.yml in the current folder.                                                                                                                                                              |
-| `-I`  | `--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).                                         |
-| `-l`  | `--list`                    | `bool`   | `false`                                      | Lists tasks with description of current Taskfile.                                                                                                                                                              |
-| `-a`  | `--list-all`                | `bool`   | `false`                                      | Lists tasks with or without a description.                                                                                                                                                                     |
-|       | `--sort`                    | `string` | `default`                                    | Changes the order of the tasks when listed.<br />`default` - Alphanumeric with root tasks first<br />`alphanumeric` - Alphanumeric<br />`none` - No sorting (As they appear in the Taskfile) |
-|       | `--json`                    | `bool`   | `false`                                      | See [JSON Output](#json-output)                                                                                                                                                                                |
-| `-o`  | `--output`                  | `string` | Default set in the Taskfile or `intervealed` | Sets output style: [`interleaved`/`group`/`prefixed`].                                                                                                                                                         |
-|       | `--output-group-begin`      | `string` |                                              | Message template to print before a task's grouped output.                                                                                                                                                      |
-|       | `--output-group-end`        | `string` |                                              | Message template to print after a task's grouped output.                                                                                                                                                       |
-|       | `--output-group-error-only` | `bool`   | `false`                                      | Swallow command output on zero exit code.                                                                                                                                                                      |
-| `-p`  | `--parallel`                | `bool`   | `false`                                      | Executes tasks provided on command line in parallel.                                                                                                                                                           |
-| `-s`  | `--silent`                  | `bool`   | `false`                                      | Disables echoing.                                                                                                                                                                                              |
-| `-y`  | `--yes`                     | `bool`   | `false`                                      | Assume "yes" as answer to all prompts.                                                                                                                                                                         |
-|       | `--status`                  | `bool`   | `false`                                      | Exits with non-zero exit code if any of the given tasks is not up-to-date.                                                                                                                                     |
-|       | `--summary`                 | `bool`   | `false`                                      | Show summary about a task.                                                                                                                                                                                     |
-| `-t`  | `--taskfile`                | `string` | `Taskfile.yml` or `Taskfile.yaml`            |                                                                                                                                                                                                                |
-| `-v`  | `--verbose`                 | `bool`   | `false`                                      | Enables verbose mode.                                                                                                                                                                                          |
-|       | `--version`                 | `bool`   | `false`                                      | Show Task version.                                                                                                                                                                                             |
-| `-w`  | `--watch`                   | `bool`   | `false`                                      | Enables watch of the given task.                                                                                                                                                                               |
+| ショート | フラグ                         | 型        | デフォルト値                                       | 説明                                                                                                                                                                                                             |
+| ---- | --------------------------- | -------- | -------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `-c` | `--color`                   | `bool`   | `true`                                       | Colored output. Enabled by default. Set flag to `false` or use `NO_COLOR=1` to disable.                                                                                                                        |
+| `-C` | `--concurrency`             | `int`    | `0`                                          | Limit number tasks to run concurrently. Zero means unlimited.                                                                                                                                                  |
+| `-d` | `--dir`                     | `string` | ワーキングディレクトリ                                  | Sets directory of execution.                                                                                                                                                                                   |
+| `-n` | `--dry`                     | `bool`   | `false`                                      | Compiles and prints tasks in the order that they would be run, without executing them.                                                                                                                         |
+| `-x` | `--exit-code`               | `bool`   | `false`                                      | Pass-through the exit code of the task command.                                                                                                                                                                |
+| `-f` | `--force`                   | `bool`   | `false`                                      | Forces execution even when the task is up-to-date.                                                                                                                                                             |
+| `-g` | `--global`                  | `bool`   | `false`                                      | Runs global Taskfile, from `$HOME/Taskfile.{yml,yaml}`.                                                                                                                                                        |
+| `-h` | `--help`                    | `bool`   | `false`                                      | Shows Task usage.                                                                                                                                                                                              |
+| `-i` | `--init`                    | `bool`   | `false`                                      | Creates a new Taskfile.yml in the current folder.                                                                                                                                                              |
+| `-I` | `--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).                                         |
+| `-l` | `--list`                    | `bool`   | `false`                                      | Lists tasks with description of current Taskfile.                                                                                                                                                              |
+| `-a` | `--list-all`                | `bool`   | `false`                                      | Lists tasks with or without a description.                                                                                                                                                                     |
+|      | `--sort`                    | `string` | `default`                                    | Changes the order of the tasks when listed.<br />`default` - Alphanumeric with root tasks first<br />`alphanumeric` - Alphanumeric<br />`none` - No sorting (As they appear in the Taskfile) |
+|      | `--json`                    | `bool`   | `false`                                      | See [JSON Output](#json-output)                                                                                                                                                                                |
+| `-o` | `--output`                  | `string` | Default set in the Taskfile or `intervealed` | Sets output style: [`interleaved`/`group`/`prefixed`].                                                                                                                                                         |
+|      | `--output-group-begin`      | `string` |                                              | Message template to print before a task's grouped output.                                                                                                                                                      |
+|      | `--output-group-end`        | `string` |                                              | Message template to print after a task's grouped output.                                                                                                                                                       |
+|      | `--output-group-error-only` | `bool`   | `false`                                      | Swallow command output on zero exit code.                                                                                                                                                                      |
+| `-p` | `--parallel`                | `bool`   | `false`                                      | Executes tasks provided on command line in parallel.                                                                                                                                                           |
+| `-s` | `--silent`                  | `bool`   | `false`                                      | Disables echoing.                                                                                                                                                                                              |
+| `-y` | `--yes`                     | `bool`   | `false`                                      | Assume "yes" as answer to all prompts.                                                                                                                                                                         |
+|      | `--status`                  | `bool`   | `false`                                      | Exits with non-zero exit code if any of the given tasks is not up-to-date.                                                                                                                                     |
+|      | `--summary`                 | `bool`   | `false`                                      | Show summary about a task.                                                                                                                                                                                     |
+| `-t` | `--taskfile`                | `string` | `Taskfile.yml`または`Taskfile.yaml`             |                                                                                                                                                                                                                |
+| `-v` | `--verbose`                 | `bool`   | `false`                                      | Enables verbose mode.                                                                                                                                                                                          |
+|      | `--version`                 | `bool`   | `false`                                      | Show Task version.                                                                                                                                                                                             |
+| `-w` | `--watch`                   | `bool`   | `false`                                      | Enables watch of the given task.                                                                                                                                                                               |

-## Exit Codes
+## 終了コード

 Task will sometimes exit with specific exit codes. These codes are split into three groups with the following ranges:

@@ -61,20 +61,25 @@ Task will sometimes exit with specific exit codes. These codes are split into th

 A full list of the exit codes and their descriptions can be found below:

-| Code | Description                                                  |
-| ---- | ------------------------------------------------------------ |
-| 0    | Success                                                      |
-| 1    | An unknown error occurred                                    |
-| 100  | No Taskfile was found                                        |
-| 101  | A Taskfile already exists when trying to initialize one      |
-| 102  | The Taskfile is invalid or cannot be parsed                  |
-| 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             |
-| 203  | There a multiple tasks with the same name or alias           |
-| 204  | A task was called too many times                             |
-| 205  | A task was cancelled by the user                             |
-| 206  | A task was not executed due to missing required variables    |
+| コード | 説明                                                           |
+| --- | ------------------------------------------------------------ |
+| 0   | Success                                                      |
+| 1   | An unknown error occurred                                    |
+| 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             |
+| 203 | There a multiple tasks with the same name or alias           |
+| 204 | A task was called too many times                             |
+| 205 | A task was cancelled by the user                             |
+| 206 | A task was not executed due to missing required variables    |

 These codes can also be found in the repository in [`errors/errors.go`](https://github.com/go-task/task/blob/main/errors/errors.go).

@@ -84,7 +89,7 @@ When Task is run with the `-x`/`--exit-code` flag, the exit code of any failed c

 :::

-## JSON Output
+## JSON出力

 When using the `--json` flag in combination with either the `--list` or `--list-all` flags, the output will be a JSON object with the following structure:

@@ -108,7 +113,7 @@ When using the `--json` flag in combination with either the `--list` or `--list-
 }
 ```

-## Special Variables
+## 特殊な変数

 There are some special variables that is available on the templating system:

@@ -120,14 +125,15 @@ There are some special variables that is available on the templating system:
 | `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                                                                                                       |
+| 環境変数                 | デフォルト値  | 説明                                                                                                                |
 | -------------------- | ------- | ----------------------------------------------------------------------------------------------------------------- |
 | `TASK_TEMP_DIR`      | `.task` | Location of the temp dir. Can relative to the project like `tmp/task` or absolute like `/tmp/.task` or `~/.task`. |
 | `TASK_COLOR_RESET`   | `0`     | Color used for white.                                                                                             |
@@ -139,18 +145,18 @@ Some environment variables can be overriden to adjust Task behavior.
 | `TASK_COLOR_RED`     | `31`    | Color used for red.                                                                                               |
 | `FORCE_COLOR`        |         | Force color output usage.                                                                                         |

-## Taskfile Schema
+## Taskfileのスキーマ

-| Attribute  | Type                               | Default       | Description                                                                                                                                                            |
+| 属性         | 型                                  | デフォルト値        | 説明                                                                                                                                                                     |
 | ---------- | ---------------------------------- | ------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
 | `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). |
@@ -181,10 +187,10 @@ includes:

 ### Variable

-| Attribute | Type     | Default | Description                                                              |
-| --------- | -------- | ------- | ------------------------------------------------------------------------ |
-| _itself_  | `string` |         | A static value that will be set to the variable.                         |
-| `sh`      | `string` |         | A shell command. The output (`STDOUT`) will be assigned to the variable. |
+| 属性       | 型        | デフォルト値 | 説明                                                                       |
+| -------- | -------- | ------ | ------------------------------------------------------------------------ |
+| _itself_ | `string` |        | A static value that will be set to the variable.                         |
+| `sh`     | `string` |        | A shell command. The output (`STDOUT`) will be assigned to the variable. |

 :::info

@@ -201,7 +207,7 @@ vars:

 ### Task

-| Attribute       | Type                               | Default                                               | Description                                                                                                                                                                                                                                                                                              |
+| 属性              | 型                                  | デフォルト値                                                | 説明                                                                                                                                                                                                                                                                                                       |
 | --------------- | ---------------------------------- | ----------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
 | `cmds`          | [`[]Command`](#command)            |                                                       | A list of shell commands to be executed.                                                                                                                                                                                                                                                                 |
 | `deps`          | [`[]Dependency`](#dependency)      |                                                       | A list of dependencies of this task. Tasks defined here will run in parallel before this task.                                                                                                                                                                                                           |
@@ -254,8 +260,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 +304,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                                                                                                  |
--- a/docs/i18n/ja-JP/docusaurus-plugin-content-docs/current/changelog.md
+++ b/docs/i18n/ja-JP/docusaurus-plugin-content-docs/current/changelog.md
@@ -1,10 +1,55 @@
 ---
 slug: /changelog/
-sidebar_position: 9
+sidebar_position: 14
 ---

 # Changelog

+## v3.32.0 - 2023-11-29
+
+- Added ability to exclude some files from `sources:` by using `exclude:` ([#225](https://github.com/go-task/task/issues/225), [#1324](https://github.com/go-task/task/issues/1324) by [@pd93](https://github.com/pd93) and [@andreynering](https://github.com/andreynering)).
+- The [Remote Taskfiles experiment](https://taskfile.dev/experiments/remote-taskfiles) now prefers remote files over cached ones by default ([#1317](https://github.com/go-task/task/issues/1317), [#1345](https://github.com/go-task/task/issues/1345) by [@pd93](https://github.com/pd93)).
+- Added `--timeout` flag to the [Remote Taskfiles experiment](https://taskfile.dev/experiments/remote-taskfiles) ([#1317](https://github.com/go-task/task/issues/1317), [#1345](https://github.com/go-task/task/issues/1345) by [@pd93](https://github.com/pd93)).
+- Fix bug where dynamic `vars:` and `env:` were being executed when they should actually be skipped by `platforms:` ([#1273](https://github.com/go-task/task/issues/1273), [#1377](https://github.com/go-task/task/issues/1377) by [@andreynering](https://github.com/andreynering)).
+- Fix `schema.json` to make `silent` valid in `cmds` that use `for` ([#1385](https://github.com/go-task/task/issues/1385), [#1386](https://github.com/go-task/task/issues/1386) by [@iainvm](https://github.com/iainvm)).
+- Add new `--no-status` flag to skip expensive status checks when running `task --list --json` ([#1348](https://github.com/go-task/task/issues/1348), [#1368](https://github.com/go-task/task/issues/1368) by [@amancevice](https://github.com/amancevice)).
+
+## v3.31.0 - 2023-10-07
+
+- Enabled the `--yes` flag for the [Remote Taskfiles experiment](https://taskfile.dev/experiments/remote-taskfiles) ([#1317](https://github.com/go-task/task/issues/1317), [#1344](https://github.com/go-task/task/issues/1344) by [@pd93](https://github.com/pd93)).
+- Add ability to set `watch: true` in a task to automatically run it in watch mode ([#231](https://github.com/go-task/task/issues/231), [#1361](https://github.com/go-task/task/issues/1361) by [@andreynering](https://github.com/andreynering)).
+- Fixed a bug on the watch mode where paths that contained `.git` (like `.github`), for example, were also being ignored ([#1356](https://github.com/go-task/task/issues/1356) by [@butuzov](https://github.com/butuzov)).
+- Fixed a nil pointer error when running a Taskfile with no contents ([#1341](https://github.com/go-task/task/issues/1341), [#1342](https://github.com/go-task/task/issues/1342) by [@pd93](https://github.com/pd93)).
+- Added a new [exit code](https://taskfile.dev/api/#exit-codes) (107) for when a Taskfile does not contain a schema version ([#1342](https://github.com/go-task/task/issues/1342) by [@pd93](https://github.com/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](https://github.com/go-task/task/issues/1321), [#1332](https://github.com/go-task/task/issues/1332)).
+- Fixed templating on descriptions on `task --list` ([#1343](https://github.com/go-task/task/issues/1343) by [@blackjid](https://github.com/blackjid)).
+- Fixed a bug where precondition errors were incorrectly being printed when task execution was aborted ([#1337](https://github.com/go-task/task/issues/1337), [#1338](https://github.com/go-task/task/issues/1338) by [@sylv](https://github.com/sylv)-io).
+
+## v3.30.1 - 2023-09-14
+
+- Fixed a regression where some special variables weren't being set correctly ([#1331](https://github.com/go-task/task/issues/1331), [#1334](https://github.com/go-task/task/issues/1334) by [@pd93](https://github.com/pd93)).
+
+## v3.30.0 - 2023-09-13
+
+- Prep work for Remote Taskfiles ([#1316](https://github.com/go-task/task/issues/1316) by [@pd93](https://github.com/pd93)).
+- Added the [Remote Taskfiles experiment](https://taskfile.dev/experiments/remote-taskfiles) as a draft ([#1152](https://github.com/go-task/task/issues/1152), [#1317](https://github.com/go-task/task/issues/1317) by [@pd93](https://github.com/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](https://github.com/go-task/task/issues/1325) by [@ReillyBrogan](https://github.com/ReillyBrogan)).
+
+## v3.29.1 - 2023-08-26
+
+- Update to Go 1.21 (bump minimum version to 1.20) ([#1302](https://github.com/go-task/task/issues/1302) by [@pd93](https://github.com/pd93))
+- Fix a missing a line break on log when using `--watch` mode ([#1285](https://github.com/go-task/task/issues/1285), [#1297](https://github.com/go-task/task/issues/1297) by [@FilipSolich](https://github.com/FilipSolich)).
+- Fix `defer` on JSON Schema ([#1288](https://github.com/go-task/task/issues/1288) by [@calvinmclean](https://github.com/calvinmclean) and [@andreynering](https://github.com/andreynering)).
+- Fix bug in usage of special variables like `{{.USER_WORKING_DIR}}` in combination with `includes` ([#1046](https://github.com/go-task/task/issues/1046), [#1205](https://github.com/go-task/task/issues/1205), [#1250](https://github.com/go-task/task/issues/1250), [#1293](https://github.com/go-task/task/issues/1293), [#1312](https://github.com/go-task/task/issues/1312), [#1274](https://github.com/go-task/task/issues/1274) by [@andarto](https://github.com/andarto), [#1309](https://github.com/go-task/task/issues/1309) by [@andreynering](https://github.com/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](https://github.com/go-task/task/issues/1305), [#1307](https://github.com/go-task/task/issues/1307) by [@visciang](https://github.com/visciang), [#1313](https://github.com/go-task/task/issues/1313) by [@andreynering](https://github.com/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](https://github.com/go-task/task/issues/82), [#1220](https://github.com/go-task/task/issues/1220) by [@pd93](https://github.com/pd93)).
+- Fixed variable propagation in multi-level includes ([#778](https://github.com/go-task/task/issues/778), [#996](https://github.com/go-task/task/issues/996), [#1256](https://github.com/go-task/task/issues/1256) by [@hudclark](https://github.com/hudclark)).
+- Fixed a bug where the `--exit-code` code flag was not returning the correct exit code when calling commands indirectly ([#1266](https://github.com/go-task/task/issues/1266), [#1270](https://github.com/go-task/task/issues/1270) by [@pd93](https://github.com/pd93)).
+- Fixed a `nil` panic when a dependency was commented out or left empty ([#1263](https://github.com/go-task/task/issues/1263) by [@neomantra](https://github.com/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)).
@@ -14,7 +59,7 @@ sidebar_position: 9
 - 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)).
  - 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 the [gentle force experiment](https://taskfile.dev/experiments/gentle-force) 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).

--- a/docs/i18n/ja-JP/docusaurus-plugin-content-docs/current/community.md
+++ b/docs/i18n/ja-JP/docusaurus-plugin-content-docs/current/community.md
@@ -1,6 +1,6 @@
 ---
 slug: /community/
-sidebar_position: 10
+sidebar_position: 9
 ---

 # Community
--- a/docs/i18n/ja-JP/docusaurus-plugin-content-docs/current/contributing.md
+++ b/docs/i18n/ja-JP/docusaurus-plugin-content-docs/current/contributing.md
@@ -19,13 +19,13 @@ This document applies to the core [Task][task] repository _and_ [Task for Visual
 - **Backwards compatibility** - Will your change break existing Taskfiles? It is much more likely that your change will merged if it backwards compatible. Is there an approach you can take that maintains this compatibility? If not, consider opening an issue first so that API changes can be discussed before you invest your time into a PR.
 - **Experiments** - If there is no way to make your change backward compatible then there is a procedure to introduce breaking changes into minor versions. We call these "\[experiments\]\[experiments\]". If you're intending to work on an experiment, then please read the \[experiments workflow\]\[experiments-workflow\] document carefully and submit a proposal first.

-## 1. Setup
+## 1. セットアップ

- **Go** - Task is written in [Go][go]. We always support the latest two major Go versions, so make sure your version is recent enough.
+- **Go** - Taskは[Go][go]で書かれています。 We always support the latest two major Go versions, so make sure your version is recent enough.
 - **Node.js** - [Node.js][nodejs] is used to host Task's documentation server and is required if you want to run this server locally. It is also required if you want to contribute to the Visual Studio Code extension.
 - **Yarn** - [Yarn][yarn] is the Node.js package manager used by Task.

-## 2. Making changes
+## 2. 変更を加える

 - **Code style** - Try to maintain the existing code style where possible. Go code should be formatted by [`gofumpt`][gofumpt] and linted using [`golangci-lint`][golangci-lint]. Any Markdown or TypeScript files should be formatted and linted by [Prettier][prettier]. This style is enforced by our CI to ensure that we have a consistent style across the project. You can use the `task lint` command to lint the code locally and the `task lint:fix` command to automatically fix any issues that are found.
 - **Documentation** - Ensure that you add/update any relevant documentation. See the [updating documentation](#updating-documentation) section below.
@@ -37,7 +37,7 @@ To run Task with working changes, you can use `go run ./cmd/task`. To run a deve

 To run Task for Visual Studio Code, you can open the project in VSCode and hit F5 (or whatever you debug keybind is set to). This will open a new VSCode window with the extension running. Debugging this way is recommended as it will allow you to set breakpoints and step through the code. Otherwise, you can run `task package` which will generate a `.vsix` file that can be used to manually install the extension.

-### Updating documentation
+### ドキュメントの更新

 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).

--- a/docs/i18n/ja-JP/docusaurus-plugin-content-docs/current/deprecations/deprecations.md
+++ b/docs/i18n/ja-JP/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.
--- a/docs/i18n/ja-JP/docusaurus-plugin-content-docs/current/deprecations/template.md
+++ b/docs/i18n/ja-JP/docusaurus-plugin-content-docs/current/deprecations/template.md
@@ -0,0 +1,17 @@
+---
+#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: [#{issue}](https://github.com/go-task/task/issues/{issue})
+- Breaks:
+  - {list any existing functionality that will be broken by this experiment}
+
+{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}
--- a/docs/i18n/ja-JP/docusaurus-plugin-content-docs/current/deprecations/version_2_schema.md
+++ b/docs/i18n/ja-JP/docusaurus-plugin-content-docs/current/deprecations/version_2_schema.md
@@ -0,0 +1,22 @@
+---
+slug: /deprecations/version-2-schema/
+---
+
+# Version 2 Schema
+
+- Issue: [#1197][deprecate-version-2-schema]
+- Breaks:
+  - Any Taskfiles that use the version 2 schema
+  - `Taskvar.yml` files
+
+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.
+
+A list of changes between version 2 and version 3 are available in the [Task v3 Release Notes][version-3-release-notes].
+
+<!-- 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
--- a/docs/i18n/ja-JP/docusaurus-plugin-content-docs/current/donate.md
+++ b/docs/i18n/ja-JP/docusaurus-plugin-content-docs/current/donate.md
@@ -1,6 +1,6 @@
 ---
 slug: /donate/
-sidebar_position: 15
+sidebar_position: 16
 ---

 # 寄付
@@ -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)
--- a/Show More
+++ b/Show More
Author	SHA1	Message	Date
Andrey Nering	58275b4b33	v3.33.1	2023-12-21 20:10:41 -03:00
Andrey Nering	862237a931	chore(readme): fix typo on link	2023-12-21 20:07:55 -03:00
Pete Davison	9d81608337	chore: changelog for #1437	2023-12-21 16:07:44 +00:00
Pete Davison	39a4b4d413	fix: variable propagation (#1437 )	2023-12-21 16:04:45 +00:00
Pete Davison	21ceb05080	chore: changelog	2023-12-21 15:51:34 +00:00
Pete Davison	b592648d55	feat: support looping over map variables (#1436 ) * feat: support looping over map variables * feat: add .KEY variable	2023-12-21 15:43:56 +00:00
Pete Davison	658b6012a6	revert: docs back to .md files until prettier supports mdx	2023-12-21 15:20:14 +00:00
Pete Davison	311cdf00ab	docs: add information about loops	2023-12-21 11:09:34 +00:00
Pete Davison	453538b405	chore: update any_variables doc to mdx	2023-12-21 02:26:53 +00:00
Andrey Nering	743a15f35b	v3.33.0	2023-12-20 23:20:06 -03:00
Andrey Nering	f00ffad63d	chore: changelog and docs for #1434	2023-12-20 23:17:44 -03:00
Andrey Nering	0d209ef05d	docs: minor updates to the "any variables" experiment page	2023-12-20 23:11:50 -03:00
Pete Davison	e177f48e41	feat: CLI_FORCE special variable (#1434 )	2023-12-21 02:08:57 +00:00
dependabot[bot]	e53dafa47e	chore(deps): bump axios from 1.4.0 to 1.6.2 in /docs (#1433 ) Bumps [axios](https://github.com/axios/axios) from 1.4.0 to 1.6.2. - [Release notes](https://github.com/axios/axios/releases) - [Changelog](https://github.com/axios/axios/blob/v1.x/CHANGELOG.md) - [Commits](https://github.com/axios/axios/compare/v1.4.0...v1.6.2) --- updated-dependencies: - dependency-name: axios dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>	2023-12-20 23:07:22 -03:00
Pete Davison	7c93741670	feat: docusaurus v3 (#1432 ) * feat: docusaurus v3 * feat: update release tool to stop it from converting links - this is now done use mdx plugins * fix: broken links * feat: more github links and prettier config * chore: changelog * fix: blog emoji	2023-12-21 01:59:29 +00:00
Pete Davison	43a2979e77	fix: non-evaluated nil values should be converted to empty strings to avoid empty interface errors in the templater	2023-12-20 19:55:25 -06:00
Pete Davison	cb195da72f	chore: changelog	2023-12-20 19:55:25 -06:00
Pete Davison	77aaf996a1	feat: testdata	2023-12-20 19:55:25 -06:00
Pete Davison	7feceeae87	fix: handle errors when sh is used in Taskfiles with the any variables experiment enabled	2023-12-20 19:55:25 -06:00
Pete Davison	1eeb7d5cf9	fix: dynamic vars break with for because of fast-compiled tasks	2023-12-20 19:55:25 -06:00
Pete Davison	4a0414274f	feat: for supports variables and lists of any type	2023-12-20 19:55:25 -06:00
Pete Davison	1a12b94bd3	feat: new dynamic variable syntax	2023-12-20 19:55:25 -06:00
Pete Davison	12a8fb0581	docs: any variables experiment	2023-12-20 19:55:25 -06:00
Pete Davison	20aad66e48	feat: update schema to support objects and arrays in vars	2023-12-20 19:55:25 -06:00
Pete Davison	1cd26ae1b9	feat: add ability to unmarshal as any when experiment enabled	2023-12-20 19:55:25 -06:00
Pete Davison	5516ac1a00	feat: change Var.Value from string to an any type	2023-12-20 19:55:25 -06:00
Pete Davison	de09e675c1	refactor: rename Var.Static to Var.Value	2023-12-20 19:55:25 -06:00
Pete Davison	f58257a208	feat: add any variable experiment flag	2023-12-20 19:55:25 -06:00
Pete Davison	abf0d29736	chore: changelog	2023-12-20 21:54:52 -03:00
Pete Davison	c5a2e92e5e	feat: add aliases to --json output	2023-12-20 21:54:52 -03:00
Pete Davison	edb9dcd284	chore: bump golangci-lint version	2023-12-19 01:20:11 +00:00
William Sjökvist	cb0e6c5efc	chore(docs): fix typo (#1422 )	2023-12-13 13:35:02 -03:00
task-bot	4e35b1e9c2	chore: sync translations (#1418 )	2023-12-13 13:34:35 -03:00
dependabot[bot]	1becb64d83	chore(deps): bump golang.org/x/term from 0.14.0 to 0.15.0 (#1419 )	2023-12-13 13:34:20 -03:00
Andrey Nering	c4dce8f506	chore(docs): fix typo on "releasing" page	2023-11-29 23:17:32 -03:00
Andrey Nering	7c221ef999	v3.32.0	2023-11-29 22:40:04 -03:00
Pete Davison	ec35d43677	feat: support negative globs (#1324 ) Co-authored-by: Andrey Nering <andrey@nering.com.br>	2023-11-29 22:38:12 -03:00
task-bot	a7958c0e3b	chore: sync translations (#1404 )	2023-11-22 09:52:01 -03:00
Pete Davison	546a4d7e46	feat: prefer remote taskfiles over cached ones (#1345 ) * feat: prefer remote taskfiles over cached ones * feat: implemented cache on network timeout * feat: --download always downloads, but never executes tasks * feat: --timeout flag * fix: bug with timeout error handling * chore: changelog	2023-11-17 14:51:10 -06:00
Andrey Nering	834babe0ef	chore: add changelog + improve code for #1368	2023-11-15 22:38:53 -03:00
Alexander Mancevice	8355f16809	feat: add `--no-status` flag (#1368 ) disables status check when running with `--list` `--json` options	2023-11-15 22:31:02 -03:00
dependabot[bot]	db2414402f	chore(deps): bump golang.org/x/term from 0.13.0 to 0.14.0 (#1395 )	2023-11-15 21:42:36 -03:00
dependabot[bot]	c7f80a3be4	chore(deps): bump golang.org/x/sync from 0.4.0 to 0.5.0 (#1396 )	2023-11-15 21:39:43 -03:00
dependabot[bot]	b883a25c9a	chore(deps): bump github.com/fatih/color from 1.15.0 to 1.16.0 (#1397 )	2023-11-15 21:39:20 -03:00
task-bot	7fbded2b13	chore: sync translations (#1399 )	2023-11-15 21:38:07 -03:00
task-bot	fb506acc27	chore: sync translations (#1389 )	2023-11-07 11:15:18 -03:00
Andrey Nering	a8d3a69013	chore: update discord link on issue template #1390	2023-11-07 11:13:35 -03:00
Iain Majer	30a2415ac8	Add silent to for_call schema (#1386 ) * Add silent to for_call schema * Update Changelog	2023-10-30 12:50:20 +00:00
Andrey Nering	b681ef9868	fix(platforms): do not run dynamic vars for other platforms (#1377 )	2023-10-22 00:42:26 +00:00
task-bot	38efad5aa2	chore: sync translations (#1376 )	2023-10-21 21:40:52 -03:00
Andrey Nering	6de3be1384	refactor(merge): use constant	2023-10-21 21:10:42 -03:00
Andrey Nering	781e55fce9	chore(website): remove gold sponsors section	2023-10-21 18:59:22 -03:00
task-bot	9b0de2e72e	chore: sync translations (#1371 )	2023-10-18 09:51:47 -03:00
dependabot[bot]	d4f7216256	chore(deps): bump @babel/traverse from 7.18.2 to 7.23.2 in /docs (#1374 )	2023-10-18 09:51:17 -03:00
Andrey Nering	2842ae7fb5	chore(docs) add missing `watch: true` to example	2023-10-11 09:40:14 -03:00
task-bot	75aa066d9c	chore: sync translations (#1367 )	2023-10-07 22:10:49 -03:00
Andrey Nering	244aa93b3a	chore(taskfile): add task to install goreleaser	2023-10-07 19:38:16 -03:00
Andrey Nering	6177376e50	v3.31.0	2023-10-07 19:10:57 -03:00
Andrey Nering	b5f6a237cc	chore: add changelog entry for #1338	2023-10-07 19:03:25 -03:00
Marcello Sylvester Bauer	d741dfe26d	fix(precondition): do not print error if context was aborted (#1338 )	2023-10-07 19:01:57 -03:00
Andrey Nering	5168e54af7	chore: add changelog entry for #1343	2023-10-07 18:59:20 -03:00
Juan Ignacio Donoso	05755f3a52	fix: templates on task descriptions (#1343 )	2023-10-07 18:57:14 -03:00
Pete Davison	dc77286282	feat: unify prompts (#1344 )	2023-10-07 21:55:43 +00:00
Andrey Nering	222cd8c8f8	chore: add changelog entry for #1356	2023-10-07 18:41:35 -03:00
Oleg Butuzov	2f92f2ac5f	fix: exclude other "ignored" files. (#1356 )	2023-10-07 18:38:14 -03:00
Andrey Nering	a70f5aafc2	fix: increase max task calls limit from 100 to 1000 Closes #1321 Closes #1332	2023-10-07 18:29:16 -03:00
Andrey Nering	adfb96b637	feat: add ability to set `watch: true` in Taskfile (#1361 )	2023-10-07 18:06:43 -03:00
dependabot[bot]	383746fcee	chore(deps): bump golang.org/x/term from 0.12.0 to 0.13.0 (#1366 )	2023-10-07 19:54:27 +00:00
dependabot[bot]	460ecdf8e9	chore(deps): bump golang.org/x/sync from 0.3.0 to 0.4.0 (#1365 )	2023-10-07 16:48:45 -03:00
dependabot[bot]	74c503a33d	chore(deps): bump postcss from 8.4.14 to 8.4.31 in /docs (#1364 )	2023-10-07 16:48:25 -03:00
skaluzka	f0d25515e6	chore: remove accidentally added taskfile-dag.gv (#1357 ) No real code changes here. It looks that an extra file has been committed by mistake in `b1ff13d3e8`. Signed-off-by: skaluzka <skaluzka@protonmail.com>	2023-10-01 16:32:04 +01:00
task-bot	9dc7502e4f	chore: sync translations (#1336 )	2023-09-20 09:53:38 -03:00
Pete Davison	078e213890	feat: error handling for undefined schema version (#1342 ) * feat: error handling for undefined schema version * docs: error codes * chore: changelog	2023-09-19 19:21:40 +01:00
Pete Davison	b1ff13d3e8	docs: typo	2023-09-15 17:30:22 +00:00
Andrey Nering	f5aca75798	chore(docs): update branch name on some links	2023-09-14 21:45:25 -03:00
Andrey Nering	99d247e254	release: v3.30.1	2023-09-14 21:31:13 -03:00
Pete Davison	d1d312f396	refactor: minor improvements to setCurrentDir	2023-09-14 21:28:43 -03:00
Pete Davison	ba299aa71f	fix: incorrect remote taskfiles cache directory	2023-09-14 21:28:43 -03:00
Pete Davison	92f30d4d70	chore: changelog	2023-09-14 21:28:43 -03:00
Pete Davison	93cccd4027	fix: only create a cache if the node is remote	2023-09-14 21:28:43 -03:00
Pete Davison	8e7e231aec	fix: e.Dir not being set to the correct directory	2023-09-14 21:28:43 -03:00
Andrey Nering	72d77eb6c0	chore(deps): upgrade slim-sprig to v3.0.0 (#1329 )	2023-09-14 01:59:35 +00:00
Andrey Nering	42ac242927	release: v3.30.0	2023-09-13 22:04:01 -03:00
Andrey Nering	d0551353f3	chore: add changelog entry for #1325	2023-09-13 21:43:40 -03:00
Reilly Brogan	1417f9f6cd	feat(checksum): replace md5 with xxh3 to improve performance (#1325 )	2023-09-13 21:26:48 -03:00
dependabot[bot]	978d66e148	chore(deps): bump golang.org/x/term from 0.11.0 to 0.12.0 (#1326 )	2023-09-13 21:12:47 -03:00
task-bot	4fd69154a3	chore: sync translations (#1328 )	2023-09-13 21:12:26 -03:00
Pete Davison	22ce67c5e5	feat: remote taskfiles (HTTP) (#1152 ) * feat: remote taskfiles over http * feat: allow insecure connections when --insecure flag is provided * feat: better error handling for fetch errors * fix: ensure cache directory always exists * fix: setup logger before everything else * feat: put remote taskfiles behind an experiment * feat: --download and --offline flags for remote taskfiles * feat: node.Read accepts a context * feat: experiment docs * chore: changelog * chore: remove unused optional param from Node interface * chore: tidy up and generalise NewNode function * fix: use sha256 in remote checksum * feat: --download by itself will not run a task * feat: custom error if remote taskfiles experiment is not enabled * refactor: BaseNode functional options and simplified FileNode * fix: use hex encoding for checksum instead of b64	2023-09-12 22:42:54 +01:00
task-bot	84ad0056e4	chore: sync translations (#1323 )	2023-09-04 09:46:45 -03:00
Pete Davison	07d5e80c57	fix: minor blog typos	2023-09-03 03:19:11 +00:00
Pete Davison	c6241af64a	fix: il8n blog authors	2023-09-02 22:15:58 +00:00
Pete Davison	4f6eea8799	blog: introducing experiments	2023-09-02 21:52:43 +00:00
Pete Davison	a207289955	chore: update experiments and deprecation docs (#1315 )	2023-09-02 17:48:05 -03:00
Andrey Nering	3f2abe011b	chore: upgrade Go to v1.21.0 on lint and release actions	2023-09-02 17:43:45 -03:00
Pete Davison	afe8a618fe	feat: node refactor (#1316 ) * refactor: node reader interface * refactor: rewrite Taskfile() as anon recursive func * chore: NewNodeFromIncludedTaskfile * chore: changelog	2023-09-02 21:24:01 +01:00
task-bot	b2e6c93b4b	chore: sync translations (#1314 )	2023-08-28 21:20:30 -03:00
Andrey Nering	c3d2437c3a	chore(changelog): consolidate v3.29.0 and v3.29.1	2023-08-26 19:17:43 -03:00
Andrey Nering	e2552dae45	chore(website): update release docs to include instructions for winget	2023-08-26 19:17:24 -03:00
Andrey Nering	1189bdec87	goreleaser: skip automatic winget release on ci	2023-08-26 19:00:14 -03:00
Andrey Nering	f51f9621d1	fix: goreleaser deprecation on ci	2023-08-26 18:52:10 -03:00
Andrey Nering	19eba3cc14	v3.29.1	2023-08-26 18:45:44 -03:00
Andrey Nering	5b8b58b6d9	v3.29.0	2023-08-26 18:39:18 -03:00
Andrey Nering	d1f643ebd9	fix: `--status` flag should not have side-effects (#1313 ) Closes #1305 Closes #1307 Co-authored-by: Giovanni Visciano <giovanni_visciano@yahoo.it>	2023-08-26 21:30:23 +00:00
Andrey Nering	e96712b020	fix: make sure USER_WORKING_DIR works corrently with includes (#1309 ) Closes #1046 Closes #1205 Closes #1250 Closes #1293 Closes #1274 Closes #1309 Closes #1312 Co-authored-by: Marcus Spading <ms@fragmentum.net>	2023-08-26 21:06:50 +00:00
task-bot	6102900060	chore: sync translations (#1308 )	2023-08-18 00:06:37 +00:00
Pete Davison	6f986af0d4	feat: bump minimum go version to 1.20 (#1302 )	2023-08-11 22:46:37 +01:00
Andrey Nering	dd9b1a1065	chore: fix goreleaser deprecations	2023-08-09 22:50:07 -03:00
Andrey Nering	ae135f5203	chore: release automatically to winget using goreleaser	2023-08-09 22:44:29 -03:00
Calvin McLean	c42bc6914e	fix: defer keyword in json schema Closes #1288	2023-08-09 22:03:17 -03:00
Andrey Nering	0cddd8c167	chore(vscode): add sample settings.json with yaml schema configuration	2023-08-09 21:30:15 -03:00
Andrey Nering	22cd0edfc9	fix: signal and watch tests	2023-08-09 21:12:50 -03:00
Filip Solich	600966ac26	fix: add missing `\n` to watcher log Closes #1285 Closes #1297	2023-08-09 21:09:11 -03:00
Andrey Nering	2b21fd2eda	chore(website): reactivate carbon	2023-08-09 20:58:59 -03:00
task-bot	90a8c26b25	chore: sync translations (#1291 )	2023-08-05 11:33:39 -03:00
dependabot[bot]	7145791f62	chore(deps): bump golang.org/x/term from 0.10.0 to 0.11.0 (#1298 )	2023-08-05 11:33:18 -03:00
James Sansbury	d9a4b4241e	docs: add required version for supporting loops (#1290 )	2023-08-01 11:26:40 -03:00
task-bot	f219e1ee76	chore: sync translations (#1287 )	2023-07-30 20:21:40 +00:00
skaluzka	c0d9c81393	docs: fix few typos in the api reference page (#1286 )	2023-07-30 17:14:09 -03:00
task-bot	7bcdccc645	chore: sync translations (#1280 )	2023-07-26 12:51:01 +00:00