ข้ามไปยังเนื้อหา
การนำทางเอกสาร

เริ่มที่นี่

ผลิตภัณฑ์

การเชื่อมต่อ

SDK

MCP

Publishing a changelog

Create a draft

Open Changelog in the app and create an entry. Give the update a clear title and body, then save it as a draft while you prepare it. Titles are limited to 140 characters and bodies to 50,000 characters. A draft is not a public update.

Format an update

Use Markdown for paragraphs, headings, lists, emphasis, links, blockquotes, code, and tables. Preview the result before publishing. Raw HTML is not a way to add scripts or arbitrary styling; unsupported markup and attributes are removed from the public output.

Associate relevant feedback with the entry so readers can connect the update to requests. Explain the outcome in the body as well as linking the request. A changelog entry and a feedback status are separate records: review both when communicating shipped work.

Publish and share

Publish when the update is ready for customers. Only published entries have public post URLs. An illustrative address is https://upweight.dev/WORKSPACE/changelog/POST. Copy the actual published URL from your workspace and verify it before sharing.

Shipped-update emails are a separate capability; do not assume publishing an entry sends an email to every voter.

Workspace updates and Upweight updates

Your workspace changelog describes your product. Upweight updates describe changes to Upweight itself. Keep those destinations distinct when sharing a release announcement. See Roadmap for the workspace planning view.

ตรวจสอบล่าสุด