chore: cut specification releases with release-please

.github/workflows/release-please.yaml

@@ -0,0 +1,32 @@
+name: Run Release Please
+
+# Cuts the specification's releases. Until now its vX.Y.Z tags were created by hand, which
+# is easy to postpone and easy to get wrong; release-please proposes the next version and
+# the changelog as a pull request, and tags once that pull request is merged.
+#
+# The tag shape is unchanged: include-component-in-tag is false in release-please-config.json,
+# so a release is tagged vX.Y.Z, continuing from v0.9.0 rather than restarting. Versioning
+# stays below 1.0.0 for now, so a breaking change bumps the minor.
+#
+# This repository enforces DCO, so the bot's own commits need a sign-off too. That is the
+# signoff key in release-please-config.json: as of v5 it is a configuration-file option, and
+# an action input of the same name is ignored.
+
+on:
+  push:
+    branches:
+      - main
+
+permissions:
+  contents: write
+  issues: write
+  pull-requests: write
+
+jobs:
+  release-please:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: googleapis/release-please-action@v5
+        with:
+          token: ${{ secrets.GITHUB_TOKEN }}
+          target-branch: main

.release-please-manifest.json

@@ -0,0 +1,3 @@
+{
+  ".": "0.9.0"
+}

release-please-config.json

@@ -0,0 +1,13 @@
+{
+  "$schema": "https://raw.githubusercontent.com/googleapis/release-please/main/schemas/config.json",
+  "signoff": "OpenFeature Bot <109696520+openfeaturebot@users.noreply.github.com>",
+  "packages": {
+    ".": {
+      "release-type": "simple",
+      "package-name": "spec",
+      "include-component-in-tag": false,
+      "changelog-path": "CHANGELOG.md",
+      "bump-minor-pre-major": true
+    }
+  }
+}

version.txt

@@ -0,0 +1 @@
+0.9.0