diff --git a/CHANGELOG.md b/CHANGELOG.md
index d312eab22a..601dd737ba 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -1,5 +1,27 @@
 
 
+## [0.410.0] - September 10, 2024
+
+### Added
+  - DP-34207: Added posibility to skip GIF image derivative generation if image is animated gif
+  - DP-34675: Add Urdu language
+  - DP-34727: Flag to Show/Hide Feedback form on Topic Page, for users with 'create topic_page content' permission.
+  - DP-34727: Flag to make optional organization field on Topic Page edit form, for users with 'create topic_page content' permission.
+  
+### Fixed
+  - DP-34424: Fixed the issue with styles in rich text related to images.
+  - DP-34678: Empty table being added to rules of court pages with no dates.
+  - DP-34797: 500 Error on https://edit.mass.gov/guides/massachusetts-energy-rebates-incentives
+  
+### Security
+  - DP-34468: Resolve dependabot issues.
+  
+### Changed
+  - DP-34515: Email validation in the feedback component.
+  - DP-34568: Don't show authors and editors the text format options.
+  
+
+
 ## [0.409.0] - September 3, 2024
 
 ### Fixed
diff --git a/changelogs/DP-34207.yml b/changelogs/DP-34207.yml
deleted file mode 100644
index 3a284b7cf0..0000000000
--- a/changelogs/DP-34207.yml
+++ /dev/null
@@ -1,41 +0,0 @@
-#
-# Write your changelog entry here. Every pull request must have a changelog yml file.
-#
-# Change types:
-# #############################################################################
-# You can use one of the following types:
-#  - Added: For new features.
-#  - Changed: For changes to existing functionality.
-#  - Deprecated: For soon-to-be removed features.
-#  - Removed: For removed features.
-#  - Fixed: For any bug fixes.
-#  - Security: In case of vulnerabilities.
-#
-# Format
-# #############################################################################
-# The format is crucial. Please follow the examples below. For reference, the requirements are:
-#  - All 3 parts are required and you must include "Type", "description" and "issue".
-#  - "Type" must be left aligned and followed by a colon.
-#  - "description" must be indented with 2 spaces followed by a colon
-#  - "issue" must be indented with 4 spaces followed by a colon.
-#  - "issue" is for the Jira ticket number only e.g. DP-1234
-#  - No extra spaces, indents, or blank lines are allowed.
-#
-# Example:
-# #############################################################################
-# Fixed:
-#  - description: Fixes scrolling on edit pages in Safari.
-#    issue: DP-13314
-#
-# You may add more than 1 description & issue for each type using the following format:
-# Changed:
-#  - description: Automating the release branch.
-#    issue: DP-10166
-#  - description: Second change item that needs a description.
-#    issue: DP-19875
-#  - description: Third change item that needs a description along with an issue.
-#    issue: DP-19843
-#
-Added:
-  - description: Added posibility to skip GIF image derivative generation if image is animated gif
-    issue: DP-34207
diff --git a/changelogs/DP-34424.yml b/changelogs/DP-34424.yml
deleted file mode 100644
index adc54992c8..0000000000
--- a/changelogs/DP-34424.yml
+++ /dev/null
@@ -1,41 +0,0 @@
-#
-# Write your changelog entry here. Every pull request must have a changelog yml file.
-#
-# Change types:
-# #############################################################################
-# You can use one of the following types:
-#  - Added: For new features.
-#  - Changed: For changes to existing functionality.
-#  - Deprecated: For soon-to-be removed features.
-#  - Removed: For removed features.
-#  - Fixed: For any bug fixes.
-#  - Security: In case of vulnerabilities.
-#
-# Format
-# #############################################################################
-# The format is crucial. Please follow the examples below. For reference, the requirements are:
-#  - All 3 parts are required and you must include "Type", "description" and "issue".
-#  - "Type" must be left aligned and followed by a colon.
-#  - "description" must be indented with 2 spaces followed by a colon
-#  - "issue" must be indented with 4 spaces followed by a colon.
-#  - "issue" is for the Jira ticket number only e.g. DP-1234
-#  - No extra spaces, indents, or blank lines are allowed.
-#
-# Example:
-# #############################################################################
-# Fixed:
-#  - description: Fixes scrolling on edit pages in Safari.
-#    issue: DP-13314
-#
-# You may add more than 1 description & issue for each type using the following format:
-# Changed:
-#  - description: Automating the release branch.
-#    issue: DP-10166
-#  - description: Second change item that needs a description.
-#    issue: DP-19875
-#  - description: Third change item that needs a description along with an issue.
-#    issue: DP-19843
-#
-Fixed:
-  - description: Fixed the issue with styles in rich text related to images.
-    issue: DP-34424
diff --git a/changelogs/DP-34468.yml b/changelogs/DP-34468.yml
deleted file mode 100644
index 79e941095e..0000000000
--- a/changelogs/DP-34468.yml
+++ /dev/null
@@ -1,41 +0,0 @@
-#
-# Write your changelog entry here. Every pull request must have a changelog yml file.
-#
-# Change types:
-# #############################################################################
-# You can use one of the following types:
-#  - Added: For new features.
-#  - Changed: For changes to existing functionality.
-#  - Deprecated: For soon-to-be removed features.
-#  - Removed: For removed features.
-#  - Fixed: For any bug fixes.
-#  - Security: In case of vulnerabilities.
-#
-# Format
-# #############################################################################
-# The format is crucial. Please follow the examples below. For reference, the requirements are:
-#  - All 3 parts are required and you must include "Type", "description" and "issue".
-#  - "Type" must be left aligned and followed by a colon.
-#  - "description" must be indented with 2 spaces followed by a colon
-#  - "issue" must be indented with 4 spaces followed by a colon.
-#  - "issue" is for the Jira ticket number only e.g. DP-1234
-#  - No extra spaces, indents, or blank lines are allowed.
-#
-# Example:
-# #############################################################################
-# Fixed:
-#  - description: Fixes scrolling on edit pages in Safari.
-#    issue: DP-13314
-#
-# You may add more than 1 description & issue for each type using the following format:
-# Changed:
-#  - description: Automating the release branch.
-#    issue: DP-10166
-#  - description: Second change item that needs a description.
-#    issue: DP-19875
-#  - description: Third change item that needs a description along with an issue.
-#    issue: DP-19843
-#
-Security:
-  - description: Resolve dependabot issues.
-    issue: DP-34468
diff --git a/changelogs/DP-34515.yml b/changelogs/DP-34515.yml
deleted file mode 100644
index f31c8ad1b0..0000000000
--- a/changelogs/DP-34515.yml
+++ /dev/null
@@ -1,41 +0,0 @@
-#
-# Write your changelog entry here. Every pull request must have a changelog yml file.
-#
-# Change types:
-# #############################################################################
-# You can use one of the following types:
-#  - Added: For new features.
-#  - Changed: For changes to existing functionality.
-#  - Deprecated: For soon-to-be removed features.
-#  - Removed: For removed features.
-#  - Fixed: For any bug fixes.
-#  - Security: In case of vulnerabilities.
-#
-# Format
-# #############################################################################
-# The format is crucial. Please follow the examples below. For reference, the requirements are:
-#  - All 3 parts are required and you must include "Type", "description" and "issue".
-#  - "Type" must be left aligned and followed by a colon.
-#  - "description" must be indented with 2 spaces followed by a colon
-#  - "issue" must be indented with 4 spaces followed by a colon.
-#  - "issue" is for the Jira ticket number only e.g. DP-1234
-#  - No extra spaces, indents, or blank lines are allowed.
-#
-# Example:
-# #############################################################################
-# Fixed:
-#  - description: Fixes scrolling on edit pages in Safari.
-#    issue: DP-13314
-#
-# You may add more than 1 description & issue for each type using the following format:
-# Changed:
-#  - description: Automating the release branch.
-#    issue: DP-10166
-#  - description: Second change item that needs a description.
-#    issue: DP-19875
-#  - description: Third change item that needs a description along with an issue.
-#    issue: DP-19843
-#
-Changed:
-  - description: Email validation in the feedback component.
-    issue: DP-34515
diff --git a/changelogs/DP-34568.yml b/changelogs/DP-34568.yml
deleted file mode 100644
index 81b83a8148..0000000000
--- a/changelogs/DP-34568.yml
+++ /dev/null
@@ -1,41 +0,0 @@
-#
-# Write your changelog entry here. Every pull request must have a changelog yml file.
-#
-# Change types:
-# #############################################################################
-# You can use one of the following types:
-#  - Added: For new features.
-#  - Changed: For changes to existing functionality.
-#  - Deprecated: For soon-to-be removed features.
-#  - Removed: For removed features.
-#  - Fixed: For any bug fixes.
-#  - Security: In case of vulnerabilities.
-#
-# Format
-# #############################################################################
-# The format is crucial. Please follow the examples below. For reference, the requirements are:
-#  - All 3 parts are required and you must include "Type", "description" and "issue".
-#  - "Type" must be left aligned and followed by a colon.
-#  - "description" must be indented with 2 spaces followed by a colon
-#  - "issue" must be indented with 4 spaces followed by a colon.
-#  - "issue" is for the Jira ticket number only e.g. DP-1234
-#  - No extra spaces, indents, or blank lines are allowed.
-#
-# Example:
-# #############################################################################
-# Fixed:
-#  - description: Fixes scrolling on edit pages in Safari.
-#    issue: DP-13314
-#
-# You may add more than 1 description & issue for each type using the following format:
-# Changed:
-#  - description: Automating the release branch.
-#    issue: DP-10166
-#  - description: Second change item that needs a description.
-#    issue: DP-19875
-#  - description: Third change item that needs a description along with an issue.
-#    issue: DP-19843
-#
-Changed:
-  - description: Don't show authors and editors the text format options.
-    issue: DP-34568
diff --git a/changelogs/DP-34675.yml b/changelogs/DP-34675.yml
deleted file mode 100644
index 5905bf57e5..0000000000
--- a/changelogs/DP-34675.yml
+++ /dev/null
@@ -1,41 +0,0 @@
-#
-# Write your changelog entry here. Every pull request must have a changelog yml file.
-#
-# Change types:
-# #############################################################################
-# You can use one of the following types:
-#  - Added: For new features.
-#  - Changed: For changes to existing functionality.
-#  - Deprecated: For soon-to-be removed features.
-#  - Removed: For removed features.
-#  - Fixed: For any bug fixes.
-#  - Security: In case of vulnerabilities.
-#
-# Format
-# #############################################################################
-# The format is crucial. Please follow the examples below. For reference, the requirements are:
-#  - All 3 parts are required and you must include "Type", "description" and "issue".
-#  - "Type" must be left aligned and followed by a colon.
-#  - "description" must be indented with 2 spaces followed by a colon
-#  - "issue" must be indented with 4 spaces followed by a colon.
-#  - "issue" is for the Jira ticket number only e.g. DP-1234
-#  - No extra spaces, indents, or blank lines are allowed.
-#
-# Example:
-# #############################################################################
-# Fixed:
-#  - description: Fixes scrolling on edit pages in Safari.
-#    issue: DP-13314
-#
-# You may add more than 1 description & issue for each type using the following format:
-# Changed:
-#  - description: Automating the release branch.
-#    issue: DP-10166
-#  - description: Second change item that needs a description.
-#    issue: DP-19875
-#  - description: Third change item that needs a description along with an issue.
-#    issue: DP-19843
-#
-Added:
-  - description: Add Urdu language
-    issue: DP-34675
diff --git a/changelogs/DP-34678.yml b/changelogs/DP-34678.yml
deleted file mode 100644
index 5ba5792439..0000000000
--- a/changelogs/DP-34678.yml
+++ /dev/null
@@ -1,41 +0,0 @@
-#
-# Write your changelog entry here. Every pull request must have a changelog yml file.
-#
-# Change types:
-# #############################################################################
-# You can use one of the following types:
-#  - Added: For new features.
-#  - Changed: For changes to existing functionality.
-#  - Deprecated: For soon-to-be removed features.
-#  - Removed: For removed features.
-#  - Fixed: For any bug fixes.
-#  - Security: In case of vulnerabilities.
-#
-# Format
-# #############################################################################
-# The format is crucial. Please follow the examples below. For reference, the requirements are:
-#  - All 3 parts are required and you must include "Type", "description" and "issue".
-#  - "Type" must be left aligned and followed by a colon.
-#  - "description" must be indented with 2 spaces followed by a colon
-#  - "issue" must be indented with 4 spaces followed by a colon.
-#  - "issue" is for the Jira ticket number only e.g. DP-1234
-#  - No extra spaces, indents, or blank lines are allowed.
-#
-# Example:
-# #############################################################################
-# Fixed:
-#  - description: Fixes scrolling on edit pages in Safari.
-#    issue: DP-13314
-#
-# You may add more than 1 description & issue for each type using the following format:
-# Changed:
-#  - description: Automating the release branch.
-#    issue: DP-10166
-#  - description: Second change item that needs a description.
-#    issue: DP-19875
-#  - description: Third change item that needs a description along with an issue.
-#    issue: DP-19843
-#
-Fixed:
-  - description: Empty table being added to rules of court pages with no dates.
-    issue: DP-34678
diff --git a/changelogs/DP-34727.yml b/changelogs/DP-34727.yml
deleted file mode 100644
index d4053c6b0b..0000000000
--- a/changelogs/DP-34727.yml
+++ /dev/null
@@ -1,43 +0,0 @@
-#
-# Write your changelog entry here. Every pull request must have a changelog yml file.
-#
-# Change types:
-# #############################################################################
-# You can use one of the following types:
-#  - Added: For new features.
-#  - Changed: For changes to existing functionality.
-#  - Deprecated: For soon-to-be removed features.
-#  - Removed: For removed features.
-#  - Fixed: For any bug fixes.
-#  - Security: In case of vulnerabilities.
-#
-# Format
-# #############################################################################
-# The format is crucial. Please follow the examples below. For reference, the requirements are:
-#  - All 3 parts are required and you must include "Type", "description" and "issue".
-#  - "Type" must be left aligned and followed by a colon.
-#  - "description" must be indented with 2 spaces followed by a colon
-#  - "issue" must be indented with 4 spaces followed by a colon.
-#  - "issue" is for the Jira ticket number only e.g. DP-1234
-#  - No extra spaces, indents, or blank lines are allowed.
-#
-# Example:
-# #############################################################################
-# Fixed:
-#  - description: Fixes scrolling on edit pages in Safari.
-#    issue: DP-13314
-#
-# You may add more than 1 description & issue for each type using the following format:
-# Changed:
-#  - description: Automating the release branch.
-#    issue: DP-10166
-#  - description: Second change item that needs a description.
-#    issue: DP-19875
-#  - description: Third change item that needs a description along with an issue.
-#    issue: DP-19843
-#
-Added:
-  - description: "Flag to Show/Hide Feedback form on Topic Page, for users with 'create topic_page content' permission."
-    issue: DP-34727
-  - description: "Flag to make optional organization field on Topic Page edit form, for users with 'create topic_page content' permission."
-    issue: DP-34727
diff --git a/changelogs/DP-34797.yml b/changelogs/DP-34797.yml
deleted file mode 100644
index 62198f2ae5..0000000000
--- a/changelogs/DP-34797.yml
+++ /dev/null
@@ -1,41 +0,0 @@
-#
-# Write your changelog entry here. Every pull request must have a changelog yml file.
-#
-# Change types:
-# #############################################################################
-# You can use one of the following types:
-#  - Added: For new features.
-#  - Changed: For changes to existing functionality.
-#  - Deprecated: For soon-to-be removed features.
-#  - Removed: For removed features.
-#  - Fixed: For any bug fixes.
-#  - Security: In case of vulnerabilities.
-#
-# Format
-# #############################################################################
-# The format is crucial. Please follow the examples below. For reference, the requirements are:
-#  - All 3 parts are required and you must include "Type", "description" and "issue".
-#  - "Type" must be left aligned and followed by a colon.
-#  - "description" must be indented with 2 spaces followed by a colon
-#  - "issue" must be indented with 4 spaces followed by a colon.
-#  - "issue" is for the Jira ticket number only e.g. DP-1234
-#  - No extra spaces, indents, or blank lines are allowed.
-#
-# Example:
-# #############################################################################
-# Fixed:
-#  - description: Fixes scrolling on edit pages in Safari.
-#    issue: DP-13314
-#
-# You may add more than 1 description & issue for each type using the following format:
-# Changed:
-#  - description: Automating the release branch.
-#    issue: DP-10166
-#  - description: Second change item that needs a description.
-#    issue: DP-19875
-#  - description: Third change item that needs a description along with an issue.
-#    issue: DP-19843
-#
-Fixed:
-  - description: "500 Error on https://edit.mass.gov/guides/massachusetts-energy-rebates-incentives"
-    issue: DP-34797
diff --git a/scripts/changelog-body.txt b/scripts/changelog-body.txt
index f525cbfb25..03c82b39a4 100644
--- a/scripts/changelog-body.txt
+++ b/scripts/changelog-body.txt
@@ -1,11 +1,22 @@
 
 
-## [0.409.0] - September 3, 2024
+## [0.410.0] - September 10, 2024
 
+### Added
+  - DP-34207: Added posibility to skip GIF image derivative generation if image is animated gif
+  - DP-34675: Add Urdu language
+  - DP-34727: Flag to Show/Hide Feedback form on Topic Page, for users with 'create topic_page content' permission.
+  - DP-34727: Flag to make optional organization field on Topic Page edit form, for users with 'create topic_page content' permission.
+  
 ### Fixed
-  - DP-34561: Fix download links in bulleted list. Adjust collapsible content spacing on mobile.
-  - DP-34687: Orphan page report now available again.
+  - DP-34424: Fixed the issue with styles in rich text related to images.
+  - DP-34678: Empty table being added to rules of court pages with no dates.
+  - DP-34797: 500 Error on https://edit.mass.gov/guides/massachusetts-energy-rebates-incentives
+  
+### Security
+  - DP-34468: Resolve dependabot issues.
   
-### Removed
-  - DP-34585: Removed descendant manager code from mass_content_api and re-enabled.
+### Changed
+  - DP-34515: Email validation in the feedback component.
+  - DP-34568: Don't show authors and editors the text format options.