Skip to content

Conversation

@renovate
Copy link

@renovate renovate bot commented Feb 18, 2025

Welcome to Renovate! This is an onboarding PR to help you understand and configure settings before regular Pull Requests begin.

🚦 To activate Renovate, merge this Pull Request. To disable Renovate, simply close this Pull Request unmerged.


Detected Package Files

  • docker/docker-compose-examples/analytics/docker-compose.yml (docker-compose)
  • docker/docker-compose-examples/cluster-mode/docker-compose-node-1.yml (docker-compose)
  • docker/docker-compose-examples/cluster-mode/docker-compose-node-2.yml (docker-compose)
  • docker/docker-compose-examples/lgtm-observability/docker-compose.yml (docker-compose)
  • docker/docker-compose-examples/push-publish/docker-compose.yml (docker-compose)
  • docker/docker-compose-examples/single-node-debug-mode/docker-compose.yml (docker-compose)
  • docker/docker-compose-examples/single-node-demo-site/docker-compose.yml (docker-compose)
  • docker/docker-compose-examples/single-node-metrics-monitoring/docker-compose.yml (docker-compose)
  • docker/docker-compose-examples/single-node/docker-compose.yml (docker-compose)
  • docker/docker-compose-examples/with-opensearch-dashboard/docker-compose.yml (docker-compose)
  • docker/docker-compose-examples/with-redis-session/docker-compose-node-1.yml (docker-compose)
  • docker/docker-compose-examples/with-redis-session/docker-compose-node-2.yml (docker-compose)
  • docker/docker-compose-examples/with-redis/docker-compose-node-1.yml (docker-compose)
  • docker/docker-compose-examples/with-redis/docker-compose-node-2.yml (docker-compose)
  • dotCMS/src/docker-compose/it-test/docker-compose.yml (docker-compose)
  • dotCMS/src/docker-compose/local-run/docker-compose.yml (docker-compose)
  • dotcms-postman/docker-compose.yml (docker-compose)
  • docker/dev-env/Dockerfile (dockerfile)
  • docker/java-base/Dockerfile (dockerfile)
  • docker/pg-base/Dockerfile (dockerfile)
  • dotCMS/src/main/docker/original/Dockerfile (dockerfile)
  • tools/dotcms-cli/cli/src/main/docker/Dockerfile.jvm (dockerfile)
  • tools/dotcms-cli/cli/src/main/docker/Dockerfile.legacy-jar (dockerfile)
  • tools/dotcms-cli/cli/src/main/docker/Dockerfile.native (dockerfile)
  • tools/dotcms-cli/cli/src/main/docker/Dockerfile.native-micro (dockerfile)
  • tools/dotcms-cli/src/main/docker/Dockerfile.jvm (dockerfile)
  • tools/dotcms-cli/src/main/docker/Dockerfile.legacy-jar (dockerfile)
  • tools/dotcms-cli/src/main/docker/Dockerfile.native (dockerfile)
  • tools/dotcms-cli/src/main/docker/Dockerfile.native-micro (dockerfile)
  • .github/actions/core-cicd/deployment/deploy-cli-npm/action.yml (github-actions)
  • .github/actions/core-cicd/deployment/deploy-docker/action.yml (github-actions)
  • .github/actions/core-cicd/deployment/deploy-javadoc/action.yml (github-actions)
  • .github/actions/core-cicd/deployment/deploy-javascript-sdk/action.yml (github-actions)
  • .github/actions/core-cicd/deployment/deploy-jfrog/action.yml (github-actions)
  • .github/actions/core-cicd/maven-job/action.yml (github-actions)
  • .github/actions/core-cicd/notification/notify-slack/action.yaml (github-actions)
  • .github/actions/core-cicd/setup-java/action.yml (github-actions)
  • .github/actions/legacy-release/sbom-generator/action.yml (github-actions)
  • .github/workflows/cicd_comp_build-phase.yml (github-actions)
  • .github/workflows/cicd_comp_cli-native-build-phase.yml (github-actions)
  • .github/workflows/cicd_comp_deployment-phase.yml (github-actions)
  • .github/workflows/cicd_comp_finalize-phase.yml (github-actions)
  • .github/workflows/cicd_comp_initialize-phase.yml (github-actions)
  • .github/workflows/cicd_comp_semgrep-phase.yml (github-actions)
  • .github/workflows/cicd_comp_test-phase.yml (github-actions)
  • .github/workflows/cicd_manual-release-sdks.yml (github-actions)
  • .github/workflows/cicd_manual_build-docker-context.yml (github-actions)
  • .github/workflows/cicd_manual_build-java-base.yml (github-actions)
  • .github/workflows/cicd_manual_publish-starter.yml (github-actions)
  • .github/workflows/cicd_post-workflow-reporting.yml (github-actions)
  • .github/workflows/cicd_release-cli.yml (github-actions)
  • .github/workflows/cicd_scheduled_notify-seated-prs.yml (github-actions)
  • .github/workflows/issue_comment_claude-code-review.yaml (github-actions)
  • .github/workflows/issue_comp_frontend-notify.yml (github-actions)
  • .github/workflows/issue_comp_label-conditional-labeling.yml (github-actions)
  • .github/workflows/issue_comp_link-issue-to-pr.yml (github-actions)
  • .github/workflows/issue_comp_release-labeling.yml (github-actions)
  • .github/workflows/issue_manual_label-customer_deployed-issues.yml (github-actions)
  • .github/workflows/issue_manual_label-issues.yml (github-actions)
  • .github/workflows/issue_on-change_assign-issues-to-qa-project.yml (github-actions)
  • .github/workflows/issue_scheduled_stale-action.yml (github-actions)
  • .github/workflows/legacy-release_comp_maven-build-docker-image.yml (github-actions)
  • .github/workflows/legacy-release_maven-release-process.yml (github-actions)
  • .github/workflows/legacy-release_publish-docker-image-on-release.yml (github-actions)
  • .github/workflows/legacy-release_release-candidate.yml (github-actions)
  • .github/workflows/legacy-release_release-trigger.yml (github-actions)
  • .github/workflows/legacy-release_sbom-generator.yaml (github-actions)
  • .github/workflows/publish_docs.yml (github-actions)
  • .github/workflows/security_scheduled_pentest.yml (github-actions)
  • .github/workflows/utility_discover-docker-tags.yml (github-actions)
  • tools/dotcms-cli/action/.github/workflows/main.yml (github-actions)
  • test-jmeter/helm-chart/jmeter-performance/values.yaml (helm-values)
  • core-web/libs/dotcms-field-elements/src/dot-form.html (html)
  • core-web/libs/dotcms-field-elements/src/index.html (html)
  • core-web/libs/dotcms-webcomponents/.storybook/preview-head.html (html)
  • bom/application/pom.xml (maven)
  • bom/logging/pom.xml (maven)
  • bom/pom.xml (maven)
  • build-parent/pom.xml (maven)
  • core-web/pom.xml (maven)
  • dotCMS/pom.xml (maven)
  • dotcms-integration/pom.xml (maven)
  • dotcms-postman/pom.xml (maven)
  • e2e/dotcms-e2e-java/pom.xml (maven)
  • e2e/dotcms-e2e-node/pom.xml (maven)
  • e2e/pom.xml (maven)
  • independent-projects/core-plugins/pom.xml (maven)
  • independent-projects/core-plugins/tika-api/pom.xml (maven)
  • independent-projects/core-plugins/tika-plugin/pom.xml (maven)
  • independent-projects/pom.xml (maven)
  • nodejs-parent/pom.xml (maven)
  • osgi-base/core-bundles/pom.xml (maven)
  • osgi-base/pom.xml (maven)
  • osgi-base/system-bundles/pom.xml (maven)
  • parent/pom.xml (maven)
  • pom.xml (maven)
  • reports/pom.xml (maven)
  • test-jmeter/pom.xml (maven)
  • test-karate/pom.xml (maven)
  • tools/dotcms-cli/api-data-model/pom.xml (maven)
  • tools/dotcms-cli/cli/pom.xml (maven)
  • tools/dotcms-cli/pom.xml (maven)
  • .mvn/wrapper/maven-wrapper.properties (maven-wrapper)
  • mvnw (maven-wrapper)
  • mvnw.cmd (maven-wrapper)
  • .github/actions/issues/issue-fetcher/package.json (npm)
  • .github/actions/issues/issue-labeler/package.json (npm)
  • .github/actions/legacy-release/changelog-report/package.json (npm)
  • .github/actions/legacy-release/rc-changelog/package.json (npm)
  • core-web/apps/mcp-server/package.json (npm)
  • core-web/libs/dot-layout-grid/package.json (npm)
  • core-web/libs/dotcms-js/package.json (npm)
  • core-web/libs/dotcms-models/package.json (npm)
  • core-web/libs/dotcms-webcomponents/package.json (npm)
  • core-web/libs/dotcms/package.json (npm)
  • core-web/libs/edit-content-bridge/package.json (npm)
  • core-web/libs/sdk/analytics/package.json (npm)
  • core-web/libs/sdk/angular/package.json (npm)
  • core-web/libs/sdk/client/package.json (npm)
  • core-web/libs/sdk/experiments/package.json (npm)
  • core-web/libs/sdk/react/package.json (npm)
  • core-web/libs/sdk/types/package.json (npm)
  • core-web/libs/sdk/uve/package.json (npm)
  • core-web/package.json (npm)
  • dotCMS/src/main/webapp/ext/tinymcev7/package.json (npm)
  • dotCMS/src/main/webapp/html/js/dojo/custom-build/dijit/package.json (npm)
  • dotCMS/src/main/webapp/html/js/dojo/custom-build/dojo/package.json (npm)
  • dotCMS/src/main/webapp/html/js/dojo/custom-build/dojox/package.json (npm)
  • dotCMS/src/main/webapp/html/js/legacy_custom_field_bridge/package.json (npm)
  • dotcms-postman/package.json (npm)
  • e2e/dotcms-e2e-node/frontend/package.json (npm)
  • starter/nextjs/package.json (npm)
  • .nvmrc (nvm)
  • core-web/.nvmrc (nvm)

