EPMRPP-116936 || Docs sitemap: Add <lastmod> tag for the last release URL

[maria-hambardzumian]

Summary by CodeRabbit

• Chores

  • Updated release documentation metadata to include accurate last update dates for release pages.

• Documentation

  • Release pages now display last update timestamps in search results and sitemaps.

[coderabbitai]

Warning

Review limit reached

@maria-hambardzumian, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 47 minutes and 35 seconds. Learn how PR review limits work.

Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file).

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based credits.

🚦 How do rate limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan refill rate.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, the refill rate gradually slows as usage increases. The highest same-day bursts are limited more strictly.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: c98b3331-3e9f-4b10-8c50-40c865a16d10

📥 Commits

Reviewing files that changed from the base of the PR and between 28feacb and d79b4d1.

📒 Files selected for processing (1)

• docusaurus.config.js

Walkthrough

Three release markdown files receive last_update.date frontmatter entries. The release generation script gains a toDateOnly helper and conditionally writes last_update from GitHub timestamps. The Docusaurus config adds gray-matter-based parsing of those dates and uses them to set lastmod in generated sitemap items.

Changes

Release lastmod sitemap pipeline

Layer / File(s)	Summary
Release script: auto-emit last_update frontmatter scripts/update-release.js	Adds toDateOnly helper converting a GitHub timestamp to YYYY-MM-DD, and extends front matter writing to conditionally append a last_update block using published_at or created_at.
Docusaurus config: sitemap lastmod from release dates docusaurus.config.js	Imports fs, path, gray-matter; adds readReleaseLastmodDates that builds a version→ISO-date map from docs/releases frontmatter; updates createSitemapItems to normalize URLs and populate lastmod for matched release pages.
Release doc frontmatter updates docs/releases/Version26.0.1.md, docs/releases/Version26.0.2.md, docs/releases/Version26.0.3.md	Sets last_update.date to 2026-02-16, 2026-03-12, and 2026-05-29 respectively in the three release pages.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

• reportportal/docs#1123: Directly overlaps — that PR created docs/releases/Version26.0.3.md, which this PR now updates with last_update.date frontmatter.

Suggested reviewers

• pressayuliya
• siarheirazuvalau

Poem

🐰 Hop, hop, a date in the front!
Each release now timestamps its stunt.
The sitemap knows when pages were born,
No lastmod shall be left forlorn.
Fresh dates for every version — what fun! 🗓️

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The PR title accurately describes the main objective: adding tags to release URLs in the documentation sitemap.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch feature/EPMRPP-116936-Docs-sitemap--Add-<lastmod>-tag-for-the-last-release-URL

---

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

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 `@docusaurus.config.js`:
- Around line 85-87: In the sitemap generation logic around the lastmod
assignment, the current code sets lastmod to undefined for non-release pages,
which overwrites the existing lastmod values that were already set by
defaultCreateSitemapItems. Modify the lastmod assignment in the return statement
to preserve the existing lastmod value from the item object when there is no
release match, instead of setting it to undefined. This way, release pages will
use the specific lastmod from releaseLastmod while non-release pages retain
their original lastmod values.

🪄 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

Run ID: 26e9ae3a-4ab8-4738-8cd1-84037653817c

📥 Commits

Reviewing files that changed from the base of the PR and between 08adf3f and 28feacb.

📒 Files selected for processing (5)

• docs/releases/Version26.0.1.md
• docs/releases/Version26.0.2.md
• docs/releases/Version26.0.3.md
• docusaurus.config.js
• scripts/update-release.js

[maria-hambardzumian]

https://jiraeu.epam.com/browse/EPMRPP-116936