diff --git a/CHANGELOG.md b/CHANGELOG.md
index 3390a6d94..528c545cc 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -2,6 +2,12 @@
 
 ## Unreleased
 ### Added
+### Fixed
+### Changed
+### Removed
+
+## 5.5.0 - 2025.05.06
+### Added
 - Wrapped SCIPgetChildren and added getChildren and test (also test getOpenNodes) 
 - Wrapped SCIPgetLeaves, SCIPgetNLeaves, and added getLeaves, getNLeaves and test
 - Wrapped SCIPgetSiblings, SCIPgetNSiblings, and added getSiblings, getNSiblings and test
diff --git a/RELEASE.md b/RELEASE.md
index 1ba05b4d3..88d763a32 100644
--- a/RELEASE.md
+++ b/RELEASE.md
@@ -1,16 +1,16 @@
 # Release Checklist
 The following are the steps to follow to make a new PySCIPOpt release. They should mostly be done in order. 
 - [ ] Check if [scipoptsuite-deploy](https://github.com/scipopt/scipoptsuite-deploy) needs a new release, if a new SCIP version is released for example, or new dependencies (change symmetry dependency, add support for papilo/ parallelization.. etc). And Update release links in `pyproject.toml`
-- [ ] Check if the table in [readme](https://github.com/scipopt/PySCIPOpt#installation) needs to be updated. 
+- [ ] Check if the table in the [documentation](https://pyscipopt.readthedocs.io/en/latest/build.html#building-from-source) needs to be updated. 
 - [ ] Update version number according to semantic versioning [rules](https://semver.org/) in `src/pyscipopt/_version.py` and `setup.py`
-- [ ] Update `CHANGELOG.md`; Change the `Unlreased` to the new version number and add an empty unreleased section.
+- [ ] Update `CHANGELOG.md`; Change the `Unreleased` to the new version number and add an empty unreleased section.
 - [ ] Create a release candidate on test-pypi by running the workflow “Build wheels” in Actions->build wheels, with these parameters `upload:true, test-pypi:true` 
 - [ ] If the pipeline passes, test the released pip package on test-pypi by running and checking that it works
 ```bash
 pip install -i https://test.pypi.org/simple/ PySCIPOpt
 ```
 - [ ] If it works, release on pypi.org with running the same workflow but with `test-pypi:false`.
-- [ ] Then create a tag wit the new version (from the master branch)
+- [ ] Then create a tag with the new version (from the master branch)
 ```bash
 git tag vX.X.X
 git push origin vX.X.X
diff --git a/setup.py b/setup.py
index 48abf2926..abebcc5d4 100644
--- a/setup.py
+++ b/setup.py
@@ -110,7 +110,7 @@
 
 setup(
     name="PySCIPOpt",
-    version="5.4.1",
+    version="5.5.0",
     description="Python interface and modeling environment for SCIP",
     long_description=long_description,
     long_description_content_type="text/markdown",
diff --git a/src/pyscipopt/_version.py b/src/pyscipopt/_version.py
index 2ac7a45eb..714c807ce 100644
--- a/src/pyscipopt/_version.py
+++ b/src/pyscipopt/_version.py
@@ -1 +1 @@
-__version__ = '5.4.1'
+__version__ = '5.5.0'