# Updates {% embed url="" %} Changelog Demo {% endembed %} ## Overview A Changelog is a document that contains a curated, chronologically ordered list of notable changes for each version of a project or product. Changelogs are used to communicate updates with internal stakeholders or customers. Released Changelogs make it easy to craft updates. Curate a list of issues related to a release in just a couple of clicks. Then let the AI copywriter transform your issue descriptions into a language that your target audience understands. ## Use-cases Use the Changelog to communicate detail technical changes or high level marketing updates. What you want to communicate and how you communicate will determine the format and frequency. Some teams write multiple posts a day, each containing a single improvement. Other teams write a post once a week, summarizing all improvements and bug-fixes in one Post. The Changelog is often used for: * Internal sprint summaries * Technical changelogs * Release notes * Marketing updates * Announcements * And many more... You can use [filters](/guide/product/changelog/staging-area.md) to only includes issues that are relevant and customize the [AI settings](/guide/product/changelog/settings/artificial-intelligence.md) to tailor the prompt to your use-case. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.released.so/guide/product/changelog.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.