Add new Bashtard post

5 files changed, 64 insertions, 3 deletions

diff --git a/content/projects/bashtard/releases/1.0.0.md b/content/projects/bashtard/releases/1.0.0.md
index 95b133d..ef54893 100644
--- a/content/projects/bashtard/releases/1.0.0.md
+++ b/content/projects/bashtard/releases/1.0.0.md
@@ -3,7 +3,7 @@ title: Bashtard v1.0.0
 date: 2022-05-06
 type: project-release
 packages:
-  bashtard-1.0.0.tar.gz: https://dist.s3.tyil.nl/packages/bashtard/bashtard-1.0.0.tar.gz
+  bashtard-1.0.0.tar.gz: https://dist.tyil.nl/packages/bashtard/bashtard-1.0.0.tar.gz
 ---
 
 This is the initial release of Bashtard.
diff --git a/content/projects/bashtard/releases/2.0.0.md b/content/projects/bashtard/releases/2.0.0.md
index 053637f..29623a7 100644
--- a/content/projects/bashtard/releases/2.0.0.md
+++ b/content/projects/bashtard/releases/2.0.0.md
@@ -3,8 +3,8 @@ title: Bashtard v2.0.0
 date: 2023-05-22
 type: project-release
 packages:
-  bashtard-2.0.0.deb: https://dist.s3.tyil.nl/bashtard/bashtard-2.0.0/bashtard-2.0.0.deb
-  bashtard-2.0.0.tar.gz: https://dist.s3.tyil.nl/bashtard/bashtard-2.0.0/bashtard-2.0.0.tar.gz
+  bashtard-2.0.0.deb: https://dist.tyil.nl/bashtard/bashtard-2.0.0/bashtard-2.0.0.deb
+  bashtard-2.0.0.tar.gz: https://dist.tyil.nl/bashtard/bashtard-2.0.0/bashtard-2.0.0.tar.gz
 ---
 
 ### Added
diff --git a/content/projects/bashtard/releases/2.0.1.md b/content/projects/bashtard/releases/2.0.1.md
new file mode 100644
index 0000000..e8bf49c
--- /dev/null
+++ b/content/projects/bashtard/releases/2.0.1.md
@@ -0,0 +1,19 @@
+---
+title: Bashtard v2.0.1
+date: 2023-09-25
+type: project-release
+packages:
+  bashtard-2.0.1.deb: https://dist.tyil.nl/bashtard/bashtard-2.0.1/bashtard-2.0.1.deb
+  bashtard-2.0.1.tar.gz: https://dist.tyil.nl/bashtard/bashtard-2.0.1/bashtard-2.0.1.tar.gz
+---
+
+### Added
+
+- A new `make` target has been added to build a .tar.gz distributable.
+
+### Changed
+
+- The `svc_` utils should now check which init service you're using when using a
+  linux system. The supported options are still only openrc and systemd.
+- The `pull` subcommand should now properly return with exit-code 0 if no
+  problem were encountered.
diff --git a/content/projects/bashtard/releases/2.0.2.md b/content/projects/bashtard/releases/2.0.2.md
new file mode 100644
index 0000000..5acaaa9
--- /dev/null
+++ b/content/projects/bashtard/releases/2.0.2.md
@@ -0,0 +1,13 @@
+---
+title: Bashtard v2.0.2
+date: 2024-02-28
+type: project-release
+packages:
+  bashtard-2.0.2.deb: https://dist.tyil.nl/bashtard/bashtard-2.0.2/bashtard-2.0.2.deb
+  bashtard-2.0.2.tar.gz: https://dist.tyil.nl/bashtard/bashtard-2.0.2/bashtard-2.0.2.tar.gz
+---
+
+### Fixed
+
+- Configuration values with `=` in their value part should now work properly
+  with `file_template`. Keys with `=` in them are still *not supported*.
diff --git a/content/projects/bashtard/releases/2.1.0.md b/content/projects/bashtard/releases/2.1.0.md
new file mode 100644
index 0000000..24caa53
--- /dev/null
+++ b/content/projects/bashtard/releases/2.1.0.md
@@ -0,0 +1,29 @@
+---
+title: Bashtard v2.1.0
+date: 2024-04-02
+type: project-release
+packages:
+  bashtard-2.1.0.deb: https://dist.tyil.nl/bashtard/bashtard-2.1.0/bashtard-2.1.0.deb
+  bashtard-2.1.0.tar.gz: https://dist.tyil.nl/bashtard/bashtard-2.1.0/bashtard-2.1.0.tar.gz
+---
+
+### Added
+
+- Configuration variables can be assigned values of other variables with the
+  `&=` assignment. This allows a single value to be re-used dynamically, rather
+  than having to explicitly set the same value several times.
+- A `zap` command has been added to remove a playbook from the registry without
+  running the playbook's `playbook_del()` function. This is intended to easily
+  remove registry entries when a playbook itself has been deleted or is
+  otherwise broken in a way that the regular `del` subcommand cannot fix.
+
+### Changed
+
+- The `description.txt` is now allowed to be used without the `.txt` suffix.
+  Usage with the `.txt` suffix continues to be supported as well.
+
+### Fixed
+
+- Passing an empty string as default value to `config` should now properly
+  return an empty string without a warning about the configuration key not
+  existing.