Configuration Summary

Based on the default config's presets, Renovate will:

  • Start dependency updates only once this onboarding PR is merged
  • Hopefully safe environment variables to allow users to configure.
  • Show all Merge Confidence badges for pull requests.
  • Enable Renovate Dependency Dashboard creation.
  • Use semantic commit type fix for dependencies and chore for all others if semantic commits are in use.
  • Ignore node_modules, bower_components, vendor and various test/tests (except for nuget) directories.
  • Group known monorepo packages together.
  • Use curated list of recommended non-monorepo package groupings.
  • Show only the Age and Confidence Merge Confidence badges for pull requests.
  • Apply crowd-sourced package replacement rules.
  • Apply crowd-sourced workarounds for known problems with packages.

🔡 Do you want to change how Renovate upgrades your dependencies? Add your custom config to renovate.json in this branch. Renovate will update the Pull Request description the next time it runs.


What to Expect

With your current configuration, Renovate will create 371 Pull Requests:

chore(deps): update dependency @​types/jest to v29.5.14
  • Schedule: ["at any time"]
  • Branch name: renovate/jest-monorepo
  • Merge into: main
  • Upgrade @types/jest to 29.5.14
chore(deps): update dependency @​types/node to v18.19.130
  • Schedule: ["at any time"]
  • Branch name: renovate/node-18.x-lockfile
  • Merge into: main
  • Upgrade @types/node to 18.19.130
