fix(changelog): Fix 404 on /changelog/ page and add navigation#17182
fix(changelog): Fix 404 on /changelog/ page and add navigation#17182
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
Autofix Details
Bugbot Autofix prepared a fix for the issue found in the latest run.
- ✅ Fixed: File filter condition is too permissive using OR
- Changed filter logic from OR to AND, requiring files to both start with docs/ and match .mdx extension, consistent with getPageTitle and fileToUrl functions.
Or push these changes by commenting:
@cursor push c32dcdac49
Preview (c32dcdac49)
diff --git a/scripts/update-docs-changelog.mjs b/scripts/update-docs-changelog.mjs
--- a/scripts/update-docs-changelog.mjs
+++ b/scripts/update-docs-changelog.mjs
@@ -189,7 +189,7 @@
for (const file of files) {
// Only include doc files
- if (!file.filename.match(/\.(mdx?|tsx?)$/) && !file.filename.startsWith('docs/')) {
+ if (!file.filename.startsWith('docs/') || !file.filename.match(/\.mdx?$/)) {
continue;
}This Bugbot Autofix run was free. To enable autofix for future PRs, go to the Cursor dashboard.
864ace0 to
0b3aed9
Compare
|
@sfanahata lots of unrelated changes to backlog (formatting, etc) - do you know why these are ending up here? |
sergical
left a comment
There was a problem hiding this comment.
something is telling me a daily cron that checks all PRs and scans files and parses all of that isn't the right solution here. I might be wrong, but have we considered just doing a standard Changelog.md that can be fetched on the changelog page and rendered nicely as markdown (or even consumed directly using mdx).
Wondering what decision caused us to pursue this route. I am not 100% against it but I am not 100% aligned either 😅
Good catch. This was implemented so I could test the formatting locally. I didn't realize it was bloating the PR. I removed it. Oh, and a rebase pulled all the commits in. 🤦 |
0ec1900 to
49c21fb
Compare
I was exploring still having the changelog accessible to other services (via API), but I don't think we need that anymore. I've had the solution rewritten to your recommendation. Seems to still look good. Will ping you when it's ready for re-review. |
49c21fb to
08ae106
Compare
08ae106 to
26e69bc
Compare
- Add /changelog/ page showing recent documentation updates - Add GitHub Action to fetch merged PRs and generate changelog - Generate MDX include file with links to actual doc pages - Add 'Docs Changelog' to navigation dropdown - Rename existing 'Changelog' links to 'Product Changelog' The workflow runs daily and creates PRs to update the changelog with recently merged documentation changes.
26e69bc to
e75dff2
Compare
8697132 to
efcfb19
Compare
efcfb19 to
aee0926
Compare
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
|
@sfanahata looks good! Is there a way to make it a little more human-readable? The previous version was providing brief LLM-generated summaries describing the changes in the PR, I felt like that was valuable. |


Preview: https://sentry-docs-git-fix-changelog-404.sentry.dev/changelog/
IS YOUR CHANGE URGENT?
Help us prioritize incoming PRs by letting us know when the change needs to go live.
SLA
Thanks in advance for your help!
PRE-MERGE CHECKLIST
Make sure you've checked the following before merging your changes: