[pull] main from open-telemetry:main

.cspell.yml

@@ -10,19 +10,19 @@ import:
 caseSensitive: true
 ignorePaths:
   - '*.svg'
-  - content/ja
-  - content/zh
+  - content/{ja,zh}
   - data/community/members.yaml
+  - data/ecosystem/vendors.yaml
+  - public/_redirects
   - static/refcache.json
-  - vendors.yaml
 patterns:
   - name: CodeBlock
     pattern: |
       /
           ^(\s*[~`]{3,})   # code-block start
           .*               # all languages and options, e.g. shell {hl_lines=[12]}
           [\s\S]*?         # content
-          \1               # code-block end
+          \1               # code-block end - cSpell:disable-next-line
       /igmx
 languageSettings:
   - languageId: markdown
@@ -58,6 +58,6 @@ dictionaries:
 words: # Valid words across all locales
   - Docsy
   - htmltest
-  # Hugo
   - jsonify
+  - opentelemetrybot
   - warnf

.github/workflows/check-i18n.yml

@@ -13,7 +13,12 @@ jobs:
         with:
           fetch-depth: 0 # all
       - name: Any files missing hash key?
-        run: scripts/check-i18n.sh -n -x -v
+        run: |
+          scripts/check-i18n.sh -n -x -v
+          .github/workflows/scripts/check-i18n-helper.sh
       - name: Any files with invalid hash keys?
         run: scripts/check-i18n.sh -v
-      - run: .github/workflows/scripts/check-i18n-helper.sh
+      - name: Drifted status needs updating?
+        run: |
+          scripts/check-i18n.sh -D
+        # npm run _diff:fail

.github/workflows/fossa.yml

@@ -0,0 +1,20 @@
+name: FOSSA scanning
+
+on:
+  push:
+    branches:
+      - main
+
+permissions:
+  contents: read
+
+jobs:
+  fossa:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4.2.2
+
+      - uses: fossas/fossa-action@93a52ecf7c3ac7eb40f5de77fd69b1a19524de94 # v1.5.0
+        with:
+          api-key: ${{secrets.FOSSA_API_KEY}}
+          team: OpenTelemetry

.gitmodules

@@ -20,7 +20,7 @@
 [submodule "content-modules/semantic-conventions"]
 	path = content-modules/semantic-conventions
 	url = https://github.com/open-telemetry/semantic-conventions
-	semconv-pin = v1.30.0
+	semconv-pin = v1.31.0
 [submodule "content-modules/opamp-spec"]
 	path = content-modules/opamp-spec
 	url = https://github.com/open-telemetry/opamp-spec

.markdownlint.json

@@ -1,5 +1,6 @@
 {
   "emphasis-style": false,
+  "first-line-h1": false,
   "line-length": false,
   "link-fragments": false,
   "list-marker-space": false,

.textlintrc.yml

@@ -19,7 +19,7 @@ filters:
       # src attribute in figure Hugo template:
       - /src=".*?"/
       # Other:
-      - /<https?://.*?>/ # Raw URLs
+      - /<https?:\/\/.*?>/ # Raw URLs
 rules:
   terminology:
     defaultTerms: false

README.md

@@ -61,7 +61,7 @@ Here is a list of community roles with current and previous members:
   - [Fabrizio Ferri-Benedetti](https://github.com/theletterf)
   - [Patrice Chalin](https://github.com/chalin), CNCF
   - [Phillip Carter](https://github.com/cartermp), Honeycomb
-  - [Severin Neumann](https://github.com/svrnm), Cisco
+  - [Severin Neumann](https://github.com/svrnm)
   - [Tiffany Hrabusa](https://github.com/tiffany76), Grafana Labs
 
 - Emeritus approvers:

assets/js/tracing.js

@@ -7,7 +7,7 @@ import { getWebAutoInstrumentations } from '@opentelemetry/auto-instrumentations
 import { registerInstrumentations } from '@opentelemetry/instrumentation';
 import { OTLPTraceExporter } from '@opentelemetry/exporter-trace-otlp-http';
 import { Resource } from '@opentelemetry/resources';
-import { SemanticResourceAttributes } from '@opentelemetry/semantic-conventions';
+import { ATTR_SERVICE_NAME } from '@opentelemetry/semantic-conventions';
 import { ZoneContextManager } from '@opentelemetry/context-zone-peer-dep';
 
 const collectorOptions = {
@@ -16,21 +16,23 @@ const collectorOptions = {
 const exporter = new OTLPTraceExporter(collectorOptions);
 
 const resources = new Resource({
-  [SemanticResourceAttributes.SERVICE_NAME]: 'opentelemetry.io',
+  [ATTR_SERVICE_NAME]: 'opentelemetry.io',
   'browser.language': navigator.language,
 });
 
 const provider = new WebTracerProvider({
   resource: resources,
+  spanProcessors: [
+    new SimpleSpanProcessor(exporter),
+    new SimpleSpanProcessor(new ConsoleSpanExporter()),
+  ],
 });
 
 registerInstrumentations({
   instrumentations: [getWebAutoInstrumentations({})],
   tracerProvider: provider,
 });
 
-provider.addSpanProcessor(new SimpleSpanProcessor(exporter));
-provider.addSpanProcessor(new SimpleSpanProcessor(new ConsoleSpanExporter()));
 provider.register({
   contextManger: new ZoneContextManager(),
 });

content/en/_includes/page-not-translated-msg.md

@@ -1,5 +1,4 @@
 ---
-title: # bogus entry for markdownlint
 ---
 
 <i class="fa-solid fa-circle-info" style="margin-left: -1.5rem"></i> You are

content/en/announcements/kubecon-eu.md

@@ -8,8 +8,10 @@ weight: -1
 
 <i class="fas fa-bullhorn"></i> [**{{% param title %}}**][LF],
 **<span class="text-nowrap">April 1 - 4,</span> London England**.
-<span class="d-none d-md-inline"><br></span> Come collaborate, learn, and
-share<span class="d-none d-sm-inline"> with the Cloud Native community</span>!
+<span class="d-none d-md-inline"><br></span> Come [collaborate, learn, and
+share][blog]<span class="d-none d-sm-inline"> with the Cloud Native
+community</span>!
 
 [LF]:
   https://events.linuxfoundation.org/kubecon-cloudnativecon-europe/register/?utm_source=opentelemetry&utm_medium=all&utm_campaign=KubeCon-EU-2025&utm_content=slim-banner
+[blog]: /blog/2025/kubecon-eu/

content/en/blog/2023/end-user-discussions-01.md

@@ -20,7 +20,7 @@ they use OpenTelemetry in real life. Sessions are held for users in the Americas
 discussions take place using a
 [Lean Coffee format](https://agilecoffee.com/leancoffee/), whereby folks are
 invited to post their topics to the
-[Agile Coffee board like this one](http://agile.coffee/#b3b37364-d40e-4029-847c-8ee059d60855),
+[Agile Coffee board like this one](http://agile.coffee/?disable_http_check#b3b37364-d40e-4029-847c-8ee059d60855),
 and everyone in attendance votes on what they want to talk about.
 
 This is a great way to meet other users in the OpenTelemetry community, and to

content/en/blog/2023/end-user-discussions-02.md

@@ -18,7 +18,7 @@ Americas (AMER), Europe Middle-East & Africa (EMEA), and Asia-Pacific (APAC).
 The discussions take place using a
 [Lean Coffee format](https://agilecoffee.com/leancoffee/), whereby folks are
 invited to post their topics to the
-[Agile Coffee board like this one](http://agile.coffee/#3716060f-183a-4966-8da4-60daab2842c4),
+[Agile Coffee board like this one](http://agile.coffee/?disable_http_check#3716060f-183a-4966-8da4-60daab2842c4),
 and everyone in attendance votes on what they want to talk about.
 
 ## What we talked about

content/en/blog/2023/end-user-discussions-03.md

@@ -19,7 +19,7 @@ Americas (AMER), Europe Middle-East & Africa (EMEA), and Asia-Pacific (APAC).
 The discussions take place using a
 [Lean Coffee format](https://agilecoffee.com/leancoffee/), whereby folks are
 invited to post their topics to the
-[Agile Coffee board like this one](http://agile.coffee/#3716060f-183a-4966-8da4-60daab2842c4),
+[Agile Coffee board like this one](http://agile.coffee/?disable_http_check#3716060f-183a-4966-8da4-60daab2842c4),
 and everyone in attendance votes on what they want to talk about.
 
 ## What we talked about

content/en/blog/2023/end-user-discussions-04.md

@@ -13,7 +13,7 @@ regions again in May.
 The discussions take place using a
 [Lean Coffee format](https://agilecoffee.com/leancoffee/), whereby folks are
 invited to post their topics to the
-[Agile Coffee board like this one](http://agile.coffee/#2f83c1c1-918c-4c78-8671-194b2e9d8e54),
+[Agile Coffee board like this one](http://agile.coffee/?disable_http_check#2f83c1c1-918c-4c78-8671-194b2e9d8e54),
 and everyone in attendance votes on what they want to talk about.
 
 ## What we talked about

content/en/blog/2023/end-user-q-and-a-02.md

@@ -274,7 +274,7 @@ him in the
 channel!
 
 Also, be sure to check out more of Doug's OTel adventures at this month's
-[OTel in Practice series, on March 27th, 09:00 PT/11:00 ET](http://surl.li/fqdox).
+[OTel in Practice series, on March 27th, 09:00 PT/11:00 ET](https://surl.li/fqdox).
 
 ## Final Thoughts
 

content/en/blog/2023/otel-arrow/index.md

@@ -15,10 +15,11 @@ which is based on [Apache Arrow](https://arrow.apache.org/), a columnar-oriented
 memory format used for developing analytics applications. This integration
 facilitates a reduction in telemetry data traffic by a factor of 10 after
 compression, offering a 40% improvement over the best existing OpenTelemetry
-Protocol (OTLP) configurations with [Zstandard (zstd)](http://www.zstd.net/)
-compression enabled. As a result, this new protocol emerges as an optimal choice
-for transporting telemetry data over the internet. We are also excited to
-announce the release of a new pair of receiver/exporter in the
+Protocol (OTLP) configurations with
+[Zstandard (zstd)](https://facebook.github.io/zstd/) compression enabled. As a
+result, this new protocol emerges as an optimal choice for transporting
+telemetry data over the internet. We are also excited to announce the release of
+a new pair of receiver/exporter in the
 [opentelemetry-collector-contrib](https://github.com/open-telemetry/opentelemetry-collector-contrib/)
 repository that supports this protocol. This protocol, designed to complement
 the OTLP protocol in situations with substantial telemetry data volumes, has

content/en/blog/2023/otterize-otel/index.md

@@ -47,7 +47,7 @@ with each other. You can then use that information for operational or security
 needs, such as determining the blast radius of a downtime or security incident.
 You can use the service graph to figure out where to start rolling out
 OpenTelemetry tracing, as that deployment tends to be more involved and requires
-the integration of the OpenTelemetry SDK into your source code.
+the integration of the OpenTelemetry SDK into your source code.
 
 While it was easy to use the OTel SDK for the network mapper, we can see why
 there's a bit of a chicken-and-egg problem here when you're looking into

content/en/blog/2024/cve-2024-36129.md

@@ -100,10 +100,11 @@ If you are using a custom distribution and building it with the
 can add a
 [“replaces”](https://github.com/open-telemetry/opentelemetry-collector/tree/main/cmd/builder#configuration)
 entry pointing to the latest version of the
-[confighttp](http://go.opentelemetry.io/collector/config/confighttp) and
-[configgrpc](http://go.opentelemetry.io/collector/config/configgrpc) Go module.
-If your base Collector version is at v0.96.0 or higher, we do not expect any
-compatibility issues by just bumping to the latest version.
+[confighttp](https://pkg.go.dev/go.opentelemetry.io/collector/config/confighttp)
+and
+[configgrpc](https://pkg.go.dev/go.opentelemetry.io/collector/config/configgrpc)
+Go module. If your base Collector version is at v0.96.0 or higher, we do not
+expect any compatibility issues by just bumping to the latest version.
 
 ## Lessons learned