chore(deps): update dependency @​types/shelljs to v0.8.17
  • Schedule: ["at any time"]
  • Branch name: renovate/shelljs-0.x-lockfile
  • Merge into: main
  • Upgrade @types/shelljs to 0.8.17
chore(deps): update dependency @​types/webpack to v4.41.40
  • Schedule: ["at any time"]
  • Branch name: renovate/webpack-4.x
  • Merge into: main
  • Upgrade @types/webpack to 4.41.40
chore(deps): update dependency com.dotcms:starter to v20240807
  • Schedule: ["at any time"]
  • Branch name: renovate/starter.deploy.version
  • Merge into: main
  • Upgrade com.dotcms:starter to 20240807
chore(deps): update dependency eslint to v8.57.1
  • Schedule: ["at any time"]
  • Branch name: renovate/eslint-monorepo
  • Merge into: main
  • Upgrade eslint to 8.57.1
chore(deps): update dependency eslint-config-prettier to v9.1.2
  • Schedule: ["at any time"]
  • Branch name: renovate/eslint-config-prettier-9.x
  • Merge into: main
  • Upgrade eslint-config-prettier to 9.1.2
chore(deps): update dependency eslint-plugin-jsx-a11y to v6.10.2
  • Schedule: ["at any time"]
  • Branch name: renovate/eslint-plugin-jsx-a11y-6.x
  • Merge into: main
  • Upgrade eslint-plugin-jsx-a11y to 6.10.2
chore(deps): update dependency glob to v3.2.11
  • Schedule: ["at any time"]
  • Branch name: renovate/glob-3.x
  • Merge into: main
  • Upgrade glob to 3.2.11
chore(deps): update dependency intern-geezer to v2.2.3
  • Schedule: ["at any time"]
  • Branch name: renovate/intern-geezer-2.x
  • Merge into: main
  • Upgrade intern-geezer to 2.2.3
chore(deps): update dependency io.karatelabs:karate-junit5 to v1.5.1
chore(deps): update dependency io.swagger.core.v3:swagger-maven-plugin to v2.2.40
chore(deps): update dependency jsgi-node to v0.3.3
  • Schedule: ["at any time"]
  • Branch name: renovate/jsgi-node-0.x
  • Merge into: main
  • Upgrade jsgi-node to 0.3.3
chore(deps): update dependency junit:junit to v3.8.2
  • Schedule: ["at any time"]
  • Branch name: renovate/junit-junit-3.x
  • Merge into: main
  • Upgrade junit:junit to 3.8.2
chore(deps): update dependency karma to v6.4.4
  • Schedule: ["at any time"]
  • Branch name: renovate/karma-6.x
  • Merge into: main
  • Upgrade karma to 6.4.4
chore(deps): update dependency maven to v3.9.11
  • Schedule: ["at any time"]
  • Branch name: renovate/maven-3.x
  • Merge into: main
  • Upgrade maven to 3.9.11
chore(deps): update dependency octokit to v3.2.2
  • Schedule: ["at any time"]
  • Branch name: renovate/octokit-monorepo
  • Merge into: main
  • Upgrade octokit to 3.2.2
chore(deps): update dependency org.apache.felix:maven-bundle-plugin to v5.1.9
chore(deps): update dependency org.apache.maven.plugins:maven-deploy-plugin to v3.1.4
chore(deps): update dependency org.apache.maven.plugins:maven-install-plugin to v3.1.4
chore(deps): update dependency org.apache.maven.plugins:maven-site-plugin to v4.0.0-m16
chore(deps): update dependency org.codehaus.cargo:cargo-maven3-plugin to v1.10.24
chore(deps): update dependency ts-node to v10.9.2
  • Schedule: ["at any time"]
  • Branch name: renovate/ts-node-10.x
  • Merge into: main
  • Upgrade ts-node to 10.9.2
chore(deps): update dependency y-protocols to v1.0.6
  • Schedule: ["at any time"]
  • Branch name: renovate/y-protocols-1.x
  • Merge into: main
  • Upgrade y-protocols to 1.0.6
chore(deps): update dorny/paths-filter action to v3.0.2
  • Schedule: ["at any time"]
  • Branch name: renovate/dorny-paths-filter-3.x
  • Merge into: main
  • Upgrade dorny/paths-filter to v3.0.2
