Multiple minor updates in docs

.devcontainer/installMoreTools.sh

@@ -3,6 +3,8 @@
 mkdir install-more-tools
 cd install-more-tools
 
+yarn add dprint
+
 SCORE_COMPOSE_VERSION=$(curl -sL https://api.github.com/repos/score-spec/score-compose/releases/latest | jq -r .tag_name)
 wget https://github.com/score-spec/score-compose/releases/download/${SCORE_COMPOSE_VERSION}/score-compose_${SCORE_COMPOSE_VERSION}_linux_amd64.tar.gz
 tar -xvf score-compose_${SCORE_COMPOSE_VERSION}_linux_amd64.tar.gz

content/en/docs/How to/github.md

@@ -22,7 +22,7 @@ To use the Score GitHub Action, add the following step to your [workflow](https:
 
 ```yaml
 steps:
-  - uses: score-spec/setup-score@v2
+  - uses: score-spec/setup-score@v3
     with:
       file: <score-cli>
       version: '<x.y.z>'
@@ -54,14 +54,14 @@ jobs:
     runs-on: ubuntu-latest
 
     steps:
-      - uses: score-spec/setup-score@v2
+      - uses: score-spec/setup-score@v3
         with:
           file: score-compose
-          version: '0.13.0'
+          version: 'latest'
           token: ${{ secrets.GITHUB_TOKEN }}
       - run: score-compose --version
 ```
 
-This installs version `0.13.0` of `score-compose`, adds it to `$PATH`, and runs `score-compose --version` to verify it is set up correctly.
+This installs the `latest` version of `score-compose`, adds it to `$PATH`, and runs `score-compose --version` to verify it is set up correctly.
 
 The action caches the Score binary, so it won't need to download it each run.

content/en/docs/How to/score-cicd-pipelines.md

@@ -77,7 +77,7 @@ jobs:
     steps:
       - uses: actions/checkout@v4
       - uses: docker/setup-buildx-action@v3
-      - uses: paulhatch/semantic-version@v5.0.3
+      - uses: paulhatch/semantic-version@v5
         id: semver
       - uses: docker/build-push-action@v5
         with:
@@ -98,10 +98,10 @@ The next set of steps focuses on testing with `score-compose`. This provides val
 This helps to maximize the chance that the "release" step to production succeeds and results in a working application.
 
 ```yaml
-  - uses: score-spec/setup-score@v2
+  - uses: score-spec/setup-score@v3
     with:
       file: score-compose
-      version: 0.15.6
+      version: latest
       token: ${{ secrets.GITHUB_TOKEN }}
   - run: score-compose init
   - run: score-compose generate score.yaml --image=${{ env.REGISTRY }}/${{ env.IMAGE_NAME }}:${{ steps.semver.outputs.version }}
@@ -147,10 +147,10 @@ jobs:
 And finally, the steps to convert to Kubernetes manifests and deploy them. Notice that the `generate` call is setting the image to the tag that was just uploaded in the previous steps. The `azure/` actions are maintained by Azure, but are not Azure-specific and can deploy to any generic Kubernetes cluster as needed. Notice that this requires a `KUBECONFIG` secret variable set in the Github Actions workflow to authenticate with the target cluster.
 
 ```yaml
-- uses: score-spec/setup-score@v2
+- uses: score-spec/setup-score@v3
   with:
     file: score-k8s
-    version: 0.1.5
+    version: latest
     token: ${{ secrets.GITHUB_TOKEN }}
 - uses: azure/k8s-set-context@v2
   with:

content/en/docs/How to/score-k8s/kind-cluster.md

@@ -72,7 +72,7 @@ EOF
 
 From here, by using the [default provisioners with `score-k8s init`](/docs/score-implementation/score-k8s/resources-provisioners/), you will be able to use this `Gateway` by using the `route` object which will generate an `HTTPRoute` link to this `Gateway`.
 
-This default `HTTPRoute` is assuming that `Gateway` is in the same `Namespace`, but if you want to use the [cross-Namespace Gateway](https://gateway-api.sigs.k8s.io/guides/multiple-ns/) approach, you will need to use [this community provisioner](https://github.com/score-spec/community-provisioners/blob/main/route/score-k8s/10-shared-gateway-httproute.provisioners.yaml) instead:
+This default `HTTPRoute` is assuming that `Gateway` is in the same `Namespace`, but if you want to use the [cross-Namespace Gateway](https://gateway-api.sigs.k8s.io/guides/multiple-ns/) approach, you will need to use [this community provisioner](https://docs.score.dev/examples/resource-provisioners/community/route/score-k8s/template/route-with-shared-gateway/) instead:
 
 ```bash
 score-k8s init \
@@ -87,7 +87,7 @@ Install the Nginx Ingress controller in the Kind cluster:
 kubectl apply -f https://raw.githubusercontent.com/kubernetes/ingress-nginx/main/deploy/static/provider/kind/deploy.yaml
 ```
 
-From here, you can now use [this community provisioner](https://github.com/score-spec/community-provisioners/blob/main/route/score-k8s/10-ingress-route.provisioners.yaml) to generate an `Ingress` for the `route` resource instead of the default `HTTPRoute`:
+From here, you can now use [this community provisioner](https://docs.score.dev/examples/resource-provisioners/community/route/score-k8s/template/ingress-route/) to generate an `Ingress` for the `route` resource instead of the default `HTTPRoute`:
 
 ```bash
 score-k8s init \

content/en/docs/community/_index.md

@@ -26,6 +26,8 @@ We host [regular community meetings](https://github.com/score-spec/spec?tab=read
 
 ## Watch talks about Score
 
+- _(Coming) [KubeCon India 2026 - The Death of the YAML-Engineer: Engineering "Invisible" Platforms With Crossplane and Score](https://sched.co/2IW4r)_
+- _(Coming) [KubeCon Europe 2026 - Unifying Inner & Outer Loops To Bridge the Gaps Between Devs & Ops With Microcks + Score - Laurent Broudoux, Microcks & Mathieu Benoit, Docker](https://sched.co/2CVxb)_
 - [Cloud Native Rejekts NA 2025 - Make your Developer's Pains go Away, with the Right Level of Abstraction for your Platform](https://youtu.be/CLCK2lBpWa8)
 - [LF Live Webinar: From CI to Kubernetes Catalog: A Practical Guide to vCluster and GitOps](https://youtu.be/U4AgmEo3oV8)
 - [KubeCon EU 2025 - Score Lightning Talk](https://sched.co/1tcwp) [[video](https://youtu.be/Nq_PgPKZHsc?list=PLj6h78yzYM2MP0QhYFK8HOb8UqgbIkLMc)]

content/en/docs/examples/included/backstage-score-compose.md

@@ -16,7 +16,7 @@ score-compose init --no-sample \
     --provisioners https://raw.githubusercontent.com/score-spec/community-provisioners/refs/heads/main/dns/score-compose/10-dns-with-url.provisioners.yaml
 ```
 
-The `init` command will create the `.score-compose` directory with the [default resource provisioners]({{< relref "/docs/score-implementation/score-compose/resources-provisioners/" >}}) available. We are also importing one external file to support the `dns` dependencies: [`dns` provisioner](https://github.com/score-spec/community-provisioners/blob/main/dns/score-compose/10-dns-with-url.provisioners.yaml).
+The `init` command will create the `.score-compose` directory with the [default resource provisioners]({{< relref "/docs/score-implementation/score-compose/resources-provisioners/" >}}) available. We are also importing one external file to support the `dns` dependencies: [`dns` provisioner](https://docs.score.dev/examples/resource-provisioners/community/dns/score-compose/template/dns-with-url/).
 
 You can see the resource provisioners available by running this command:
 

content/en/docs/examples/included/backstage-score-k8s.md

@@ -16,7 +16,7 @@ score-k8s init --no-sample \
     --provisioners https://raw.githubusercontent.com/score-spec/community-provisioners/refs/heads/main/dns/score-k8s/10-dns-with-url.provisioners.yaml
 ```
 
-The `init` command will create the `.score-k8s` directory with the [default resource provisioners]({{< relref "/docs/score-implementation/score-k8s/resources-provisioners/" >}}) available. We are also importing one external file to support the `dns` dependencies: [`dns` provisioner](https://github.com/score-spec/community-provisioners/blob/main/dns/score-k8s/10-dns-with-url.provisioners.yaml).
+The `init` command will create the `.score-k8s` directory with the [default resource provisioners]({{< relref "/docs/score-implementation/score-k8s/resources-provisioners/" >}}) available. We are also importing one external file to support the `dns` dependencies: [`dns` provisioner](https://docs.score.dev/examples/resource-provisioners/community/dns/score-k8s/template/dns-with-url/).
 
 You can see the resource provisioners available by running this command:
 

content/en/docs/examples/included/dapr-score-compose.md

@@ -17,7 +17,7 @@ score-compose init --no-sample \
     --patch-templates https://raw.githubusercontent.com/score-spec/community-patchers/refs/heads/main/score-compose/dapr.tpl
 ```
 
-The `init` command will create the `.score-compose` directory with the [default resource provisioners]({{< relref "/docs/score-implementation/score-compose/resources-provisioners/" >}}) available. We are also importing one external file to seamlessly generate a Dapr StateStore `Component` pointing to a Redis database: [`dapr-state-store` provisioner](https://github.com/score-spec/community-provisioners/blob/main/dapr-state-store/score-compose/10-redis-dapr-state-store.provisioners.yaml).
+The `init` command will create the `.score-compose` directory with the [default resource provisioners]({{< relref "/docs/score-implementation/score-compose/resources-provisioners/" >}}) available. We are also importing one external file to seamlessly generate a Dapr StateStore `Component` pointing to a Redis database: [`dapr-state-store` provisioner](https://docs.score.dev/examples/resource-provisioners/community/dapr-state-store/score-compose/template/redis-dapr-state-store/).
 
 You can see the resource provisioners available by running this command:
 

content/en/docs/examples/included/dapr-score-k8s.md

@@ -16,7 +16,7 @@ score-k8s init --no-sample \
     --provisioners https://raw.githubusercontent.com/score-spec/community-provisioners/refs/heads/main/dapr-state-store/score-k8s/10-redis-dapr-state-store.provisioners.yaml
 ```
 
-The `init` command will create the `.score-k8s` directory with the [default resource provisioners]({{< relref "/docs/score-implementation/score-k8s/resources-provisioners/" >}}) available. We are also importing one external file to generate a Dapr StateStore `Component` pointing to a Redis database: [`dapr-state-store` provisioner](https://github.com/score-spec/community-provisioners/blob/main/dapr-state-store/score-k8s/10-redis-dapr-state-store.provisioners.yaml).
+The `init` command will create the `.score-k8s` directory with the [default resource provisioners]({{< relref "/docs/score-implementation/score-k8s/resources-provisioners/" >}}) available. We are also importing one external file to generate a Dapr StateStore `Component` pointing to a Redis database: [`dapr-state-store` provisioner](https://docs.score.dev/examples/resource-provisioners/community/dapr-state-store/score-k8s/template/redis/).
 
 You can see the resource provisioners available by running this command:
 

content/en/docs/examples/included/frontend-and-backend-score-compose.md

@@ -17,7 +17,7 @@ score-compose init --no-sample \
     --provisioners https://raw.githubusercontent.com/score-spec/community-provisioners/refs/heads/main/dns/score-compose/10-dns-with-url.provisioners.yaml
 ```
 
-The `init` command will create the `.score-compose` directory with the [default resource provisioners]({{< relref "/docs/score-implementation/score-compose/resources-provisioners/" >}}) available. We are also importing two external files to support the `dns` dependencies: [`dns` provisioner](https://github.com/score-spec/community-provisioners/blob/main/dns/score-compose/10-dns-with-url.provisioners.yaml) and `service` dependencies: [`service` provisioner](https://github.com/score-spec/community-provisioners/blob/main/service/score-compose/10-service.provisioners.yaml).
+The `init` command will create the `.score-compose` directory with the [default resource provisioners]({{< relref "/docs/score-implementation/score-compose/resources-provisioners/" >}}) available. We are also importing two external files to support the `dns` dependencies: [`dns` provisioner](https://docs.score.dev/examples/resource-provisioners/community/dns/score-compose/template/dns-with-route/) and `service` dependencies: [`service` provisioner](https://docs.score.dev/examples/resource-provisioners/community/service/score-compose/template/static-service/).
 
 You can see the resource provisioners available by running this command:
 

content/en/docs/examples/included/frontend-and-backend-score-k8s.md

@@ -17,7 +17,7 @@ score-k8s init --no-sample \
     --provisioners https://raw.githubusercontent.com/score-spec/community-provisioners/refs/heads/main/dns/score-k8s/10-dns-with-url.provisioners.yaml
 ```
 
-The `init` command will create the `.score-k8s` directory with the [default resource provisioners]({{< relref "/docs/score-implementation/score-k8s/resources-provisioners/" >}}) available. We are also importing two external files to support the `dns` dependencies: [`dns` provisioner](https://github.com/score-spec/community-provisioners/blob/main/dns/score-k8s/10-dns-with-url.provisioners.yaml) and `service` dependencies: [`service` provisioner](https://github.com/score-spec/community-provisioners/blob/main/service/score-k8s/10-service.provisioners.yaml).
+The `init` command will create the `.score-k8s` directory with the [default resource provisioners]({{< relref "/docs/score-implementation/score-k8s/resources-provisioners/" >}}) available. We are also importing two external files to support the `dns` dependencies: [`dns` provisioner](https://docs.score.dev/examples/resource-provisioners/community/dns/score-k8s/template/dns-with-url/) and `service` dependencies: [`service` provisioner](https://docs.score.dev/examples/resource-provisioners/community/service/score-k8s/template/static-service/).
 
 You can see the resource provisioners available by running this command: