fix(deps): update module github.com/redis/go-redis/v9 to v9.17.2 #57
Conversation
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
renovate
bot
force-pushed
the
renovate/github.com-redis-go-redis-v9-9.x
branch
from
60a8261 to
6f158e2
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/github.com-redis-go-redis-v9-9.x
branch
from
6f158e2 to
a13c86f
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/github.com-redis-go-redis-v9-9.x
branch
from
a13c86f to
d44b6d1
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/github.com-redis-go-redis-v9-9.x
branch
from
d44b6d1 to
c74635e
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/github.com-redis-go-redis-v9-9.x
branch
from
c74635e to
be957ca
Compare
renovate
bot
changed the title
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/github.com-redis-go-redis-v9-9.x
branch
from
be957ca to
cb0e711
Compare
renovate
bot
force-pushed
the
renovate/github.com-redis-go-redis-v9-9.x
branch
from
cb0e711 to
c5f4989
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/github.com-redis-go-redis-v9-9.x
branch
from
c5f4989 to
33c42f0
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/github.com-redis-go-redis-v9-9.x
branch
from
33c42f0 to
5069c33
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/github.com-redis-go-redis-v9-9.x
branch
from
5069c33 to
727c551
Compare
renovate
bot
changed the title
Task: 5.5 Implement Kubernetes readiness features - Fixed readiness route tests to use correct Authelia configuration keys - Fixed MainRoute tests to include all required Authelia headers - All health endpoint tests now pass - Kubernetes readiness and liveness probes fully functional
Task 5.8: Final integration testing and validation - Comprehensive integration tests for OAuth2/OIDC providers (Casdoor, Keycloak, Authentik) - Cache behavior validation across all providers (memory, redis, file, disabled) - Elasticsearch failover scenario testing - Kubernetes deployment readiness validation Task 5.11: Phase 5 Checkpoint - Production readiness complete - All tests passing (100% success rate) - Build succeeds without errors or warnings - System ready for production deployment
- Add Requirement 17 for documentation migration to Starlight framework - Configure Starlight with default styling, light/dark/system themes - Add Mermaid diagram support using rehype-mermaid plugin - Include Pagefind search functionality (built-in) - Specify English-only content without internationalization - Add Phase 6 implementation tasks for documentation migration - Create Context7 MCP tools steering rule for research phases - Update design with Starlight architecture and configuration - Add correctness properties for documentation completeness - Configure GitHub Pages deployment with Node.js 24 and Task runner Requirements: 17.1-17.13 covering migration, themes, search, Mermaid, deployment
Task: 6.1 Research and setup Starlight documentation framework - Created new Starlight project structure in docs/ folder - Configured astro.config.mjs with proper site settings and navigation - Added astro-mermaid plugin for client-side Mermaid diagram rendering - Set up package.json with required dependencies (no Playwright needed) - Created elastauth logo and basic index page with architecture diagram - Verified build process works correctly with Mermaid integration - Configured GitHub Pages deployment settings (site/base URLs) Requirements: 17.2, 17.6, 17.11
Task: 6.4 Configure Starlight navigation and features - Set up sidebar navigation with proper categorization - Configure auto-generation for provider and cache sections - Add social links and edit links to GitHub repository - Enable last updated timestamps and SEO optimization (built-in) - Verify light/dark/system theme modes work correctly (built-in) - Test Pagefind search functionality (built-in) All Starlight built-in features are now properly configured: - Sidebar navigation with Getting Started, Authentication Providers, Cache Providers, and Guides sections - Auto-generation for providers and cache directories - GitHub social link and edit links - Last updated timestamps enabled - Pagefind search functionality working (9 pages indexed) - Light/dark/system theme modes (built-in) - SEO optimization (built-in) - Responsive design (built-in)
Task: 6.5 Enhance documentation with Starlight features - Added comprehensive Mermaid diagrams for architecture and flow documentation - Enhanced cross-references and internal linking between pages - Added extensive YAML configuration examples for different providers and deployments - Removed code snippets except for YAML configurations as required - Verified full-text search functionality works (Pagefind indexed 1674 words) - Confirmed light/dark/system theme modes and responsive design work (built-in) - Enhanced all major documentation pages with better organization and navigation Key improvements: - Main index page: Enhanced architecture diagrams and quick start guide - Concepts page: Added detailed system architecture and configuration examples - OIDC provider: Comprehensive provider-specific YAML configurations - Authelia provider: Production-ready configuration examples - Redis cache: Enterprise deployment configurations - Troubleshooting: Advanced diagnostic flows and solutions All Starlight features are working correctly including search, themes, and Mermaid diagrams.
- Create GitHub Actions workflow for deploying Starlight documentation - Configure workflow to use Node.js 24 with npm for build process - Set up proper GitHub Pages permissions and deployment configuration - Update Astro config to use environment variables for site/base URLs - Test build process locally to ensure functionality Task: 6.7 Set up GitHub Pages deployment workflow Requirements: 17.7
…pi integration - Install starlight-openapi package for interactive API documentation - Copy OpenAPI specification to docs/src/schemas/openapi.yaml - Configure starlight-openapi plugin in astro.config.mjs with API Reference section - Add comprehensive documentation links in OpenAPI spec with correct base paths - Fix all internal links across documentation to include /elastauth base path - Generate interactive API documentation pages for all endpoints - Maintain existing OpenAPI specification functionality - Add cross-references between API docs and provider documentation Task: 6.9 Migrate OpenAPI specification to Starlight
- Remove duplicate H1 titles from all documentation content files - Keep titles only in frontmatter for automatic Starlight rendering - Fix internal links in providers index page to include /elastauth base path - Maintain consistent title structure across all documentation pages - OpenAPI pages already have proper titles without duplication This eliminates the duplicate title issue where each page showed the title twice: once from the frontmatter (in menu and page header) and once as markdown H1.
- Remove docs-backup/ directory (migration to Starlight complete) - Remove old documentation files that were moved to Starlight structure: - docs/cache/, docs/concepts.md, docs/providers/, docs/troubleshooting.md, docs/upgrading.md - docs/openapi.yaml, docs/examples/ - Remove build artifacts: docs/dist/, docs/.astro/, docs/node_modules/.astro/ - Remove unused kibana-auth-proxy.png file - Mark task 6.9 as completed in tasks.md All documentation has been successfully migrated to the new Starlight structure with interactive OpenAPI documentation and proper internal linking.
- Remove accidentally committed docs/.git directory - Clean up repository structure - Maintain all documentation functionality
- Add installation section with git clone options - Recommend shallow clone (--depth 1) for faster downloads - Document repository size issue with historical node_modules - Provide both quick and full clone options for users
renovate
bot
force-pushed
the
renovate/github.com-redis-go-redis-v9-9.x
branch
from
99bf7e6 to
4989a65
Compare
- Add period to description to force new deployment - Previous deployment was stuck in queue for 8+ minutes
renovate
bot
force-pushed
the
renovate/github.com-redis-go-redis-v9-9.x
branch
from
4989a65 to
35ec3e8
Compare
- Update deployment condition to allow both push to main AND workflow_dispatch - Enables manual triggering of documentation deployments via GitHub UI - Useful for troubleshooting stuck deployments or deploying without code changes - Based on GitHub Actions best practices from Context7 research
renovate
bot
force-pushed
the
renovate/github.com-redis-go-redis-v9-9.x
branch
from
35ec3e8 to
9dbab84
Compare
- Removed excessive Redis, Elasticsearch, and infrastructure setup information - Focused documentation on elastauth configuration and usage - Cleaned up cache documentation to remove Redis administration details - Simplified provider documentation to focus on elastauth integration - Streamlined troubleshooting guide to elastauth-specific issues - Removed deployment guides and external system management information - Maintained only elastauth configuration examples and usage patterns The documentation now focuses on what users need to know about elastauth itself rather than general infrastructure management.
renovate
bot
force-pushed
the
renovate/github.com-redis-go-redis-v9-9.x
branch
from
9dbab84 to
4a92517
Compare
renovate
bot
changed the title
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/github.com-redis-go-redis-v9-9.x
branch
from
cff2ebf to
4a92517
Compare
Contributor
Author
Edited/Blocked NotificationRenovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR. You can manually request rebase by checking the rebase/retry box above. |
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.
This PR contains the following updates:
v9.17.1→v9.17.2Release Notes
redis/go-redis (github.com/redis/go-redis/v9)
v9.17.2: 9.17.2Compare Source
🐛 Bug Fixes
🧰 Maintenance
Contributors
We'd like to thank all the contributors who worked on this release!
@cyningsun and @ndyakov
Configuration
📅 Schedule: Branch creation - Between 12:00 AM and 03:59 AM ( * 0-3 * * * ) (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.