chore(deps): update opensearchproject/opensearch docker tag to v1.3.20
  • Schedule: ["at any time"]
  • Branch name: renovate/opensearchproject-opensearch-1.x
  • Merge into: main
  • Upgrade opensearchproject/opensearch to 1.3.20
chore(deps): update react monorepo
chore(deps): update redis docker tag to v6.2.12
  • Schedule: ["at any time"]
  • Branch name: renovate/redis-6.x
  • Merge into: main
  • Upgrade redis to 6.2.12-bullseye
chore(deps): update version.jococo.plugin to v0.8.14
fix(deps): update angular monorepo
fix(deps): update angular-cli monorepo to v19.2.19
fix(deps): update dependency @​angular/cdk to v19.2.19
  • Schedule: ["at any time"]
  • Branch name: renovate/angularmaterial-monorepo
  • Merge into: main
  • Upgrade @angular/cdk to 19.2.19
fix(deps): update dependency biz.aqute.bnd:biz.aqute.bndlib to v6.4.1
fix(deps): update dependency com.amazonaws:aws-java-sdk-bom to v1.12.793
fix(deps): update dependency com.dotcms.lib:dot.sslext to v1.2_2
  • Schedule: ["at any time"]
  • Branch name: renovate/com.dotcms.lib-dot.sslext-1.x
  • Merge into: main
  • Upgrade com.dotcms.lib:dot.sslext to 1.2_2
fix(deps): update dependency com.github.ben-manes.caffeine:caffeine to v2.9.3
fix(deps): update dependency com.microsoft.sqlserver:mssql-jdbc to v7.4.1.jre12
fix(deps): update dependency com.pgvector:pgvector to v0.1.6
  • Schedule: ["at any time"]
  • Branch name: renovate/com.pgvector-pgvector-0.x
  • Merge into: main
  • Upgrade com.pgvector:pgvector to 0.1.6
fix(deps): update dependency com.sun.mail:jakarta.mail to v1.6.8
  • Schedule: ["at any time"]
  • Branch name: renovate/com.sun.mail-jakarta.mail-1.x
  • Merge into: main
  • Upgrade com.sun.mail:jakarta.mail to 1.6.8
fix(deps): update dependency com.thoughtworks.xstream:xstream to v1.4.21
fix(deps): update dependency com.zaxxer:hikaricp to v3.4.5
  • Schedule: ["at any time"]
  • Branch name: renovate/com.zaxxer-hikaricp-3.x
  • Merge into: main
  • Upgrade com.zaxxer:HikariCP to 3.4.5
fix(deps): update dependency dijit to v1.17.3
  • Schedule: ["at any time"]
  • Branch name: renovate/dijit-1.x
  • Merge into: main
  • Upgrade dijit to 1.17.3
fix(deps): update dependency dojo to v1.17.3
  • Schedule: ["at any time"]
  • Branch name: renovate/dojo-1.x
  • Merge into: main
  • Upgrade dojo to 1.17.3
fix(deps): update dependency fop:fop to v0.20.5
  • Schedule: ["at any time"]
  • Branch name: renovate/fop-fop-0.x
  • Merge into: main
  • Upgrade fop:fop to 0.20.5
fix(deps): update dependency io.vavr:vavr to v0.10.7
  • Schedule: ["at any time"]
  • Branch name: renovate/io.vavr-vavr-0.x
  • Merge into: main
  • Upgrade io.vavr:vavr to 0.10.7
fix(deps): update dependency jakarta.inject:jakarta.inject-api to v1.0.5
fix(deps): update dependency org.apache.felix:org.apache.felix.configadmin to v1.9.26
fix(deps): update dependency org.apache.httpcomponents:httpclient to v4.5.14
fix(deps): update dependency org.apache.pdfbox:pdfbox to v2.0.35
  • Schedule: ["at any time"]
  • Branch name: renovate/org.apache.pdfbox-pdfbox-2.x
  • Merge into: main
  • Upgrade org.apache.pdfbox:pdfbox to 2.0.35
fix(deps): update dependency org.aspectj:aspectjrt to v1.9.24
  • Schedule: ["at any time"]
  • Branch name: renovate/org.aspectj-aspectjrt-1.x
  • Merge into: main
  • Upgrade org.aspectj:aspectjrt to 1.9.24
fix(deps): update dependency org.jetbrains:annotations to v16.0.3
  • Schedule: ["at any time"]
  • Branch name: renovate/org.jetbrains-annotations-16.x
  • Merge into: main
  • Upgrade org.jetbrains:annotations to 16.0.3
fix(deps): update dependency org.postgresql:postgresql to v42.7.8
  • Schedule: ["at any time"]
  • Branch name: renovate/org.postgresql-postgresql-42.x
  • Merge into: main
  • Upgrade org.postgresql:postgresql to 42.7.8
fix(deps): update dependency org.slf4j:slf4j-api to v2.0.17
  • Schedule: ["at any time"]
  • Branch name: renovate/slf4j-monorepo
  • Merge into: main
  • Upgrade org.slf4j:slf4j-api to 2.0.17
fix(deps): update dependency primeng to v17.18.15
  • Schedule: ["at any time"]
  • Branch name: renovate/primeng-17.x
  • Merge into: main
  • Upgrade primeng to 17.18.15
