Some checks failed
Deploy MineGeo to Dokploy / deploy (push) Failing after 3m40s
24 lines
1.5 KiB
Markdown
24 lines
1.5 KiB
Markdown
# Release changelogs
|
|
|
|
`/changelogs` reads messages from MineGeo's `___news___` channel (`1558048830770122772`).
|
|
Only release posts from webhook ID `1561021045211660401` appear. The bot only reads
|
|
message history using GET; this feature never sends, edits, or deletes Discord messages.
|
|
The webhook URL and its secret token are not needed or stored by the reader.
|
|
|
|
Use the existing server-only `DISCORD_BOT_TOKEN` with View Channel and Read Message
|
|
History in news. Enable Message Content Intent in Discord Developer Portal → Bot;
|
|
otherwise Discord redacts the webhook messages' text. Optional `DISCORD_NEWS_CHANNEL_ID` and `DISCORD_RELEASE_WEBHOOK_ID`
|
|
override the defaults. Never prefix these variables with `NEXT_PUBLIC_`.
|
|
|
|
The feed accepts `## MineGeo 1.0.4 Alpha`, `Beta`, `Production`, and four-part
|
|
`Bug fix` headings. It removes role mentions, leading separators, and the trailing
|
|
`PLAY THE MINEGEO AT:` footer. React safely renders paragraphs, bullet lists, bold,
|
|
inline code, and HTTP(S) links; raw HTML cannot execute.
|
|
|
|
Discord history is cached for 60 seconds. The latest page refreshes every 65 seconds
|
|
while visible. Each page scans 100 Discord messages; Older posts continues through
|
|
history even when a page contains only tournament announcements. Edited and deleted
|
|
release posts are reflected after revalidation. If credentials or history permissions
|
|
are unavailable, the page displays a temporary-unavailability state, without exposing
|
|
Discord errors or credentials. There is no database migration for changelogs.
|