[ImgBot] Optimize images - #1
Open
imgbot[bot] wants to merge 1 commit into
Open
Conversation
*Total -- 1,679.45kb -> 1,330.46kb (20.78%) /docs/assets/images/dashboard-v3.3.0-preview.png -- 428.57kb -> 254.08kb (40.71%) /docs/statistics/charts/contributors.png -- 237.97kb -> 198.39kb (16.63%) /docs/statistics/charts/october_sprint.png -- 192.33kb -> 165.03kb (14.2%) /docs/statistics/charts/activity_patterns.png -- 268.41kb -> 232.32kb (13.45%) /docs/statistics/charts/growth_trajectory.png -- 288.58kb -> 250.06kb (13.35%) /docs/statistics/charts/monthly_activity.png -- 255.36kb -> 223.25kb (12.58%) /docs/assets/images/project-infographic.svg -- 8.23kb -> 7.33kb (10.96%) Signed-off-by: ImgBotApp <ImgBotHelp@gmail.com>
amm10090
pushed a commit
that referenced
this pull request
Nov 8, 2025
…_tag) Fixes two critical bugs introduced in v8.19.0 affecting hybrid storage backend: **Bug #1: retrieve_memory parameter error** - Root cause: MemoryService.retrieve_memories() was calling storage.retrieve() with unsupported 'tags' and 'memory_type' parameters - Fix: Removed unsupported parameters from storage call and implemented post-retrieval filtering in MemoryService for tags/type - Impact: retrieve_memory tool now works correctly with all storage backends **Bug doobidoo#2: search_by_tag type error** - Root cause: Code assumed created_at was always string (ISO format), but hybrid storage returns float timestamps - Location: server.py lines 2232, 2180 (handle_search_by_tag, handle_retrieve_memory) - Fix: Added type checking to handle both float (timestamp) and string (ISO format) using datetime.fromtimestamp() for floats and fromisoformat() for strings - Impact: search_by_tag tool now works correctly with hybrid storage **Testing:** - Updated tests/unit/test_memory_service.py to match new behavior - All retrieve_memory tests passing - Both tools verified working in production Closes doobidoo#211 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
amm10090
pushed a commit
that referenced
this pull request
Nov 26, 2025
Based on v8.28.0 release lessons learned (PR doobidoo#228): ## New Features 1. **CHANGELOG Validation Protocol** (new section) - Mandatory validation commands before any release - Detection for duplicate sections, incorrect order, content duplication - Specific examples from PR doobidoo#228 mistakes - Post-merge validation before tag creation 2. **Four-File Version Bump Procedure** (enhanced) - Explicit requirement: init.py, pyproject.toml, README.md, uv.lock - All files must be committed together - Updated from 3-file to 4-file awareness 3. **Documentation Updates** (validation-first approach) - New step 3a: CHANGELOG Validation (run grep checks FIRST) - Fix issues before proceeding with content updates - Verify no duplicates, correct position after [Unreleased] 4. **Quality Assurance Checklist** (4 new items) - [ ] No duplicate version sections (verified with grep) - [ ] Versions in reverse chronological order - [ ] New version positioned after [Unreleased] - [ ] No content duplicated from previous versions - Updated "three files" → "four files" 5. **Post-Merge Validation** (new step 6) - Run CHANGELOG validation before creating tag - Check version consistency across all four files - Mandatory fix commit if issues found - DO NOT proceed with tag until validated ## Root Causes Addressed - Issue #1: Content duplication → grep-based detection - Issue doobidoo#2: Incorrect order → chronological validation - Issue doobidoo#3: Missing validation → mandatory checks - Issue doobidoo#4: Version inconsistency → four-file awareness ## Prevention Next release will automatically detect CHANGELOG issues before creating tags, preventing the 2-commit cleanup needed for v8.28.0 (commits 4d4552f + f3a9abc). Lines added: ~95 Impact: Critical path improvements for all future releases
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.
Beep boop. Your images are optimized!
Your image file size has been reduced by 21% 🎉
Details
📝 docs |
repo | 🙋🏾 issues | 🏪 marketplace
~Imgbot - Part of Optimole family