atom-json-editor

atom-json-editor copied to clipboard

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

• .circleci/config.yml (circleci)
• package.json (npm)

Configuration Summary

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

• Start dependency updates only once this onboarding PR is merged
• 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 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.

🔡 Would you like to change the way Renovate is upgrading your dependencies? Simply edit the renovate.json in this branch with your custom config and the list of Pull Requests in the "What to Expect" section below will be updated the next time Renovate runs.

---

What to Expect

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

chore(deps): update dependency @ls-age/bump-version to v0.2.1

• Schedule: ["at any time"]
• Branch name: renovate/ls-age-bump-version-0.x-lockfile
• Merge into: master
• Upgrade @ls-age/bump-version to 0.2.1

chore(deps): update node.js to v17

• Schedule: ["at any time"]
• Branch name: renovate/circleci-node-17.x
• Merge into: master
• Upgrade circleci/node to 17

---

❓ 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 has been generated by Mend Renovate. View repository job log here.

⚠️ No Changeset found

Latest commit: 37cb1f05c735a1b1f86d99c2e1daae0b3e4d4ffe

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR