Repository navigation
Start release notes for 8.1.0 - #4681
Conversation
Running docs/release-notes/<version>.md file, appended in the same PR as any user-visible behavior change, so notes are written at merge time instead of reconstructed at release time. Seeded with the #4675 key pre-processor entry.
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 5057e94b2b
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
|
|
||
| ... | ||
|
|
||
| ## Behavior Changes |
There was a problem hiding this comment.
Because this page is the running 8.1.0 notes, it also needs to mention the other user-visible behavior from #4675: FTSearchParams.params(Map) now merges/overwrites existing PARAMS after addParam() or prior params() calls instead of effectively ignoring the later map. Without an entry here, users upgrading from 8.0.0 won't know why FT.SEARCH queries built with mixed params can start returning different results; please add a Behavior Changes item for that fix.
AGENTS.md reference: AGENTS.md:L10-L10
Useful? React with 👍 / 👎.
Reviewers couldn't tell which versions the notes cover. Add a Full Changelog compare link (v8.0.0...master until the tag exists) and fold the link flip into the release-time step.
The compare link needed a manual update at release time; a plain sentence states the covered upgrade without maintenance.
ggivo
added
maintenance
churn
Adds a running
docs/release-notes/<version>.mdfile, appended in the same PR as any user-visible behavior change, so notes are written at merge time instead of reconstructed at release time. Includes the mkdocs nav entry and an AGENTS.md rule making it part of the contribution conventions.Seeded with the #4675 key pre-processor entry. The page carries an "Unreleased" notice until 8.1.0 ships; removing it is part of the release.
Note
Low Risk
Documentation and contributor-process updates only; no runtime or API changes in this diff.
Overview
Introduces a running release-notes workflow for the next version: contributors add user-visible behavior changes to
docs/release-notes/8.1.0.mdin the same PR instead of writing notes at release time.AGENTS.md now requires that non-breaking behavior changes get an entry under
docs/release-notes/, and MkDocs adds a Release Notes → 8.1.0 nav item. The new page is marked Unreleased until 8.1.0 ships and includes a Behavior Changes template plus the first entry for #4675 (key pre-processor coverage forZRANGESTORE/GEOSEARCHSTOREsource keys andeval/evalshascript keys, with upgrade actions for double-prefix workarounds and CROSSSLOT exception handling).Reviewed by Cursor Bugbot for commit 0cd271f. Bugbot is set up for automated code reviews on this repo. Configure here.