Dependency Dashboard

This issue lists Renovate updates and detected dependencies. Read the [Dependency Dashboard](https://docs.renovatebot.com/key-concepts/dashboard/) docs to learn more.

## Awaiting Schedule

The following updates are awaiting their schedule. To get an update now, click on a checkbox below.

- [ ] Update Node.js to ccd0612
- [ ] Update dependency commonmarker to v2.10.0
- [ ] Update dependency netlify-cli to v27.3.0
- [ ] Update jdkato/vale Docker tag to v3.18.0
- [ ] Update dependency @docsearch/js to v5
- [ ] 🔐 **Create all awaiting schedule PRs at once** 🔐

## Detected Dependencies

buildkite (8)

.buildkite/pipeline.deploy.yml (5)

- `aws-assume-role-with-web-identity v1.7.0`
- `ecr v2.12.0`
- `aws-assume-role-with-web-identity v1.7.0`
- `cultureamp/ecr-scan-results v1.9.1`
- `aws-assume-role-with-web-identity v1.7.0`

.buildkite/pipeline.graphql.yml (2)

- `aws-assume-role-with-web-identity v1.7.0`
- `aws-ssm v1.1.0`

.buildkite/pipeline.preview.yml (5)

- `aws-assume-role-with-web-identity v1.7.0`
- `aws-ssm v1.1.0`
- `aws-assume-role-with-web-identity v1.7.0`
- `aws-ssm v1.1.0`
- `docker-compose v5.14.0`

.buildkite/pipeline.sync_public_pr.yml (3)

- `aws-assume-role-with-web-identity v1.7.0`
- `aws-ssm v1.1.0`
- `docker v5.14.0`

.buildkite/pipeline.sync.yml (2)

- `aws-assume-role-with-web-identity v1.7.0`
- `aws-ssm v1.1.0`

.buildkite/pipeline.yml (44)

- `aws-assume-role-with-web-identity v1.7.0`
- `ecr v2.12.0`
- `docker-compose v5.14.0`
- `aws-assume-role-with-web-identity v1.7.0`
- `ecr v2.12.0`
- `docker-compose v5.14.0`
- `aws-assume-role-with-web-identity v1.7.0`
- `ecr v2.12.0`
- `aws-ssm v1.1.0`
- `docker v5.14.0`
- `aws-assume-role-with-web-identity v1.7.0`
- `ecr v2.12.0`
- `docker-compose v5.14.0`
- `docker v5.14.0`
- `docker v5.14.0`
- `docker v5.14.0`
- `docker v5.14.0`
- `docker v5.14.0`
- `aws-assume-role-with-web-identity v1.7.0`
- `ecr v2.12.0`
- `docker v5.14.0`
- `docker-compose v5.14.0`
- `aws-assume-role-with-web-identity v1.7.0`
- `ecr v2.12.0`
- `docker v5.14.0`
- `aws-assume-role-with-web-identity v1.7.0`
- `ecr v2.12.0`
- `docker v5.14.0`
- `aws-assume-role-with-web-identity v1.7.0`
- `ecr v2.12.0`
- `docker v5.14.0`
- `aws-assume-role-with-web-identity v1.7.0`
- `ecr v2.12.0`
- `docker v5.14.0`
- `aws-assume-role-with-web-identity v1.7.0`
- `ecr v2.12.0`
- `docker-compose v5.14.0`
- `aws-assume-role-with-web-identity v1.7.0`
- `ecr v2.12.0`
- `docker-compose v5.14.0`
- `bugcrowd/test-summary v1.11.0`
- `aws-assume-role-with-web-identity v1.7.0`
- `aws-ssm v1.1.0`
- `docker v5.14.0`

.buildkite/steps/docs-draft-changelog.yml (3)

- `aws-assume-role-with-web-identity v1.7.0`
- `aws-ssm v1.1.0`
- `docker v5.14.0`

.buildkite/steps/docs-draft-step.yml (3)

- `aws-assume-role-with-web-identity v1.7.0`
- `aws-ssm v1.1.0`
- `docker v5.14.0`

bundler (1)

Gemfile (28)

- `ruby ~> 4.0`
- `actionpack "~> 8.1.0"`
- `actionview "~> 8.1.0"`
- `activesupport "~> 8.1.0"`
- `railties "~> 8.1.0"`
- `puma "~> 8.0"`
- `foreman lock file @ 0.90.0`
- `stringex lock file @ 2.8.6`
- `redcarpet lock file @ 3.6.1`
- `commonmarker lock file @ 2.9.0` → [Updates: `undefined`]
- `rouge "5.1.0"`
- `lograge lock file @ 0.15.0`
- `bugsnag lock file @ 6.30.0`
- `front_matter_parser lock file @ 1.0.1`
- `matrix lock file @ 0.4.3`
- `ostruct lock file @ 0.6.3`
- `vite_rails lock file @ 3.11.1`
- `turbo-rails lock file @ 2.0.23`
- `sitemap_generator lock file @ 7.1.1`
- `byebug lock file @ 13.0.0`
- `dotenv-rails lock file @ 3.2.0`
- `web-console lock file @ 4.3.0`
- `pry lock file @ 0.16.0`
- `graphql-client lock file @ 0.26.0`
- `rspec-rails lock file @ 8.0.4`
- `rspec_junit_formatter lock file @ 0.6.0`
- `capybara lock file @ 3.40.0`
- `buildkite-test_collector lock file @ 2.14.0`

docker-compose (2)

docker-compose.yml

vale/docker-compose.yml

dockerfile (2)

Dockerfile (6)

- `public.ecr.aws/docker/library/ruby 4.0.6-slim-bookworm@sha256:c5650da02325ecb3e7dd96e7074772c3ae2ecd093a9acf2cdbcf1a2fdc680726`
- `public.ecr.aws/docker/library/node 24-bookworm-slim@sha256:3638d9a6fe4030bd716be989438248074489337ba3275657f93595428be4fc03` → [Updates: `24-bookworm-slim`]
- `public.ecr.aws/docker/library/golang 1.27-bookworm`
- `public.ecr.aws/docker/library/ruby 4.0.6-slim-bookworm@sha256:c5650da02325ecb3e7dd96e7074772c3ae2ecd093a9acf2cdbcf1a2fdc680726`
- `raviqqe/muffet 2.11.5`
- `public.ecr.aws/docker/library/ruby 4.0.6-slim-bookworm@sha256:c5650da02325ecb3e7dd96e7074772c3ae2ecd093a9acf2cdbcf1a2fdc680726`

vale/Dockerfile (1)

- `jdkato/vale v3.17.1` → [Updates: `v3.18.0`]

github-actions (1)

.github/workflows/labeler.yml (1)

- `actions/labeler v7@bf12e9b00b37c5c0ca2b87b79b2daf7891dbda13`

gomod (3)

go.mod (1)

- `go 1.24.0`

scripts/algolia/go.mod (2)

- `go 1.24.0`
- `github.com/algolia/algoliasearch-client-go/v4 v4.45.0`

tools/pr-review-agent/go.mod (1)

- `go 1.24.4`

mise (1)

mise.toml (2)

- `ruby 4.0.6`
- `node 24`

npm (1)

package.json (8)

- `@docsearch/js 4` → [Updates: `5`]
- `@hotwired/turbo-rails ^8.0.23`
- `husky ^9.0.0`
- `netlify-cli ^27.0.0` → [Updates: `^27.0.0`]
- `prettier 3.9.6`
- `sass ^1.66.1`
- `vite ^8.0.0`
- `vite-plugin-ruby ^5.2.0`

regex (5)

.buildkite/pipeline.sync_public_pr.yml (1)

- `ruby 4.0.6-bookworm`

.buildkite/pipeline.yml (12)

- `public.ecr.aws/docker/library/ruby 4.0.6-slim-bookworm`
- `golang 1.27`
- `golang 1.27`
- `golang 1.27`
- `ruby 4.0.6-bookworm`
- `ruby 4.0.6-bookworm`
- `public.ecr.aws/docker/library/node 24-alpine`
- `public.ecr.aws/docker/library/node 24-alpine`
- `public.ecr.aws/docker/library/node 24-alpine`
- `public.ecr.aws/docker/library/node 24-alpine`
- `public.ecr.aws/docker/library/node 24-alpine`
- `golang 1.27-bookworm`

.buildkite/steps/docs-draft-changelog.yml (1)

- `node 24-slim`

.buildkite/steps/docs-draft-step.yml (1)

- `node 24-slim`

scripts/update-bkcli-help.sh (1)

- `buildkite/cli v3.55.0`

Start with one awaiting-schedule entry and inspect the named manifest or configuration file, such as Gemfile, package.json, Dockerfile, or a .buildkite pipeline. Read the linked Renovate Dependency Dashboard documentation first, then verify the selected dependency update does not leave the dashboard entry awaiting schedule and that the relevant checks pass.

Written by the indexing model from the issue text.