Skip to content
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.

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

chore: Configure Renovate #1

Closed
wants to merge 1 commit into from
Closed

chore: Configure Renovate #1

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Feb 13, 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

  • .github/workflows/build.yml (github-actions)
  • .github/workflows/deploy.yml (github-actions)
  • 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.
  • Apply crowd-sourced package replacement rules.
  • Apply crowd-sourced workarounds for known problems with packages.
  • Pin dependency versions for development dependencies and retain SemVer ranges for others.
  • If automerging, push the new commit directly to the base branch (no PR).
  • Automerge patch and minor upgrades if they pass tests.
  • Enable Renovate Dependency Dashboard creation.
  • Apply label renovate to PRs.
  • Wait for branch tests to pass or fail before creating the PR.
  • Rebase existing PRs any time the base branch has been updated.
  • Apply crowd-sourced package replacement rules.

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

chore(deps): update dependency vite to v5.4.12 [security]
  • Branch name: renovate/npm-vite-vulnerability
  • Merge into: main
  • Upgrade vite to 5.4.12
chore(deps): pin dependencies
chore(deps): update dependency vue to ^3.5.11
  • Schedule: ["at any time"]
  • Branch name: renovate/vue-monorepo
  • Merge into: main
  • Upgrade vue to ^3.5.11
chore(deps): update dependency @​types/node to ^20.16.10
  • Schedule: ["at any time"]
  • Branch name: renovate/node-20.x
  • Merge into: main
  • Upgrade @types/node to ^20.16.10
chore(deps): update dependency @​vitejs/plugin-vue to ^5.2.1
  • Schedule: ["at any time"]
  • Branch name: renovate/vitejs-plugin-vue-5.x
  • Merge into: main
  • Upgrade @vitejs/plugin-vue to ^5.2.1
chore(deps): update dependency @​vue/tsconfig to ^0.7.0
  • Schedule: ["at any time"]
  • Branch name: renovate/vue-tsconfig-0.x
  • Merge into: main
  • Upgrade @vue/tsconfig to ^0.7.0
chore(deps): update dependency sass to ^1.84.0
  • Schedule: ["at any time"]
  • Branch name: renovate/sass-1.x
  • Merge into: main
  • Upgrade sass to ^1.84.0
chore(deps): update dependency typescript to ~5.7.0
  • Schedule: ["at any time"]
  • Branch name: renovate/typescript-5.x
  • Merge into: main
  • Upgrade typescript to ~5.7.0
chore(deps): update dependency vue-tsc to ^2.2.0
  • Schedule: ["at any time"]
  • Branch name: renovate/vue-tsc-2.x
  • Merge into: main
  • Upgrade vue-tsc to ^2.2.0
chore(deps): update dependency @​types/node to v22
  • Schedule: ["at any time"]
  • Branch name: renovate/node-22.x
  • Merge into: main
  • Upgrade @types/node to ^22.0.0
feat(deps): update dependency @​fkui/date to v6
  • Schedule: ["at any time"]
  • Branch name: renovate/fkui-date-6.x
  • Merge into: main
  • Upgrade @fkui/date to ^6.0.0
feat(deps): update dependency @​fkui/design to v6
  • Schedule: ["at any time"]
  • Branch name: renovate/fkui-design-6.x
  • Merge into: main
  • Upgrade @fkui/design to ^6.0.0
feat(deps): update dependency @​fkui/icon-lib-default to v6
  • Schedule: ["at any time"]
  • Branch name: renovate/fkui-icon-lib-default-6.x
  • Merge into: main
  • Upgrade @fkui/icon-lib-default to ^6.0.0
feat(deps): update dependency @​fkui/logic to v6
  • Schedule: ["at any time"]
  • Branch name: renovate/fkui-logic-6.x
  • Merge into: main
  • Upgrade @fkui/logic to ^6.0.0
feat(deps): update dependency @​fkui/vue to v6
  • Schedule: ["at any time"]
  • Branch name: renovate/fkui-vue-6.x
  • Merge into: main
  • Upgrade @fkui/vue to ^6.0.0

🚸 Branch 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.

@renovate renovate bot added the renovate label Feb 13, 2025
@ext
Copy link

ext commented Feb 13, 2025

@MCFK jag tror du slog på renovate globalt på alla repon inkl de som inte är våra

@MCFK
Copy link
Collaborator

MCFK commented Feb 13, 2025

@MCFK jag tror du slog på renovate globalt på alla repon inkl de som inte är våra

Spännande, då har jag några PR´s att stänga nu då :)

@MCFK MCFK closed this Feb 13, 2025
Copy link
Author

renovate bot commented Feb 13, 2025

Renovate is disabled

Renovate is disabled because there is no Renovate configuration file. To enable Renovate, you can either (a) change this PR's title to get a new onboarding PR, and merge the new onboarding PR, or (b) create a Renovate config file, and commit that file to your base branch.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants