--- title: "[Create and Manage Releases] - About Releases" description: About Releases url: https://www.contentstack.com/docs/content-managers/create-and-manage-releases/about-releases product: Contentstack doc_type: concept audience: - content-managers version: unknown last_updated: 2026-03-25 --- # [Create and Manage Releases] - About Releases This page explains what Releases are in Contentstack and how they help content managers deploy (publish or unpublish) multiple entries and assets together to a chosen environment, especially for time-sensitive or large-scale content updates. ## About Releases You can define a “Release” as a set of [entries](https://www.contentstack.com/docs/content-managers/working-with-entries/about-entries/) and [assets](https://www.contentstack.com/docs/content-managers/working-with-assets/about-assets/) that needs to be deployed ([published](https://www.contentstack.com/docs/content-managers/working-with-entries/publish-an-entry/) or [unpublished](https://www.contentstack.com/docs/content-managers/working-with-entries/unpublish-an-entry/)) all at once to a particular [environment](https://www.contentstack.com/docs/developers/set-up-environments/about-environments/). **Note:** When working within specific branches, releases created will be specific to that particular branch. Refer to our [Branch-specific Modules](/docs/developers/branches/branch-specific-modules) document for more information. If you are using a CMS to manage and publish your content, you know that publishing large amounts of time-sensitive content (for example, when there’s a product launch, press release, or sales promotion) is a daunting task. You have to publish multiple entries/assets and their publishing status, and, in most cases, you have to find and keep track of the content pieces one by one. This is a time-consuming process and is prone to errors. Releases dramatically simplify this task for you. All you need to do is simply pin all the required entries and assets to a “Release.” When you deploy this Release, all the pinned items are published/unpublished at the same time to whatever environment you choose. **Note:** To use Releases with web framework, you will need contentstack-express version 3.1.9 or above. To understand more about Releases, make sure you read the articles provided in our “More articles” section ## Common questions ### What is a Release used for? A “Release” is used to deploy (published or unpublished) a set of entries and assets all at once to a particular environment. ### Can Releases be branch-specific? Yes. When working within specific branches, releases created will be specific to that particular branch. ### What happens when I deploy a Release? When you deploy a Release, all the pinned items are published/unpublished at the same time to whatever environment you choose. ### Is there a version requirement to use Releases with a web framework? Yes. To use Releases with web framework, you will need contentstack-express version 3.1.9 or above.