Bump version to 0.1.0b5 for next development cycle (#121)

Post-release version bump. Ensures builds from source are
distinguishable from the published b4 release.

Also adds the post-release version bump step to CONTRIBUTING.md.

Co-authored-by: tpellissier <tpellissier@microsoft.com>
Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Author: 3 people

CONTRIBUTING.md

@@ -109,4 +109,16 @@ Brief summary of the release
 ### Fixed
 - Bug fix 1 (#125)
 - Bug fix 2 (#126)
+```
+
+**Post-Release Version Bump:**
+
+After tagging and publishing a release, immediately bump the version on `main` to the next
+development target. This ensures builds from source are clearly distinguished from the
+published release:
+
+```bash
+# After publishing v0.1.0b4, bump to v0.1.0b5 on main
+# Update both pyproject.toml and src/PowerPlatform/Dataverse/__version__.py
+# Commit directly to main: "Bump version to 0.1.0b5 for next development cycle"
 ```

pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "PowerPlatform-Dataverse-Client"
-version = "0.1.0b4"
+version = "0.1.0b5"
 description = "Python SDK for Microsoft Dataverse"
 readme = {file = "README.md", content-type = "text/markdown"}
 authors = [{name = "Microsoft Corporation"}]

src/PowerPlatform/Dataverse/__version__.py

@@ -3,4 +3,4 @@
 
 """Version information for PowerPlatform-Dataverse-Client package."""
 
-__version__ = "0.1.0b4"
+__version__ = "0.1.0b5"