Merge branch 'gh-pages' into patch-1

Author: AlvaroRausell

.devcontainer/devcontainer.json

@@ -3,7 +3,7 @@
 {
 	"name": "Jekyll",
 	// Or use a Dockerfile or Docker Compose file. More info: https://containers.dev/guide/dockerfile
-	"image": "mcr.microsoft.com/devcontainers/jekyll:1-bullseye",
+	"image": "mcr.microsoft.com/devcontainers/jekyll:2",
 
 	// Features to add to the dev container. More info: https://containers.dev/features.
 	"features": {

.devcontainer/fetch-index.sh

@@ -0,0 +1,12 @@
+# To get started with Dependabot version updates, you'll need to specify which
+# package ecosystems to update and where the package manifests are located.
+# Please see the documentation for more information:
+# https://docs.github.com/github/administering-a-repository/configuration-options-for-dependency-updates
+# https://containers.dev/guide/dependabot
+
+version: 2
+updates:
+ - package-ecosystem: "devcontainers"
+   directory: "/"
+   schedule:
+     interval: weekly

.github/dependabot.yml

@@ -0,0 +1,10 @@
+---
+
+extends: default
+
+
+rules:
+  line-length: disable
+  trailing-spaces: disable
+  document-start: disable
+

.github/lint-config.yaml

@@ -0,0 +1,26 @@
+name: 'Lint collection-index.yml'
+on:
+  pull_request:
+    paths:
+      - _data/collection-index.yml
+
+permissions:
+  contents: read
+  pull-requests: write
+
+jobs:
+  yamllint:
+    name: 'Yamllint'
+    runs-on: ubuntu-latest
+    steps:
+      - name: 'Checkout'
+        uses: actions/checkout@v6
+      - name: 'Yamllint'
+        uses: karancode/yamllint-github-action@@v2.1.1
+        with:
+          yamllint_file_or_dir: _data/collection-index.yml
+          yamllint_strict: true
+          yamllint_config_filepath: .github/lint-config.yaml
+          yamllint_comment: true
+        env:
+          GITHUB_ACCESS_TOKEN: ${{ secrets.GITHUB_TOKEN }}

.github/workflows/lint.yml

@@ -58,7 +58,7 @@ jobs:
           destination: ./_site
 
       - name: Upload artifact
-        uses: actions/upload-pages-artifact@v1
+        uses: actions/upload-pages-artifact@v3
 
   # Deployment job
   deploy:
@@ -70,4 +70,4 @@ jobs:
     steps:
       - name: Deploy to GitHub Pages
         id: deployment
-        uses: actions/deploy-pages@v1
+        uses: actions/deploy-pages@v4

.github/workflows/publish.yml

@@ -6,7 +6,7 @@ author: Microsoft
 index: 4
 ---
 
-The `devcontainer.json` file contains any needed metadata and settings required to configurate a **development container** for a given well-defined tool and runtime stack. It can be used by [tools and services that support the dev container spec](../../supporting) to create a **development environment** that contains one or more **development containers**.
+The `devcontainer.json` file contains any needed metadata and settings required to configure a **development container** for a given well-defined tool and runtime stack. It can be used by [tools and services that support the dev container spec](../../supporting) to create a **development environment** that contains one or more **development containers**.
 
 Metadata properties marked with a 🏷️️ can be stored in the `devcontainer.metadata` **[container image label](/implementors/reference/#labels)** in addition to `devcontainer.json`. This label can contain an array of json snippets that will be automatically merged with `devcontainer.json` contents (if any) when a container is created.
 

_data/collection-index.yml

@@ -57,7 +57,7 @@ <h1 style="margin-left: auto;margin-right: auto;">Available Dev Container Featur
     const collectionTable = document.getElementById('collectionTable');
     const rows = collectionTable.getElementsByTagName('tr');
 
-    searchInput.addEventListener('input', function () {
+    function performSearch() {
         const searchValue = searchInput.value.toLowerCase();
 
         for (let i = 1; i < rows.length; i++) {
@@ -71,5 +71,24 @@ <h1 style="margin-left: auto;margin-right: auto;">Available Dev Container Featur
                 rows[i].style.display = 'none';
             }
         }
+    }
+
+    searchInput.addEventListener('input', function () {
+        performSearch();
+        const url = new URL(window.location);
+        if (searchInput.value) {
+            url.searchParams.set('search', searchInput.value);
+        } else {
+            url.searchParams.delete('search');
+        }
+        window.history.replaceState({}, '', url);
     });
+
+    // Read search parameter from URL on page load
+    const urlParams = new URLSearchParams(window.location.search);
+    const searchParam = urlParams.get('search');
+    if (searchParam) {
+        searchInput.value = searchParam;
+        performSearch();
+    }
 </script>

_implementors/json_reference.md

@@ -193,6 +193,17 @@ The following properties apply differently to CodeSandbox.
 
 [DevPod](https://github.com/loft-sh/devpod) is a client-only tool to create reproducible developer environments based on a `devcontainer.json` on any backend. Each developer environment runs in a container and is specified through a `devcontainer.json`. Through DevPod providers these environments can be created on any backend, such as the local computer, a Kubernetes cluster, any reachable remote machine or in a VM in the cloud.
 
+### <a href="#ona" name="ona" class="anchor"> Ona (formerly Gitpod) </a>
+
+[Ona](https://ona.com/) (formerly Gitpod)  is the mission control for software projects and software engineering agents. It provides secure, ephemeral development environments that run in our cloud or your VPC, enabling humans and agents to collaborate seamlessly.
+
+Ona fully adheres to the Dev Container Specification, so you can define portable and reproducible environments with `devcontainer.json`. Whether you’re onboarding a new developer, running background agents, or delegating long-running migrations, Ona Environments ensure every task runs in a clean, policy-enforced environment.
+
+For details on constraints, customization, and automation options, see the [Ona Dev Container docs](https://ona.com/docs/ona/configuration/devcontainer/overview).
+
+
 ### <a href="#schema" name="schema" class="anchor"> Schema </a>
 
 You can explore the [VS Code implementation](implementors/json_schema) of the dev container schema.
+
+