fix(deps): update dependency redis.clients:jedis to v4.4.8
  • Schedule: ["at any time"]
  • Branch name: renovate/redis.clients-jedis-4.x
  • Merge into: main
  • Upgrade redis.clients:jedis to 4.4.8
fix(deps): update dependency xmlpull:xmlpull to v1.1.3.4a
  • Schedule: ["at any time"]
  • Branch name: renovate/xmlpull-xmlpull-1.x
  • Merge into: main
  • Upgrade xmlpull:xmlpull to 1.1.3.4a
fix(deps): update graalvm.version to v22.3.5
fix(deps): update storybook monorepo
fix(deps): update swagger.version to v2.2.40
fix(deps): update tomcat.version to v9.0.111
  • Schedule: ["at any time"]
  • Branch name: renovate/tomcat.version
  • Merge into: main
  • Upgrade org.apache.tomcat:tomcat-catalina to 9.0.111
  • Upgrade org.apache.tomcat:tomcat-jdbc to 9.0.111
  • Upgrade org.apache.tomcat:tomcat-jasper to 9.0.111
chore(deps): update aarcangeli/load-dotenv action to v1.1.0
  • Schedule: ["at any time"]
  • Branch name: renovate/aarcangeli-load-dotenv-1.x
  • Merge into: main
  • Upgrade aarcangeli/load-dotenv to v1.1.0
chore(deps): update alpine docker tag to v3.22
  • Schedule: ["at any time"]
  • Branch name: renovate/alpine-3.x
  • Merge into: main
  • Upgrade alpine to 3.22
chore(deps): update appbaseio/dejavu docker tag to v3.10.0
  • Schedule: ["at any time"]
  • Branch name: renovate/appbaseio-dejavu-3.x
  • Merge into: main
  • Upgrade appbaseio/dejavu to 3.10.0
chore(deps): update cubejs/cube docker tag to v0.36.11
  • Schedule: ["at any time"]
  • Branch name: renovate/cubejs-cube-0.x
  • Merge into: main
  • Upgrade cubejs/cube to v0.36.11
chore(deps): update dependency @​actions/core to v1.11.1
  • Schedule: ["at any time"]
  • Branch name: renovate/actions-core-1.x-lockfile
  • Merge into: main
  • Upgrade @actions/core to 1.11.1
chore(deps): update dependency @faker-js/faker to v9.9.0
  • Schedule: ["at any time"]
  • Branch name: renovate/faker-js-faker-9.x
  • Merge into: main
  • Upgrade @faker-js/faker to 9.9.0
chore(deps): update dependency @testing-library/react to v16.3.0
  • Schedule: ["at any time"]
  • Branch name: renovate/testing-library-monorepo
  • Merge into: main
  • Upgrade @testing-library/react to 16.3.0
chore(deps): update dependency @​types/googlemaps to v3.43.3
  • Schedule: ["at any time"]
  • Branch name: renovate/googlemaps-3.x
  • Merge into: main
  • Upgrade @types/googlemaps to 3.43.3
chore(deps): update dependency @​types/jasmine to v4.6.5
  • Schedule: ["at any time"]
  • Branch name: renovate/jasmine-4.x
  • Merge into: main
  • Upgrade @types/jasmine to 4.6.5
chore(deps): update dependency @​vercel/ncc to ^0.38.0
  • Schedule: ["at any time"]
  • Branch name: renovate/vercel-ncc-0.x
  • Merge into: main
  • Upgrade @vercel/ncc to ^0.38.0
chore(deps): update dependency com.diffplug.spotless:spotless-maven-plugin to v2.46.1
chore(deps): update dependency com.github.eirslett:frontend-maven-plugin to v1.15.4
chore(deps): update dependency com.puppycrawl.tools:checkstyle to v10.26.1
chore(deps): update dependency esbuild to ^0.25.0
  • Schedule: ["at any time"]
  • Branch name: renovate/esbuild-0.x
  • Merge into: main
  • Upgrade esbuild to ^0.25.0
chore(deps): update dependency eslint-config-next to v14.2.33
  • Schedule: ["at any time"]
  • Branch name: renovate/nextjs-monorepo
  • Merge into: main
  • Upgrade eslint-config-next to 14.2.33
chore(deps): update dependency eslint-plugin-import to v2.32.0
  • Schedule: ["at any time"]
  • Branch name: renovate/eslint-plugin-import-2.x
  • Merge into: main
  • Upgrade eslint-plugin-import to 2.32.0
chore(deps): update dependency eslint-plugin-playwright to ^0.22.0
  • Schedule: ["at any time"]
  • Branch name: renovate/eslint-plugin-playwright-0.x
  • Merge into: main
  • Upgrade eslint-plugin-playwright to ^0.22.0
chore(deps): update dependency eslint-plugin-react to v7.37.5
  • Schedule: ["at any time"]
  • Branch name: renovate/eslint-plugin-react-7.x
  • Merge into: main
  • Upgrade eslint-plugin-react to 7.37.5
chore(deps): update dependency formidable to v1.2.6
  • Schedule: ["at any time"]
  • Branch name: renovate/formidable-1.x
  • Merge into: main
  • Upgrade formidable to 1.2.6
