Add release changelog for v1.1.0 - #422
Conversation
Signed-off-by: ravjotb <ravjot.brar@improving.com>
Signed-off-by: ravjotb <ravjot.brar@improving.com>
Signed-off-by: ravjotb <ravjot.brar@improving.com>
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughThe documentation site adds Valkey Admin v1.1.0 release notes dated July 2026. It updates navigation, homepage content, and Docker release references. The introduction page is removed. ChangesDocumentation site update
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🧹 Nitpick comments (1)
docs-site/src/content/docs/releases.md (1)
40-42: 🔒 Security & Privacy | 🔵 Trivial | ⚡ Quick winAdd traceability to the security updates.
The dependency update does not identify the affected package, fixed version, advisory, or change reference. The CI permission change also has no pull request reference. Add these details so users can assess the scope of the security changes.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@docs-site/src/content/docs/releases.md` around lines 40 - 42, Update the release-note entries in the releases content so the vulnerable dependency update names the affected package, fixed version, relevant advisory, and pull request or change reference. Also add the corresponding pull request reference to the CI workflow permissions entry, preserving the existing release-note format.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@docs-site/src/content/docs/releases.md`:
- Line 60: Update the Full Changelog link in the release entry to compare v1.0.1
against the v1.1.0 tag, matching the release heading; use release/1.1.0 only if
the page explicitly documents that branch.
---
Nitpick comments:
In `@docs-site/src/content/docs/releases.md`:
- Around line 40-42: Update the release-note entries in the releases content so
the vulnerable dependency update names the affected package, fixed version,
relevant advisory, and pull request or change reference. Also add the
corresponding pull request reference to the CI workflow permissions entry,
preserving the existing release-note format.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro Plus
Run ID: 841eeaa5-1808-42a8-b294-499216da1d73
📒 Files selected for processing (1)
docs-site/src/content/docs/releases.md
|
|
||
| @ravjotbrar, @ArgusLi, @nassery318, @dbaker-arch, @michaelstingl, @antonin-suzor | ||
|
|
||
| **Full Changelog**: [v1.0.1...v1.1.0](https://github.com/valkey-io/valkey-admin/compare/v1.0.1...release/1.1.0) |
There was a problem hiding this comment.
🗄️ Data Integrity & Integration | 🟡 Minor | ⚡ Quick win
🧩 Analysis chain
🏁 Script executed:
#!/usr/bin/env bash
set -euo pipefail
repo='https://github.com/valkey-io/valkey-admin.git'
git ls-remote --exit-code --tags "$repo" 'refs/tags/v1.0.1*' >/dev/null
git ls-remote --exit-code --tags "$repo" 'refs/tags/v1.1.0*' >/dev/null
git ls-remote --exit-code --heads "$repo" 'refs/heads/release/1.1.0' >/dev/null
gh api repos/valkey-io/valkey-admin/compare/v1.0.1...v1.1.0 \
--jq '{status, ahead_by, behind_by}'
gh api repos/valkey-io/valkey-admin/compare/v1.0.1...release/1.1.0 \
--jq '{status, ahead_by, behind_by}'Repository: valkey-io/valkey-admin
Length of output: 160
🏁 Script executed:
#!/usr/bin/env bash
set -euo pipefail
repo='https://github.com/valkey-io/valkey-admin.git'
printf 'Tags:\n'
git ls-remote --tags "$repo" | rg '(refs/tags/v1\.0\.1|refs/tags/v1\.1\.0|release/1\.1\.0)$' || true
printf '\nBranches:\n'
git ls-remote --heads "$repo" | rg 'refs/heads/(release/1\.1\.0|release-1\.1\.0|v1\.1\.0.*|.*1\.1\.0.*)$' || true
printf '\nCommit objects for refs (no resolve):\n'
for ref in refs/tags/v1.0.1 refs/tags/v1.1.0 refs/heads/release/1.1.0; do
git ls-remote "$repo" "$ref" || true
doneRepository: valkey-io/valkey-admin
Length of output: 464
🌐 Web query:
valkey-io valkey-admin v1.1.0 branch release/1.1.0
💡 Result:
As of July 31, 2026, there is no v1.1.0 release or branch for valkey-admin in the official valkey-io/valkey-admin repository [1][2]. The most recent stable version is v1.0.1, which was released on May 6, 2026 [3]. Development continues under the repository's main branch, but a release/1.1.0 branch has not been established [1][2].
Citations:
- 1: https://github.com/valkey-io/valkey-admin/releases
- 2: https://github.com/valkey-io/valkey-admin
- 3: https://github.com/valkey-io/valkey-admin/releases/tag/v1.0.1
🏁 Script executed:
#!/usr/bin/env bash
set -euo pipefail
printf 'docs-site/src/content/docs/releases.md around Line 60:\n'
sed -n '50,68p' docs-site/src/content/docs/releases.md | cat -n -v
printf '\nAll v1.1.0/release/1.1.0 references:\n'
rg -n "v1\.1\.0|release/1\.1\.0" docs-site/src/content/docs/releases.md docs-site -S || true
printf '\nRepository remote refs for v1.1.0 and release/1.1.0 (full):\n'
git ls-remote --tags https://github.com/valkey-io/valkey-admin.git | rg '(^|)[[:xdigit:]]{40}\s+refs/tags/v1\.1\.0|refs/tags/v1\.1\.0.*$' || true
git ls-remote --tags https://github.com/valkey-io/valkey-admin.git | rg 'v1\.1\.0' || true
git ls-remote --heads https://github.com/valkey-io/valkey-admin.git | rg 'release/1\.1\.0|v1\.1\.0' || true
printf '\nLocal git ref status:\n'
git status -sb
git rev-parse --verify v1.1.0 2>/dev/null || true
git rev-parse --verify release/1.1.0 2>/dev/null || trueRepository: valkey-io/valkey-admin
Length of output: 2338
Fix the mismatched changelog link.
Full Changelog links to v1.0.1...release/1.1.0, while the release entry uses v1.1.0. Use v1.0.1...v1.1.0; only use release/1.1.0 if this page documents that branch instead of the release tag.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@docs-site/src/content/docs/releases.md` at line 60, Update the Full Changelog
link in the release entry to compare v1.0.1 against the v1.1.0 tag, matching the
release heading; use release/1.1.0 only if the page explicitly documents that
branch.
Signed-off-by: ravjotb <ravjot.brar@improving.com>
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@docs-site/src/content/docs/index.mdx`:
- Around line 46-48: Update the Big Keys Analysis Card description in
docs-site/src/content/docs/index.mdx lines 46-48 to state that access-frequency
insights require an LFU eviction policy, and make the same documentation change
in the Activity card at lines 95-99.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro Plus
Run ID: 78214f6d-95a4-49a2-b550-44f8ec8ca89d
⛔ Files ignored due to path filters (2)
docs-site/package-lock.jsonis excluded by!**/package-lock.jsondocs-site/src/assets/monitoring_big_keys.pngis excluded by!**/*.png
📒 Files selected for processing (4)
docs-site/astro.config.mjsdocs-site/src/content/docs/index.mdxdocs-site/src/content/docs/introduction.mdxdocs-site/src/content/docs/releases.md
💤 Files with no reviewable changes (1)
- docs-site/src/content/docs/introduction.mdx
🚧 Files skipped from review as they are similar to previous changes (1)
- docs-site/src/content/docs/releases.md
| <Card title="Big Keys Analysis" icon="magnifier"> | ||
| Scan the keyspace to find the largest keys by memory usage with access frequency insights. | ||
| </Card> |
There was a problem hiding this comment.
🎯 Functional Correctness | 🟡 Minor | ⚡ Quick win
Document the conditional access-frequency behavior in both cards.
docs-site/src/content/docs/releases.md limits OBJECT FREQ access-frequency data to servers using an LFU eviction policy. Both homepage descriptions omit this condition.
docs-site/src/content/docs/index.mdx#L46-L48: state that access-frequency insights require an LFU eviction policy.docs-site/src/content/docs/index.mdx#L95-L99: state the same prerequisite in the Activity card.
📍 Affects 1 file
docs-site/src/content/docs/index.mdx#L46-L48(this comment)docs-site/src/content/docs/index.mdx#L95-L99
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@docs-site/src/content/docs/index.mdx` around lines 46 - 48, Update the Big
Keys Analysis Card description in docs-site/src/content/docs/index.mdx lines
46-48 to state that access-frequency insights require an LFU eviction policy,
and make the same documentation change in the Activity card at lines 95-99.
Signed-off-by: ravjotb <ravjot.brar@improving.com>
2 participants
No description provided.