Skip to content

chore: Configure Renovate#8

Open
renovate[bot] wants to merge 1 commit intomainfrom
renovate/configure
Open

chore: Configure Renovate#8
renovate[bot] wants to merge 1 commit intomainfrom
renovate/configure

Conversation

@renovate
Copy link
Copy Markdown

@renovate renovate Bot commented Mar 17, 2026

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

  • .github/workflows/npm-publish-github-packages.yml (github-actions)
  • package.json (npm)
  • projects/shongo-calendar/package.json (npm)

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.
  • Ensure that every dependency pinned by digest and sourced from GitHub.com contains a link to the commit-to-commit diff
  • Correctly link to the source code for golang.org/x packages
  • Link to pkg.go.dev/... for golang.org/x packages' title

🔡 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 35 Pull Requests:

chore(deps): update dependency @​angular/common to v19 [security]
  • Branch name: renovate/npm-angular-common-vulnerability
  • Merge into: main
  • Upgrade @angular/common to ^19.0.0
chore(deps): update angular monorepo
chore(deps): update angular-cli monorepo to v16.2.16
chore(deps): update dependency bootstrap to v5.3.8
  • Schedule: ["at any time"]
  • Branch name: renovate/bootstrap-5.x-lockfile
  • Merge into: main
  • Upgrade bootstrap to 5.3.8
chore(deps): update dependency karma to v6.4.4
  • Schedule: ["at any time"]
  • Branch name: renovate/karma-6.x-lockfile
  • Merge into: main
  • Upgrade karma to 6.4.4
chore(deps): update dependency karma-coverage to v2.2.1
  • Schedule: ["at any time"]
  • Branch name: renovate/karma-coverage-2.x-lockfile
  • Merge into: main
  • Upgrade karma-coverage to 2.2.1
chore(deps): update dependency prettier-plugin-organize-imports to v3.2.4
  • Schedule: ["at any time"]
  • Branch name: renovate/prettier-plugin-organize-imports-3.x-lockfile
  • Merge into: main
  • Upgrade prettier-plugin-organize-imports to 3.2.4
chore(deps): update angular-eslint monorepo to v16.3.1
chore(deps): update dependency @​types/jasmine to ~4.6.0
  • Schedule: ["at any time"]
  • Branch name: renovate/jasmine-4.x
  • Merge into: main
  • Upgrade @types/jasmine to ~4.6.0
chore(deps): update dependency angular-calendar to v0.32.0
  • Schedule: ["at any time"]
  • Branch name: renovate/angular-calendar-0.x
  • Merge into: main
  • Upgrade angular-calendar to ^0.31.0 || ^0.32.0
  • Upgrade angular-calendar to ^0.32.0
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 jasmine-core to ~4.6.0
  • Schedule: ["at any time"]
  • Branch name: renovate/jasmine-monorepo
  • Merge into: main
  • Upgrade jasmine-core to ~4.6.0
chore(deps): update dependency karma-chrome-launcher to ~3.2.0
  • Schedule: ["at any time"]
  • Branch name: renovate/karma-chrome-launcher-3.x
  • Merge into: main
  • Upgrade karma-chrome-launcher to ~3.2.0
chore(deps): update dependency karma-jasmine-html-reporter to ~2.2.0
  • Schedule: ["at any time"]
  • Branch name: renovate/karma-jasmine-html-reporter-2.x
  • Merge into: main
  • Upgrade karma-jasmine-html-reporter to ~2.2.0
chore(deps): update dependency rxjs to ~7.8.0
  • Schedule: ["at any time"]
  • Branch name: renovate/rxjs-7.x
  • Merge into: main
  • Upgrade rxjs to ~7.8.0
chore(deps): update dependency stylelint to v15.11.0
  • Schedule: ["at any time"]
  • Branch name: renovate/stylelint-15.x-lockfile
  • Merge into: main
  • Upgrade stylelint to 15.11.0
chore(deps): update dependency stylelint-config-standard-scss to v11.1.0
  • Schedule: ["at any time"]
  • Branch name: renovate/stylelint-config-standard-scss-11.x-lockfile
  • Merge into: main
  • Upgrade stylelint-config-standard-scss to 11.1.0
chore(deps): update dependency tslib to v2.8.1
  • Schedule: ["at any time"]
  • Branch name: renovate/tslib-2.x-lockfile
  • Merge into: main
  • Upgrade tslib to 2.8.1
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 typescript-eslint monorepo to v6.21.0
chore(deps): update actions/checkout action to v6
  • Schedule: ["at any time"]
  • Branch name: renovate/actions-checkout-6.x
  • Merge into: main
  • Upgrade actions/checkout to v6
chore(deps): update actions/setup-node action to v6
  • Schedule: ["at any time"]
  • Branch name: renovate/actions-setup-node-6.x
  • Merge into: main
  • Upgrade actions/setup-node to v6
chore(deps): update angular monorepo to v21 (major)
chore(deps): update angular-cli monorepo to v21 (major)
chore(deps): update angular-eslint monorepo to v21 (major)
chore(deps): update dependency @​types/jasmine to v6
  • Schedule: ["at any time"]
  • Branch name: renovate/jasmine-6.x
  • Merge into: main
  • Upgrade @types/jasmine to ~6.0.0
chore(deps): update dependency eslint to v10
  • Schedule: ["at any time"]
  • Branch name: renovate/major-eslint-monorepo
  • Merge into: main
  • Upgrade eslint to ^10.0.0
chore(deps): update dependency jasmine-core to v6
  • Schedule: ["at any time"]
  • Branch name: renovate/major-jasmine-monorepo
  • Merge into: main
  • Upgrade jasmine-core to ~6.1.0
chore(deps): update dependency ng-packagr to v21
  • Schedule: ["at any time"]
  • Branch name: renovate/ng-packagr-21.x
  • Merge into: main
  • Upgrade ng-packagr to ^21.0.0
chore(deps): update dependency node to v24
  • Schedule: ["at any time"]
  • Branch name: renovate/node-24.x
  • Merge into: main
  • Upgrade node to 24
chore(deps): update dependency prettier-plugin-organize-imports to v4
chore(deps): update dependency stylelint to v17
  • Schedule: ["at any time"]
  • Branch name: renovate/stylelint-17.x
  • Merge into: main
  • Upgrade stylelint to ^17.0.0
chore(deps): update dependency stylelint-config-standard to v40
  • Schedule: ["at any time"]
  • Branch name: renovate/stylelint-config-standard-40.x
  • Merge into: main
  • Upgrade stylelint-config-standard to ^40.0.0
chore(deps): update dependency stylelint-config-standard-scss to v17
  • Schedule: ["at any time"]
  • Branch name: renovate/stylelint-config-standard-scss-17.x
  • Merge into: main
  • Upgrade stylelint-config-standard-scss to ^17.0.0
chore(deps): update typescript-eslint monorepo to v8 (major)

🚸 PR creation will be limited to maximum 2 per hour, so it doesn't swamp any CI resources or overwhelm the project. See docs for prHourlyLimit for details.


❓ Got questions? Check out Renovate's Docs, particularly the Getting Started section.
If you need any further assistance then you can also request help here.


This PR was generated by Mend Renovate. View the repository job log.

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