Remove old new-in badges

content/en/hugo-modules/use-modules.md

@@ -133,8 +133,6 @@ Also see the [CLI Doc](/commands/hugo_mod_clean/).
 
 ## Module workspaces
 
-{{< new-in 0.109.0 >}}
-
 Workspace support was added in [Go 1.18](https://go.dev/blog/get-familiar-with-workspaces) and Hugo got solid support for it in the `v0.109.0` version.
 
 A common use case for a workspace is to simplify local development of a site with its theme modules.

content/en/hugo-pipes/postprocess.md

@@ -88,7 +88,7 @@ HUGO_ENVIRONMENT
 : The value e.g. set with `hugo -e production` (defaults to `production` for `hugo` and `development` for `hugo server`).
 
 HUGO_PUBLISHDIR
-: {{< new-in 0.109.0 >}} The absolute path to the publish directory (the `public` directory). Note that the value will always point to a directory on disk even when running `hugo server` in memory mode. If you write to this folder from PostCSS when running the server, you could run the server with one of these flags:
+: The absolute path to the publish directory (the `public` directory). Note that the value will always point to a directory on disk even when running `hugo server` in memory mode. If you write to this folder from PostCSS when running the server, you could run the server with one of these flags:
 
 ```sh
 hugo server --renderToDisk

content/en/hugo-pipes/transpile-sass-to-css.md

@@ -42,7 +42,7 @@ transpiler
 targetPath
 : (`string`) If not set, the transformed resource's target path will be the original path of the asset file with its extension replaced by `.css`.
 
-vars {{< new-in 0.109.0 >}}
+vars
 : (`map`) A map of key-value pairs that will be available in the `hugo:vars` namespace. Useful for [initializing Sass variables from Hugo templates](https://discourse.gohugo.io/t/42053/).
 
 ```scss

content/en/methods/page/Ancestors.md

@@ -16,8 +16,6 @@ action:
   signatures: [PAGE.Ancestors]
 ---
 
-{{< new-in 0.109.0 >}}
-
 {{% include "methods/page/_common/definition-of-section.md" %}}
 
 With this content structure: