docs: adds an upgrade guide for overlay 1.1

upgrading/index.md

@@ -21,5 +21,6 @@ Each version upgrade guide covers:
 
 - [Upgrading from OpenAPI 3.0 to 3.1](v3.0-to-v3.1): Learn about the significant changes and how to migrate your API descriptions.
 - [Upgrading from OpenAPI 3.1 to 3.2](v3.1-to-v3.2): Discover the latest features and migration path for the newest version.
+- [Upgrading from Overlay 1.0 to 1.1](overlay-v1.0-to-v1.1): Discover the latest features and migration path for the newest version.
 
 Choose the appropriate guide based on your current OpenAPI version and target version.

upgrading/overlay-v1.0-to-v1.1.md

@@ -0,0 +1,110 @@
+---
+layout: default
+title: Overlay - Upgrading Between Versions 1.0 and 1.1
+parent: Upgrading Between Versions
+nav_order: 1
+---
+
+# Overlay - Upgrading Between Versions 1.0 and 1.1
+
+Overlay 1.1 adds powerful new copy features, and upgrading from 1.0 is as simple as updating the version number. This guide walks you through that quick transition.
+
+## Getting started
+
+Begin by updating the version number in your Overlay document. Locate this line in your JSON or YAML file:
+
+```yaml
+overlay: 1.0.0
+```
+
+Update it to:
+
+```yaml
+overlay: 1.1.0
+```
+
+## Copy elements from the OpenAPI document
+
+The following example illustrates how you can now use the copy action to update a target node with a value from the document being processed. Saving you from having duplicate definitions in your overlay document.
+
+```yaml
+overlay: 1.0.0
+info:
+  title: Copy a schema component
+  version: 1.1.0
+actions:
+  - target: '$.components.schemas'
+    description: Ensure the target schema is present
+    update:
+      Bar: {}
+  - target: '$.components.schemas['Bar']'
+    copy: '$.components.schemas['Foo']'
+    description: Copy the Foo Schema to Bar
+```
+
+## Name the file according to the convention for better tooling integration
+
+You might want to rename your overlay documents to end with `.overlay.yaml|json` to get better integration with tooling.
+
+## Ensure your JSONPath are RFC 9535 for better interoperability
+
+### Missing square brackets around property names
+
+This example JSONPath query expression, which filters path items based on an OpenAPI extension property:
+
+```jsonpath
+$.paths.*.get[?(@.x-oai-traits[?(@ == 'paged')])]
+```
+
+Should in fact be:
+
+```jsonpath
+$.paths.*.get[?(@['x-oai-traits'][?(@ == 'paged')])]
+```
+
+Because square brackets are required for property selection.
+
+### Use of the undefined `in` keyword
+
+This example JSONPath query expression, which selects tags matching *Enterprise-Only*:
+
+```jsonpath
+$.paths..[?('Enterprise-Only' in @.tags)]
+```
+
+Should instead be:
+
+```jsonpath
+$.paths..[?(@.tags[?(@ == 'Enterprise-Only')])]
+```
+
+Since the `in` keyword is undefined in the RFC.
+
+## Removing/Updating primitive values is now fully supported
+
+```yaml
+overlay: 1.1.0
+info:
+  title: Targeted Overlay
+  version: 1.0.0
+actions:
+  - target: $.paths['/foo'].get.description
+    update: This is the new description
+  - target: $.paths['/bar'].get.description
+    update: This is the updated description
+```
+
+Before it used to require updating the parent object.
+
+## Add a description to your overlay document
+
+The Overlay information section now supports a new description field. Adding a detailed description to your overlay documents is a great way to convey the purpose and nature of your documents.
+
+```yaml
+overlay: 1.1.0
+info:
+  title: Overlay with description
+  version: 1.0.0
+  description: This overlay document has a long description thanks to the new field.
+actions: []
+```