chore: ignore Dream local state and bump to 0.22.1#19
Merged
Conversation
Keep .claude/dream/ (baseline, findings ledger, run logs) out of the repository. Sync uv.lock bloomy-python package version to 0.22.0 to match pyproject.toml.
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
1 participant
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.
Summary
Keep Dream plugin local state out of the repository and sync packaging metadata after the 0.22.0 release.
Why
.claude/dream/. That data is machine-local and must not be committed.uv.lockstill listed package version0.21.2whilepyproject.tomlwas already at0.22.0on main. The lockfile needed a sync.What changed
.gitignore: ignore.claude/dream/uv.lock: setbloomy-pythonpackage version to match the project versionpyproject.toml+uv.lock: patch bump to 0.22.1Test plan
.claude/dream/is ignored and not tracked0.22.1inpyproject.tomlanduv.lock