docs: Update Changelog for release v0.10.0

docs: Make sure the version tag is created before the release is deployed.

TASK: IL-423

CHANGELOG.md

@@ -2,6 +2,14 @@
 
 ## Unreleased
 
+### Breaking Changes
+
+### New Features
+
+### Fixes
+
+## 0.10.0
+
 ### Breaking Changes
 - breaking change: `ExpandChunksOutput` now returns `ChunkWithStartEndIndices` instead of `TextChunk`
 - breaking change: `MultipleChunkRetrieverQa`'s `AnswerSource` now contains `EnrichedChunk` instead of just the `TextChunk`

RELEASE.md

@@ -5,7 +5,9 @@
 - Update the "version" field of the project in `pyproject.toml`
   - We use [semantic versioning](https://semver.org/)
 - Commit the changes and merge to main
-- Create a new release tag in GitHub (Tags -> Releases -> Draft a new release) and save it as draft
+- Tag the latest commit on main with the new release number (e.g. v0.6.0)
+  - `git checkout main, git tag <tag_name>, git push origin <tag_name>`
+- Create a new release draft in GitHub (Tags -> Releases -> Draft a new release) and save it as draft
   - Copy the changelog into the release description. Also add a link to the commits since the last release at the bottom of the description.
 - Make sure the changes have been merged into the main branch.
 - Publish the release.

pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "poetry.core.masonry.api"
 
 [tool.poetry]
 name = "intelligence-layer"
-version = "0.9.1"
+version = "0.10.0"
 description = ""
 authors = ["Aleph Alpha Engineering <[email protected]>"]
 readme = "README.md"