chore(deps): update dependency info.picocli:picocli-codegen to v4.7.7
chore(deps): update dependency io.fabric8:docker-maven-plugin to v0.46.0
chore(deps): update dependency io.quarkus.bot:build-reporter-maven-extension to v3.12.1
chore(deps): update dependency jasmine-core to v4.6.1
  • Schedule: ["at any time"]
  • Branch name: renovate/jasmine-monorepo
  • Merge into: main
  • Upgrade jasmine-core to 4.6.1
chore(deps): update dependency jest-preset-angular to v14.6.2
  • Schedule: ["at any time"]
  • Branch name: renovate/jest-preset-angular-14.x
  • Merge into: main
  • Upgrade jest-preset-angular to 14.6.2
chore(deps): update dependency jiti to v2.6.1
  • Schedule: ["at any time"]
  • Branch name: renovate/jiti-2.x
  • Merge into: main
  • Upgrade jiti to 2.6.1
chore(deps): update dependency karma-jasmine-html-reporter to v2.1.0
  • Schedule: ["at any time"]
  • Branch name: renovate/karma-jasmine-html-reporter-2.x
  • Merge into: main
  • Upgrade karma-jasmine-html-reporter to 2.1.0
chore(deps): update dependency maven-wrapper to v3.3.4
  • Schedule: ["at any time"]
  • Branch name: renovate/maven-wrapper-3.x
  • Merge into: main
  • Upgrade maven-wrapper to 3.3.4
chore(deps): update dependency monaco-editor to ^0.54.0
  • Schedule: ["at any time"]
  • Branch name: renovate/monaco-editor-0.x
  • Merge into: main
  • Upgrade monaco-editor to ^0.54.0
chore(deps): update dependency node to v16.20.2
  • Schedule: ["at any time"]
  • Branch name: renovate/node-16.x
  • Merge into: main
  • Upgrade node to 16.20.2
chore(deps): update dependency org.apache.maven.plugins:maven-antrun-plugin to v3.2.0
chore(deps): update dependency org.apache.maven.plugins:maven-assembly-plugin to v3.7.1
chore(deps): update dependency org.apache.maven.plugins:maven-assembly-plugin to v3.7.1
chore(deps): update dependency org.apache.maven.plugins:maven-checkstyle-plugin to v3.6.0
chore(deps): update dependency org.apache.maven.plugins:maven-clean-plugin to v3.5.0
chore(deps): update dependency org.apache.maven.plugins:maven-compiler-plugin to v3.14.1
chore(deps): update dependency org.apache.maven.plugins:maven-dependency-plugin to v3.9.0
chore(deps): update dependency org.apache.maven.plugins:maven-enforcer-plugin to v3.6.2
chore(deps): update dependency org.apache.maven.plugins:maven-failsafe-plugin to v3.5.4
chore(deps): update dependency org.apache.maven.plugins:maven-gpg-plugin to v3.2.8
chore(deps): update dependency org.apache.maven.plugins:maven-help-plugin to v3.5.1
chore(deps): update dependency org.apache.maven.plugins:maven-jar-plugin to v3.4.2
chore(deps): update dependency org.apache.maven.plugins:maven-jar-plugin to v3.4.2
chore(deps): update dependency org.apache.maven.plugins:maven-javadoc-plugin to v3.12.0
chore(deps): update dependency org.apache.maven.plugins:maven-jxr-plugin to v3.6.0
chore(deps): update dependency org.apache.maven.plugins:maven-plugin-plugin to v3.15.2
chore(deps): update dependency org.apache.maven.plugins:maven-project-info-reports-plugin to v3.9.0
chore(deps): update dependency org.apache.maven.plugins:maven-shade-plugin to v3.6.1
chore(deps): update dependency org.apache.maven.plugins:maven-source-plugin to v3.3.1
chore(deps): update dependency org.apache.maven.plugins:maven-surefire-report-plugin to v3.5.4
chore(deps): update dependency org.apache.maven.plugins:maven-war-plugin to v3.5.0
chore(deps): update dependency org.codehaus.mojo:build-helper-maven-plugin to v3.6.1
chore(deps): update dependency org.codehaus.mojo:buildnumber-maven-plugin to v3.2.1
chore(deps): update dependency org.codehaus.mojo:exec-maven-plugin to v3.6.2
chore(deps): update dependency org.codehaus.mojo:flatten-maven-plugin to v1.7.3
chore(deps): update dependency org.codehaus.mojo:versions-maven-plugin to v2.19.1
chore(deps): update dependency org.hamcrest:hamcrest to v2.2
  • Schedule: ["at any time"]
  • Branch name: renovate/javahamcrest-monorepo
  • Merge into: main
  • Upgrade org.hamcrest:hamcrest to 2.2
chore(deps): update dependency org.jreleaser:jreleaser-maven-plugin to v1.21.0
chore(deps): update dependency org.openrewrite.maven:rewrite-maven-plugin to v5.47.3
chore(deps): update dependency org.openrewrite.recipe:rewrite-migrate-java to v2.31.1
chore(deps): update dependency org.owasp:dependency-check-maven to v8.4.3
chore(deps): update dependency postcss-preset-env to v7.8.3
  • Schedule: ["at any time"]
  • Branch name: renovate/postcss-preset-env-7.x
  • Merge into: main
  • Upgrade postcss-preset-env to 7.8.3
chore(deps): update dependency prettier to v3.6.2
  • Schedule: ["at any time"]
  • Branch name: renovate/prettier-3.x-lockfile
  • Merge into: main
  • Upgrade prettier to 3.6.2
