docs(waf): note that beta tag may persist beyond the 7-day review period#31984
Open
zeinjaber wants to merge 1 commit into
Open
docs(waf): note that beta tag may persist beyond the 7-day review period#31984zeinjaber wants to merge 1 commit into
zeinjaber wants to merge 1 commit into
Conversation
zeinjaber
requested review from
a team,
ay-cf,
danielegm,
elithrar,
hsaxenaCF and
vs-mg
as code owners
Contributor
Review
Fix in your agentFix the following review findings in PR #31984 (https://github.com/cloudflare/cloudflare-docs/pull/31984).
Before making changes, review each finding and present a brief summary table:
- For each finding, state whether you agree, disagree, or need clarification
- If you disagree (e.g. the fix requires disproportionate effort for minimal benefit,
or the finding is factually incorrect), explain why
- If you need clarification before deciding, ask those questions
- Then share your plan for which issues to tackle and in what order
After triaging, fix all legitimate findings. For any you decide to skip,
post a comment on this PR with the finding ID and your reasoning.
---
## Code Review
### Warnings (1)
#### CR-45e6324a0d50 · Reference to non-existent changelog field
- **File:** `src/content/docs/waf/change-log/index.mdx` line 41
- **Issue:** The added note tells readers to use the `last_updated` field in the WAF changelog, but the WAF changelog entries in the repository (e.g., `src/content/changelog/waf/2026-06-23-waf-release.mdx`) and the page component (`src/pages/waf/change-log/changelog/[...page].astro`) expose only the entry date and rule/action tables; no `last_updated` field is rendered.
- **Fix:** Confirm with the WAF team whether `last_updated` is actually exposed to readers in the changelog. If it is not, reword the note to reference the entry date shown on the changelog or another available signal.
Code ReviewThis code review is in beta and may not always be helpful — use your judgment. Warnings (1)
ConventionsNo convention issues found. Style Guide ReviewNo style-guide issues found. CommandsOnly codeowners can run commands. Post a comment with the command to trigger it.
|
Contributor
|
This pull request requires reviews from CODEOWNERS as it changes files that match the following patterns:
|
Contributor
|
Preview URL: https://ca5844a4.preview.developers.cloudflare.com Files with changes (up to 15)
|
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
6 participants
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.
What
Adds a note in the Release cycle section of the WAF changelog page clarifying that the
betatag may persist beyond the standard seven-day review period in certain scenarios, and advising customers to uselast_updatedto understand a rule's actual modification history.Why
The current docs present the 7-day beta-to-GA cycle as absolute. In practice, replacement rules pending the deprecation of an older rule can carry the
betatag for significantly longer. Customers who find rules taggedbetawithaction=blockand oldlast_updatedtimestamps have no public explanation for this behavior, leading to confusion and support escalations.Files changed
src/content/docs/waf/change-log/index.mdx— note block after the Week 2 paragraph in the Release cycle section (+4 lines)How to verify
Navigate to /waf/change-log/ and confirm the note appears between the Week 2 paragraph and the "For updates to existing rules" paragraph.
Closes DEE-3698