diff --git a/packages/provider/README.md b/packages/provider/README.md
index 55cc093fb2fe98e83a90a6d4a5bb86670a8e0131..cb628e8770720a393177b048f48a7a7a89bbe4ac 100644
--- a/packages/provider/README.md
+++ b/packages/provider/README.md
@@ -41,6 +41,12 @@ You can provide attributes (e.g. `global-name`) for components inside the provid
 <script type="module" src="node_modules/@dbp-toolkit/provider/dist/dbp-provider.js"></script>
 ```
 
+Or you can also use the CDN to include the component:
+
+```html
+<script type="module" src="https://unpkg.com/@dbp-toolkit/provider@0.2.2/dist/dbp-provider.js"></script>
+```
+
 All other components are also inherent providers (see below), so you don't really need `dbp-provider` in the shadow dom
 of other components. The use of `dbp-provider` is mainly suggested being used for namespacing (e.g. different languages
 or entry point urls on the same page) or to deliver attribute changes across different components.
diff --git a/packages/provider/package.json b/packages/provider/package.json
index b1c7c9d4f2b2bdc459d4700b09902e8383428437..f7db285060c65816526a92c35b73f8c22d3e91c8 100644
--- a/packages/provider/package.json
+++ b/packages/provider/package.json
@@ -1,7 +1,7 @@
 {
   "name": "@dbp-toolkit/provider",
   "homepage": "https://gitlab.tugraz.at/dbp/web-components/toolkit/-/tree/master/packages/provider",
-  "version": "0.2.2",
+  "version": "0.2.3",
   "main": "src/index.js",
   "license": "LGPL-2.1-or-later",
   "repository": {