chore: prep any variables for release (go-task#1586)

* chore: release blog post

* chore: rename blog post to any-variables

* chore: update the release version in the blog

* chore: update blog date

website/blog/2024-04-09-variables.mdx → website/blog/2024-05-09-any-variables.mdx

@@ -6,7 +6,6 @@ authors: [pd93]
 tags: [experiments, variables]
 image: https://i.imgur.com/mErPwqL.png
 hide_table_of_contents: false
-draft: true
 ---
 
 import Tabs from '@theme/Tabs';
@@ -15,7 +14,7 @@ import TabItem from '@theme/TabItem';
 Task has always had variables, but even though you were able to define them
 using different YAML types, they would always be converted to strings by Task.
 This limited users to string manipulation and encouraged messy workarounds for
-simple problems. Starting from [v3.36.0][v3.36.0], this is no longer the case!
+simple problems. Starting from [v3.37.0][v3.37.0], this is no longer the case!
 Task now supports most variable types, including **booleans**, **integers**,
 **floats** and **arrays**!
 
@@ -175,7 +174,7 @@ We're looking for feedback on a couple of different proposals, so please give
 them a go and let us know what you think. :pray:
 
 {/* prettier-ignore-start */}
-[v3.36.0]: https://github.com/go-task/task/releases/tag/v3.36.0
+[v3.37.0]: https://github.com/go-task/task/releases/tag/v3.37.0
 [slim-sprig-math]: https://go-task.github.io/slim-sprig/math.html
 [slim-sprig-list]: https://go-task.github.io/slim-sprig/lists.html
 [map-variables]: /experiments/map-variables