chore(deps): update dependency prettier to v3.6.2
  • Schedule: ["at any time"]
  • Branch name: renovate/prettier-3.x
  • Merge into: main
  • Upgrade prettier to 3.6.2
chore(deps): update dependency puppeteer to ~5.5.0
  • Schedule: ["at any time"]
  • Branch name: renovate/puppeteer
  • Merge into: main
  • Upgrade puppeteer to ~5.5.0
chore(deps): update dependency python to 3.14
  • Schedule: ["at any time"]
  • Branch name: renovate/python-3.x
  • Merge into: main
  • Upgrade python to 3.14
chore(deps): update dependency sinon to v1.17.7
  • Schedule: ["at any time"]
  • Branch name: renovate/sinon-1.x
  • Merge into: main
  • Upgrade sinon to 1.17.7
chore(deps): update dependency stylus to v0.64.0
  • Schedule: ["at any time"]
  • Branch name: renovate/stylus-0.x
  • Merge into: main
  • Upgrade stylus to 0.64.0
chore(deps): update dependency ts-jest to v29.4.5
  • Schedule: ["at any time"]
  • Branch name: renovate/ts-jest-29.x-lockfile
  • Merge into: main
  • Upgrade ts-jest to 29.4.5
chore(deps): update dependency ts-jest to v29.4.5
  • Schedule: ["at any time"]
  • Branch name: renovate/ts-jest-29.x
  • Merge into: main
  • Upgrade ts-jest to 29.4.5
chore(deps): update dependency typedoc to ^0.28.0
  • Schedule: ["at any time"]
  • Branch name: renovate/typedoc-0.x
  • Merge into: main
  • Upgrade typedoc to ^0.28.0
chore(deps): update dependency typescript to v5.9.3
  • Schedule: ["at any time"]
  • Branch name: renovate/typescript-5.x-lockfile
  • Merge into: main
  • Upgrade typescript to 5.9.3
chore(deps): update dependency typescript to v5.9.3
  • Schedule: ["at any time"]
  • Branch name: renovate/typescript-5.x
  • Merge into: main
  • Upgrade typescript to 5.9.3
chore(deps): update dependency verdaccio to v6.2.1
  • Schedule: ["at any time"]
  • Branch name: renovate/verdaccio-6.x
  • Merge into: main
  • Upgrade verdaccio to 6.2.1
chore(deps): update dependency y-prosemirror to v1.3.7
  • Schedule: ["at any time"]
  • Branch name: renovate/y-prosemirror-1.x
  • Merge into: main
  • Upgrade y-prosemirror to 1.3.7
chore(deps): update dependency yjs to v13.6.27
  • Schedule: ["at any time"]
  • Branch name: renovate/yjs-13.x
  • Merge into: main
  • Upgrade yjs to 13.6.27
chore(deps): update docker/build-push-action action to v6.18.0
  • Schedule: ["at any time"]
  • Branch name: renovate/docker-build-push-action-6.x
  • Merge into: main
  • Upgrade docker/build-push-action to v6.18.0
chore(deps): update docker/login-action action to v3.6.0
  • Schedule: ["at any time"]
  • Branch name: renovate/docker-login-action-3.x
  • Merge into: main
  • Upgrade docker/login-action to v3.6.0
chore(deps): update docker/setup-buildx-action action to v3.11.1
  • Schedule: ["at any time"]
  • Branch name: renovate/docker-setup-buildx-action-3.x
  • Merge into: main
  • Upgrade docker/setup-buildx-action to v3.11.1
chore(deps): update grafana/grafana docker tag to v10.4.19
  • Schedule: ["at any time"]
  • Branch name: renovate/grafana-monorepo
  • Merge into: main
  • Upgrade grafana/grafana to 10.4.19
chore(deps): update jamesives/github-pages-deploy-action action to v4.7.3
chore(deps): update mikefarah/yq action to v4.48.1
  • Schedule: ["at any time"]
  • Branch name: renovate/mikefarah-yq-4.x
  • Merge into: main
  • Upgrade mikefarah/yq to v4.48.1
chore(deps): update node.js to v22.21.1
  • Schedule: ["at any time"]
  • Branch name: renovate/node-22.x
  • Merge into: main
  • Upgrade node to 22.21.1
chore(deps): update postgres docker tag to v13.22
  • Schedule: ["at any time"]
  • Branch name: renovate/postgres-13.x
  • Merge into: main
  • Upgrade postgres to 13.22
chore(deps): update prom/prometheus docker tag to v2.55.1
  • Schedule: ["at any time"]
  • Branch name: renovate/prom-prometheus-2.x
  • Merge into: main
  • Upgrade prom/prometheus to v2.55.1
chore(deps): update re

