chore(release): bump version to 0.2.24 - #4
Merged
Merged
Conversation
Erhöht die App-Version nach dem Merge von Paket C + Secret-Hygiene (PR #3), damit Code-Version und das anstehende Release-Tag v0.2.24 übereinstimmen. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Was
Hebt die App-Version von
0.2.23auf0.2.24an (app/__init__.py, Single Source of Truth).Warum
Nach dem Merge von Paket C + Secret-Hygiene (PR #3, Squash
f74b45b) stand die Code-Version noch auf0.2.23, während das bestehende Tagv0.2.23auf einen älteren Commit zeigt. Dieser Bump richtet Code-Version und das anschließende Release-Tagv0.2.24aufeinander aus.Tests
python3 -m compileall apppytest tests/test_version.py -q→ 1 passed (Semver-Format)git diff --check→ sauberNächster Schritt
Nach Merge wird
v0.2.24auf den Merge-Commit gesetzt und gepusht.