Update generate_changelog.py

[amyblais]

A quick fix for changelog automation to update the blog post link.

[coderabbitai]

📝 Walkthrough

Walkthrough

The changelog generator now asks AI-polished output to use BLOG_POST_LINK and replaces that placeholder with a generated Markdown blog link when no blog URL is provided.

Changes

Changelog blog link handling

Layer / File(s)	Summary
Prompt and fallback link rendering .github/scripts/generate_changelog.py	The improvements prompt uses BLOG_POST_LINK; fallback URL generation strips the final numeric patch segment from the version slug and substitutes the placeholder with a Markdown link.

Estimated code review effort: 2 (Simple) | ~10 minutes

Possibly related PRs

• mattermost/docs#9091: Updates the same changelog script’s prompt and blog-link rendering logic.

Suggested labels: 1: Dev Review

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
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.
Title check	✅ Passed	The title is related to the change, though broad; it still points to the file that was updated.
Description check	✅ Passed	The description matches the changelog blog-link fix described in the diff.

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch amyblais-changelogfix

---

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.}

[coderabbitai]

🧹 Nitpick comments (1)

.github/scripts/generate_changelog.py (1)

75-75: 📐 Maintainability & Code Quality | 🔵 Trivial | 💤 Low value

Improve the grammar in the generated sentence.

The phrase "on the highlights" in the system prompt isn't very idiomatic. Consider changing it to "for the highlights" to make the resulting changelog read more naturally.

♻️ Proposed fix

-    - `### Improvements` — for new features and enhancements only. Do NOT place items beginning with "Fixed..." here — those belong in Bug Fixes. Begin this section with the line `See BLOG_POST_LINK on the highlights in our latest release.` (use the exact placeholder `BLOG_POST_LINK` — it will be replaced automatically with a Markdown link), followed by a blank line before the first `####` subsection heading. Then add subsections as applicable:
+    - `### Improvements` — for new features and enhancements only. Do NOT place items beginning with "Fixed..." here — those belong in Bug Fixes. Begin this section with the line `See BLOG_POST_LINK for the highlights in our latest release.` (use the exact placeholder `BLOG_POST_LINK` — it will be replaced automatically with a Markdown link), followed by a blank line before the first `####` subsection heading. Then add subsections as applicable:

🤖 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 @.github/scripts/generate_changelog.py at line 75, Update the Improvements
section instruction in the changelog generation prompt to use “for the
highlights” instead of “on the highlights,” while preserving the exact
BLOG_POST_LINK placeholder and surrounding formatting requirements.

🤖 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.

Nitpick comments:
In @.github/scripts/generate_changelog.py:
- Line 75: Update the Improvements section instruction in the changelog
generation prompt to use “for the highlights” instead of “on the highlights,”
while preserving the exact BLOG_POST_LINK placeholder and surrounding formatting
requirements.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 3d9a17f0-9ab9-44d9-8060-f24418405abf

📥 Commits

Reviewing files that changed from the base of the PR and between 7347959 and b8dd8f2.

📒 Files selected for processing (1)

• .github/scripts/generate_changelog.py

[Copilot]

Pull request overview

Updates the changelog generation script used in the Mattermost docs automation to change how the “Improvements” section references the release highlights blog post, including switching from a raw URL placeholder to a Markdown-link placeholder.

Changes:

• Updates the AI/system prompt to use a BLOG_POST_LINK placeholder in the Improvements intro line.
• Updates blog URL construction logic to remove a trailing -0 from the version slug and inject a Markdown-formatted link into the generated changelog text.

[github-actions]

Newest code from mattermost has been published to preview environment for Git SHA b8dd8f2

[github-actions]

Newest code from mattermost has been published to preview environment for Git SHA bed36f1

[github-actions]

Newest code from mattermost has been published to preview environment for Git SHA a033b8b