diff --git a/CHANGELOG.md b/CHANGELOG.md
new file mode 100644
index 000000000..09193efd9
--- /dev/null
+++ b/CHANGELOG.md
@@ -0,0 +1,190 @@
+# Changelog
+
+All notable changes to this project will be documented in this file. The format is based on
+[Keep a Changelog], and this project adheres to [Semantic Versioning].
+
+
+[Keep a Changelog]: https://keepachangelog.com/en/1.1.0/
+[Semantic Versioning]: https://semver.org/spec/v2.0.0.html
+
+## [Unreleased]
+
+
+[Unreleased]: https://github.com/PowerShell/DSC/compare/v3.0.0-alpha.2...main
+
+
+## [v3.0.0-alpha.2] - 2023-09-05
+
+
+[v3.0.0-alpha.2]: https://github.com/PowerShell/DSC/compare/v3.0.0-alpha.1...v3.0.0-alpha.2
+
+### Added
+
+- Implemented functionality for the [dependsOn property of resource instances][01] in configuration
+ documents, enabling resource instances to depend on the successful processing of one or more
+ other instances in the document.
+
+ Related work items
+
+ - Issues: #45
+ - PRs: #175
+
+
+
+- Added the [export][02] property to the resource manifest schema, indicating that the resource is
+ exportable and defining how DSC can retrieve the current state for every instance of the
+ resource.
+
+ Related work items
+
+ - Issues: #73
+ - PRs: #171
+
+
+
+- Added the [dsc config export][03] command to convert an input configuration document defining a
+ list of resource types into a usable configuration document that defines the current state for
+ every instance of those resources.
+
+ Related work items
+
+ - Issues: #73
+ - PRs: #171
+
+
+
+- Added the [dsc resource export][04] command to generate a usable configuration document that
+ defines the current state for every instance of a specified resource.
+
+ Related work items
+
+ - Issues: #73
+ - PRs: #171
+
+
+
+- Added the [--all][05] option for the [dsc resource get][06] command, enabling users to retrieve
+ the current state for every instance of an exportable resource with a single command.
+
+ Related work items
+
+ - Issues:
+ - #73
+ - #174
+ - PRs: #171
+
+
+
+- Added handling for the Ctrl+C key combination to cancel a DSC operation.
+ When `dsc` cancels an operation due to this key-press, it indicates that the operation was
+ cancelled with [exit code 6][07].
+
+ Related work items
+
+ - PRs: #177
+ - Issues: #150
+
+
+
+- Added support for using the [DSC_RESOURCE_PATH environment variable][08] to define a list of
+ folders to search for command-based DSC Resource manifests. When `DSC_RESOURCE_PATH` is defined,
+ DSC searches those folders for resources and ignores the `PATH` variable for resource discovery.
+
+ Related work items
+
+ - PRs: #176
+ - Issues: #133
+
+
+
+- The `DSC/AssertionGroup`, `DSC/Group`, and `DSC/ParallelGroup` resources now define semantic exit
+ codes in their manifests. These resources now indicate that they use the same
+ [exit codes as the dsc command][08].
+
+ Related work items
+
+ - PRs: #182
+ - Issues: #181
+
+
+
+- Added type validation in the schema for the [defaultValue][09] and [allowedValues][10] properties
+ of [configuration document parameters][11] to improve the authoring experience. Now, when a
+ parameter defines values for these properties that are incompatible with the defined data type,
+ validation raises an error indicating that the values are invalid and why.
+
+- Enhanced VS Code-specific schemas for configuration documents and resource manifests to improve
+ the authoring experience. The enhanced schemas use keywords only supported by VS Code to:
+
+ - Render Markdown help information for properties and enums.
+ - Provide contextual error messages when a value fails pattern validation.
+ - Define default snippets to autocomplete values.
+
+ These schemas are non-canonical and should only be used for authoring. For more information, see
+ [Using the enhanced schemas for authoring][12].
+
+ Related work items
+
+ - PRs: #172
+
+
+
+- Documentation to the [Microsoft/OSInfo][13] resource instance schema and command-line tool to
+ provide contextual help about the properties the resource can validate.
+
+ Related work items
+
+ - PRs: #168
+
+
+
+### Changed
+
+- The [$schema][14] value for configuration documents now points to the canonical published schema
+ URI,
+ `https://raw.githubusercontent.com/PowerShell/DSC/main/schemas/2023/08/config/document.json`.
+
+ Related work items
+
+ - PRs: #156
+
+
+
+### Fixed
+
+- The data-type conditionals for the [configuration parameters][11] schema so that the `min*` and
+ `max*` keywords apply to the correct data types. Previously, the logic prevented them from ever
+ applying.
+
+- Using the `registry find` command no longer raises a panic error due to conflicting option
+ definitions on the command.
+
+ Related work items
+
+ - PRs: #163
+
+
+
+## [v3.0.0-alpha.1] - 2023-08-04
+
+
+[v3.0.0-alpha.1]: https://github.com/PowerShell/DSC/compare/6090b1464bbf81fded5453351708482a4db35258...v3.0.0-alpha.1
+
+This is the first public release of DSC v3. Consider this release alpha quality. Use it only for
+development evaluation, as it has known issues and isn't feature complete.
+
+
+[01]: docs/reference/schemas/config/resource.md#dependson
+[02]: docs/reference/schemas/resource/manifest/export.md
+[03]: docs/reference/cli/config/export.md
+[04]: docs/reference/cli/resource/export.md
+[05]: docs/reference/cli/resource/get.md##a---all
+[06]: docs/reference/cli/resource/get.md
+[07]: docs/reference/cli/dsc.md#exit-codes
+[08]: docs/reference/cli/dsc.md#environment-variables
+[09]: docs/reference/schemas/config/parameter.md#defaultvalue
+[10]: docs/reference/schemas/config/parameter.md#allowedvalues
+[11]: docs/reference/schemas/config/parameter.md
+[12]: https://learn.microsoft.com/powershell/dsc/concepts/using-enhanced-schemas?view=dsc-3.0&preserveView=true
+[13]: https://learn.microsoft.com/powershell/dsc/reference/microsoft/osinfo/resource?view=dsc-3.0&preserveView=true
+[14]: docs/reference/schemas/config/document.md#schema