Skip to content

chore(deps): update dependency markdownlint-cli2 to v0.19.1 #925

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
trask merged 2 commits into from
Nov 26, 2025
Merged

chore(deps): update dependency markdownlint-cli2 to v0.19.1 #925

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
78c9f06
chore(deps): update dependency markdownlint-cli2 to v0.19.1
renovate[bot] Nov 26, 2025
e668401
Fix new linting errors
trask Nov 26, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion mise.toml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3,7 +3,7 @@ lychee = "0.21.0"
k3d = "5.8.2"
"go:github.com/grafana/oats" = "0.4.1"
kubectl = "1.34.2"
markdownlint-cli2 = "0.17.1"
markdownlint-cli2 = "0.19.1"

[settings]
# Only install tools explicitly defined in the [tools] section above
Expand Down
6 changes: 3 additions & 3 deletions resource-detection-gcp/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@

An example application that shows what resource attributes will be detected by the [GCP Resource Detector](https://github.com/open-telemetry/opentelemetry-java-contrib/tree/main/gcp-resources) and how the [Autoconfigure Resource Provider SPI](https://opentelemetry.io/docs/languages/java/configuration/#spi-service-provider-interface) automatically *attaches* the detected resource attributes to the generated telemetry.

*For users looking to use the GCP Resource Detector with OpenTelemetry Java Agent for automatic instrumentation, refer to the instructions [here](https://opentelemetry.io/docs/languages/java/automatic/configuration/#enable-resource-providers-that-are-disabled-by-default).*
*For users looking to use the GCP Resource Detector with OpenTelemetry Java Agent for automatic instrumentation, refer to the [instructions for enabling resource providers that are disabled by default](https://opentelemetry.io/docs/languages/java/automatic/configuration/#enable-resource-providers-that-are-disabled-by-default).*

## Prerequisites

Expand Down Expand Up @@ -53,7 +53,7 @@ gcloud artifacts repositories create ${ARTIFACT_REGISTRY} --repository-format=do
## Running in Google Kubernetes Engine

> [!NOTE]
> Make sure that kubectl is installed and configured to access a GKE cluster. Relevant documentation can be found [here](https://cloud.google.com/kubernetes-engine/docs/how-to/cluster-access-for-kubectl#run_against_a_specific_cluster).
> Make sure that kubectl is installed and configured to access a GKE cluster. Relevant documentation can be found in the [GKE cluster access guide](https://cloud.google.com/kubernetes-engine/docs/how-to/cluster-access-for-kubectl#run_against_a_specific_cluster).

To spin it up on your own GKE cluster, run the following:

Expand All @@ -74,7 +74,7 @@ The detected attributes will contain the attributes detected by the GCP resource
## Running the application locally

> [!NOTE]
> Resource attributes won't be detected in unsupported environments. You can find a list of environments supported by the GCP detector [here](https://github.com/open-telemetry/opentelemetry-java-contrib/tree/main/gcp-resources).
> Resource attributes won't be detected in unsupported environments. You can find a [list of supported environments in the GCP detector documentation](https://github.com/open-telemetry/opentelemetry-java-contrib/tree/main/gcp-resources).

You can run the application locally as well:

Expand Down