diff --git a/BREAKING_CHANGES.md b/BREAKING_CHANGES.md
deleted file mode 100644
index 7e0d08644..000000000
--- a/BREAKING_CHANGES.md
+++ /dev/null
@@ -1,9 +0,0 @@
-- View Filters config structure changed
-- View Groups config structure changed
-- `theme` props removed (use new `useTheme` hook instead)
-- date string template filter now use date-fns instead of momentjs
-- filter rules behavior changed for objects and lists
-- i18n settings `defaultLocale` => `default_locale`
-
-# Typescript
-- `StringOrTextField` has been split into `StringField` and `TextField`.
\ No newline at end of file
diff --git a/packages/docs/content/docs/decap-migration-guide.mdx b/packages/docs/content/docs/decap-migration-guide.mdx
index 377806442..43c4b4d0f 100644
--- a/packages/docs/content/docs/decap-migration-guide.mdx
+++ b/packages/docs/content/docs/decap-migration-guide.mdx
@@ -4,10 +4,6 @@ title: Decap / Netlify Migration Guide
weight: 190
---
-
- This page is a work in progress! It will likely change before v4.0.0 goes live.
-
-
Static CMS is a fork of [Decap](https://github.com/decaporg/decap-cms) (previously Netlify CMS). Many changes have been made, some big, some small.
In this guide, we will walk you through the steps of migrating from Decap or Netlify to Static CMS.
@@ -33,7 +29,7 @@ Netlify (_remove_):
Static CMS (_add_):
```html
-
+
```
### Bundling
diff --git a/packages/docs/content/docs/editorial-workflow.mdx b/packages/docs/content/docs/editorial-workflow.mdx
index 025c547c9..a637c92ae 100644
--- a/packages/docs/content/docs/editorial-workflow.mdx
+++ b/packages/docs/content/docs/editorial-workflow.mdx
@@ -6,7 +6,7 @@ beta: true
---
- Editorial Workflow currently does not work for the Gitea backend. Support coming soon.
+ Editorial Workflow is not available for the Gitea backend.
By default, all entries created or edited in Static CMS are committed directly into the main repository branch.
diff --git a/packages/docs/content/docs/gitea-backend.mdx b/packages/docs/content/docs/gitea-backend.mdx
index e920ad86b..84ef48eee 100644
--- a/packages/docs/content/docs/gitea-backend.mdx
+++ b/packages/docs/content/docs/gitea-backend.mdx
@@ -4,6 +4,10 @@ group: Backends
weight: 45
---
+
+ Gitea backend cannot be used with the Editorial Workflow.
+
+
- **Name**: `gitea`
For repositories stored on Gitea, the `gitea` backend allows CMS users to log in directly with their Gitea account. Note that all users must have push access to your content repository for this to work.
diff --git a/packages/docs/content/docs/migration-guide-v4.mdx b/packages/docs/content/docs/migration-guide-v4.mdx
index 7e45115e9..d8df9a2a7 100644
--- a/packages/docs/content/docs/migration-guide-v4.mdx
+++ b/packages/docs/content/docs/migration-guide-v4.mdx
@@ -4,10 +4,6 @@ title: How to Upgrade to v4
weight: 101
---
-
- This page is a work in progress! It will likely change before v4.0.0 goes live.
-
-
Static CMS v4 introduces:
- [Custom themes](/docs/custom-theme)
@@ -23,23 +19,23 @@ Please [report any issues](https://github.com/StaticJsCMS/static-cms/issues/new)
To install the latest version of Static CMS:
```bash
-npm install @staticcms/core@^4.0.0-beta.15
+npm install @staticcms/core@^4.0.0
```
Or if you are using yarn:
```bash
-yarn add @staticcms/core@^4.0.0-beta.15
+yarn add @staticcms/core@^4.0.0
```
If you are using a CDN to load Static CMS, simply change your URLs:
```html
-
+
```
```html
-
+
```
## View Filters
diff --git a/packages/docs/content/docs/open-authoring.mdx b/packages/docs/content/docs/open-authoring.mdx
index 644c95b62..506f12110 100644
--- a/packages/docs/content/docs/open-authoring.mdx
+++ b/packages/docs/content/docs/open-authoring.mdx
@@ -6,7 +6,7 @@ beta: true
---
- Open Authoring only works with the [GitHub backend](/docs/github-backend) and must be used with the [Editorial Workflow](/docs/editorial-workflow).
+ Open Authoring is only available with the [GitHub backend](/docs/github-backend) and must be used with the [Editorial Workflow](/docs/editorial-workflow).
When using the [GitHub backend](/docs/github-backend), you can use Static CMS to accept contributions from GitHub users without giving them access to your repository. When they make changes in the CMS, the CMS forks your repository for them behind the scenes, and all the changes are made to the fork. When the contributor is ready to submit their changes, they can set their draft as ready for review in the CMS. This triggers a pull request to your repository, which makes it appear in the Dashboard for maintainers.
diff --git a/packages/docs/content/releases.json b/packages/docs/content/releases.json
index 1bca3d20a..a7a794b6a 100644
--- a/packages/docs/content/releases.json
+++ b/packages/docs/content/releases.json
@@ -1,5 +1,11 @@
{
"releases": [
+ {
+ "date": "2024-01-03T10:00:00.000Z",
+ "version": "v4.0.0",
+ "type": "major",
+ "description": "Editorial workflow, open authoring and theming"
+ },
{
"date": "2024-01-02T11:00:00.000Z",
"version": "v4.0.0-beta.17",