Update lychee to latest version which really does verify link fragments (#2848)

Author: trask

.github/scripts/lychee-config.toml

@@ -2,14 +2,25 @@ include_fragments = true
 
 accept = ["200..=299", "403"]
 
+remap = [
+  # workaround for https://github.com/lycheeverse/lychee/issues/1729
+  "https://github.com/(.*?)/(.*?)/blob/(.*?)/(.*#.*)$ https://raw.githubusercontent.com/$1/$2/$3/$4",
+  "https://docs.oracle.com/(.*)#.*$ https://docs.oracle.com/$1",
+  "https://www.ibm.com/docs/api/v1/content/SSYKE2_8.0.0/openj9/(.*)#.*$ https://www.ibm.com/docs/api/v1/content/SSYKE2_8.0.0/openj9/$1",
+  "https://docs.docker.com/reference/(.*)#.*$ https://docs.docker.com/reference/$1",
+  "https://javadoc.io/(.*)#.*$ https://javadoc.io/$1",
+  "https://github.com/(.*)#issuecomment-.*$ https://github.com/$1",
+  "https://github.com/(.*)#discussion_r.*$ https://github.com/$1",
+]
+
 exclude = [
-    "^https://www.foo.bar",
-    # excluding links to pull requests and issues is done for performance
-    "^https://github.com/open-telemetry/semantic-conventions/(pull|issues)/\\d+$",
-    "^https://github.com/open-telemetry/opentelemetry-specification/(pull|issues)/\\d+$",
-    # TODO (lmolkova) treat timeout as not a failure?
-    "^https://www.intersystems.com",
-    "^https://gcc.gnu.org",
+  "^https://www.foo.bar",
+  # excluding links to pull requests and issues is done for performance
+  "^https://github.com/open-telemetry/semantic-conventions/(pull|issues)/\\d+$",
+  "^https://github.com/open-telemetry/opentelemetry-specification/(pull|issues)/\\d+$",
+  # TODO (lmolkova) treat timeout as not a failure?
+  "^https://www.intersystems.com",
+  "^https://gcc.gnu.org",
 ]
 
 # better to be safe and avoid failures

CHANGELOG.md

@@ -414,7 +414,7 @@ the VCS metrics to include `vcs.repository.name` as a recommended attribute.
 ### 🧰 Bug fixes 🧰
 
 - `service`: Merge `resource` experimental and stable groups for service and telemetry.sdk (#1423)
-  Discovered when fixing [weaver#306](https://github.com/open-telemetry/weaver/issues/306#issue-2458430277)
+  Discovered when fixing [weaver#306](https://github.com/open-telemetry/weaver/issues/306)
 
 - `db`: Fix telemetry for complex queries:
 

dependencies.Dockerfile

@@ -9,4 +9,4 @@ FROM otel/weaver:v0.18.0@sha256:5425ade81dc22ddd840902b0638b4b6a9186fb654c5b50c1
 FROM openpolicyagent/opa:1.9.0@sha256:bd7e1216865884be8095726fb80282ece2f6b531883bc86f9f8917f2fc52de61 AS opa
 
 # Lychee is used for checking links in documentation.
-FROM lycheeverse/lychee:sha-2aa22f8@sha256:2e3786630482c41f9f2dd081e06d7da1c36d66996e8cf6573409b8bc418d48c4 AS lychee
+FROM lycheeverse/lychee:sha-0a96dc2@sha256:2d397eb32e4add073deb5af328f7d644538cd62c007892c57b57551b073b6a12 AS lychee

docs/cicd/cicd-metrics.md

@@ -79,7 +79,7 @@ Batch operations:
 Bulk operations:
 
 - `execute_bulk` SHOULD be used on spans reported for methods like
-  [`executeBulkOperations`](https://javadoc.io/doc/com.azure/azure-cosmos/latest/com/azure/cosmos/CosmosAsyncContainer.html#executeBulkOperations)).
+  [`executeBulkOperations`](https://javadoc.io/doc/com.azure/azure-cosmos/latest/com/azure/cosmos/CosmosAsyncContainer.html#executeBulkOperations(reactor.core.publisher.Flux)),
   which represents a bulk execution of multiple operations.
 - `bulk_{operation name}` (`bulk_create_item`, `bulk_upsert_item`, etc) SHOULD be used on spans describing individual operations (when they are reported)
   within the bulk. This pattern SHOULD be used when instrumentation creates span per each operation, but operations are buffered and then performed in bulk.

docs/database/cosmosdb.md

@@ -21,7 +21,7 @@ emitted through the [Logger API](https://github.com/open-telemetry/opentelemetry
 ## Recording an exception
 
 Exceptions SHOULD be recorded as attributes on the
-[LogRecord](https://github.com/open-telemetry/opentelemetry-specification/blob/v1.49.0/specification/logs/data-model.md#log-and-event-record-definition) passed to the [Logger](https://github.com/open-telemetry/opentelemetry-specification/tree/v1.49.0/specification/logs/api.md#logger) emit
+[LogRecord](https://github.com/open-telemetry/opentelemetry-specification/blob/v1.49.0/specification/logs/data-model.md#log-and-event-record-definition) passed to the [Logger](https://github.com/open-telemetry/opentelemetry-specification/blob/v1.49.0/specification/logs/api.md#logger) emit
 operations. Exceptions MAY be recorded on "logs" or "events" depending on the
 context.
 

docs/exceptions/exceptions-logs.md

@@ -385,7 +385,7 @@ FaaS providers. This list is not exhaustive.
 * [AWS Lambda Metrics](https://docs.aws.amazon.com/lambda/latest/dg/monitoring-metrics.html)
 * [AWS Lambda Insight Metrics](https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/Lambda-Insights-metrics.html)
 * [Azure Functions Metrics](https://docs.microsoft.com/azure/azure-monitor/platform/metrics-supported)
-* [Google CloudFunctions Metrics](https://cloud.google.com/monitoring/api/metrics_gcp#gcp-cloudfunctions)
+* [Google CloudFunctions Metrics](https://cloud.google.com/monitoring/api/metrics_gcp)
 * [OpenFaas Metrics](https://docs.openfaas.com/architecture/metrics/)
 
 [DocumentStatus]: https://opentelemetry.io/docs/specs/otel/document-status

docs/faas/faas-metrics.md

@@ -121,7 +121,7 @@ The span attribute `faas.invocation_id` differs from the [resource attribute][Fa
 
 [AWS lambda]: https://docs.aws.amazon.com/lambda/latest/dg/lambda-runtimes.html
 [Azure functions]: https://docs.microsoft.com/azure/azure-functions/manage-connections#static-clients
-[Google functions]: https://cloud.google.com/functions/docs/concepts/execution-environment#scope
+[Google functions]: https://cloud.google.com/functions/docs/concepts/execution-environment
 
 ## Incoming invocations
 

docs/faas/faas-spans.md

@@ -26,7 +26,7 @@ This can be used to determine the impact a feature has on a request, enabling en
 
 ## Recording an evaluation
 
-Feature flag evaluations SHOULD be recorded as attributes on the [Event](https://github.com/open-telemetry/opentelemetry-specification/blob/v1.49.0/specification/logs/data-model.md#events) passed to the [Logger](https://github.com/open-telemetry/opentelemetry-specification/tree/v1.49.0/specification/logs/api.md#logger) emit operations.
+Feature flag evaluations SHOULD be recorded as attributes on the [Event](https://github.com/open-telemetry/opentelemetry-specification/blob/v1.49.0/specification/logs/data-model.md#events) passed to the [Logger](https://github.com/open-telemetry/opentelemetry-specification/blob/v1.49.0/specification/logs/api.md#logger) emit operations.
 
 > Note:
 > Events are in-development and not yet available in some languages. Check the [spec-compliance matrix](https://github.com/open-telemetry/opentelemetry-specification/blob/v1.49.0/spec-compliance-matrix.md#logs) to see the implementation status in the corresponding language.

docs/feature-flags/feature-flags-events.md

@@ -26,7 +26,7 @@ with attributes and the type of the body if any.
   that uniquely identifies the event. Event names are subject to the [Naming guidelines](/docs/general/naming.md). Event name SHOULD be of a low-cardinality.
 * Events MAY have [attributes](https://github.com/open-telemetry/opentelemetry-specification/blob/v1.49.0/specification/logs/data-model.md#field-attributes)
   that provide additional context about the event.
-* Events MAY contain a [body](https://github.com/open-telemetry/opentelemetry-specification/blob/v1.49.0/specification/logs/data-model.md#field-body) of type [`any`](https://github.com/open-telemetry/opentelemetry-specification/tree/v1.49.0/specification/logs/data-model.md#type-any).
+* Events MAY contain a [body](https://github.com/open-telemetry/opentelemetry-specification/blob/v1.49.0/specification/logs/data-model.md#field-body) of type [`any`](https://github.com/open-telemetry/opentelemetry-specification/blob/v1.49.0/specification/logs/data-model.md#type-any).
 * The event name uniquely identifies event structure: the set of attributes and
   the type of the body.
 * Events MAY have [severity number](https://github.com/open-telemetry/opentelemetry-specification/blob/v1.49.0/specification/logs/data-model.md#field-severitynumber).