@spbolton spbolton requested a review from a team as a code owner February 21, 2025 01:07
@renovate renovate bot force-pushed the renovate/configure branch from 2c2a877 to 91b2ec3 Compare February 21, 2025 01:07
@renovate renovate bot force-pushed the renovate/configure branch 2 times, most recently from c7d0558 to 72e173e Compare April 9, 2025 08:38
@renovate renovate bot force-pushed the renovate/configure branch 7 times, most recently from 5731330 to 03f63c8 Compare April 23, 2025 09:53
@renovate renovate bot force-pushed the renovate/configure branch 3 times, most recently from d396500 to 3c65996 Compare April 27, 2025 08:02
@renovate renovate bot force-pushed the renovate/configure branch from 3c65996 to 11abdc8 Compare May 20, 2025 11:39
@renovate renovate bot force-pushed the renovate/configure branch 7 times, most recently from 297b46a to 22b67fc Compare May 25, 2025 00:19
@renovate renovate bot force-pushed the renovate/configure branch 3 times, most recently from 411df90 to 6e9b5f1 Compare May 29, 2025 12:16
@renovate renovate bot force-pushed the renovate/configure branch 3 times, most recently from 393b98e to 27033ef Compare July 17, 2025 10:40
@github-actions
Copy link

❌ Issue Linking Required

This PR could not be linked to an issue. All PRs must be linked to an issue for tracking purposes.

How to fix this:

Option 1: Link via GitHub UI (Recommended)

  1. Go to the PR → Development section (right sidebar)
  2. Click "Link issue" and select an existing issue

Option 2: Add keyword to PR body
Edit this PR description and add one of these lines:

  • This PR fixes: #123
  • This PR closes: #123
  • This PR resolves: #123

Option 3: Use branch naming
Create a new branch with one of these patterns:

  • 123-feature-description (number at start)
  • issue-123-feature-description (issue-number at start)
  • feature-issue-123 (issue-number anywhere)

Why is this required?

Issue linking ensures proper tracking, documentation, and helps maintain project history. It connects your code changes to the problem they solve.


This comment was automatically generated by the issue linking workflow

@renovate renovate bot force-pushed the renovate/configure branch from 27033ef to 30cd67e Compare July 17, 2025 10:46
@github-actions
Copy link

❌ Issue Linking Required

This PR could not be linked to an issue. All PRs must be linked to an issue for tracking purposes.

How to fix this:

Option 1: Link via GitHub UI (Recommended)

  1. Go to the PR → Development section (right sidebar)
  2. Click "Link issue" and select an existing issue

Option 2: Add keyword to PR body
Edit this PR description and add one of these lines:

  • This PR fixes: #123
  • This PR closes: #123
  • This PR resolves: #123

Option 3: Use branch naming
Create a new branch with one of these patterns:

  • 123-feature-description (number at start)
  • issue-123-feature-description (issue-number at start)
  • feature-issue-123 (issue-number anywhere)

Why is this required?

Issue linking ensures proper tracking, documentation, and helps maintain project history. It connects your code changes to the problem they solve.


This comment was automatically generated by the issue linking workflow

@renovate renovate bot force-pushed the renovate/configure branch from 30cd67e to a1f4ff1 Compare July 17, 2025 10:51
@github-actions
Copy link

❌ Issue Linking Required

This PR could not be linked to an issue. All PRs must be linked to an issue for tracking purposes.

How to fix this:

Option 1: Add keyword to PR body (Recommended - auto-removes this comment)
Edit this PR description and add one of these lines:

  • This PR fixes: #123
  • This PR closes: #123
  • This PR resolves: #123

Option 2: Link via GitHub UI (Note: won't clear the failed check)

  1. Go to the PR → Development section (right sidebar)

  2. Click "Link issue" and select an existing issue

  3. Push a new commit or re-run the workflow to clear the failed check
    Option 3: Use branch naming
    Create a new branch with one of these patterns:

  • 123-feature-description (number at start)

  • issue-123-feature-description (issue-number at start)

  • feature-issue-123 (issue-number anywhere)

Why is this required?

Issue linking ensures proper tracking, documentation, and helps maintain project history. It connects your code changes to the problem they solve.
---This comment was automatically generated by the issue linking workflow

@renovate renovate bot force-pushed the renovate/configure branch from a1f4ff1 to 20b0115 Compare July 17, 2025 10:57
@github-actions
Copy link

❌ Issue Linking Required

This PR could not be linked to an issue. All PRs must be linked to an issue for tracking purposes.

How to fix this:

Option 1: Add keyword to PR body (Recommended - auto-removes this comment)
Edit this PR description and add one of these lines:

  • This PR fixes: #123
  • This PR closes: #123
  • This PR resolves: #123

Option 2: Link via GitHub UI (Note: won't clear the failed check)

  1. Go to the PR → Development section (right sidebar)

  2. Click "Link issue" and select an existing issue

  3. Push a new commit or re-run the workflow to clear the failed check
    Option 3: Use branch naming
    Create a new branch with one of these patterns:

  • 123-feature-description (number at start)

  • issue-123-feature-description (issue-number at start)

  • feature-issue-123 (issue-number anywhere)

Why is this required?

Issue linking ensures proper tracking, documentation, and helps maintain project history. It connects your code changes to the problem they solve.
---This comment was automatically generated by the issue linking workflow

@renovate renovate bot force-pushed the renovate/configure branch 8 times, most recently from 9e6f180 to 18dd015 Compare August 23, 2025 06:45
@renovate renovate bot force-pushed the renovate/configure branch from 18dd015 to 62d47fd Compare September 5, 2025 02:13
@renovate renovate bot force-pushed the renovate/configure branch 8 times, most recently from 3ac440f to 761112f Compare September 27, 2025 03:34
@renovate renovate bot force-pushed the renovate/configure branch from 761112f to 76333e5 Compare September 27, 2025 03:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants