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

Configure Renovate #113

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Configure Renovate #113

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Apr 8, 2024

Mend Renovate

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/node.js.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
  • 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 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.

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

Update dependency semantic-release to v19 [SECURITY]
  • Branch name: renovate/npm-semantic-release-vulnerability
  • Merge into: master
  • Upgrade semantic-release to ^19.0.0
Update dependency nock to v13.5.4
  • Schedule: ["at any time"]
  • Branch name: renovate/nock-13.x-lockfile
  • Merge into: master
  • Upgrade nock to 13.5.4
Update dependency node-fetch to v2.7.0
  • Schedule: ["at any time"]
  • Branch name: renovate/node-fetch-2.x-lockfile
  • Merge into: master
  • Upgrade node-fetch to 2.7.0
Update actions/checkout action to v4
  • Schedule: ["at any time"]
  • Branch name: renovate/actions-checkout-4.x
  • Merge into: master
  • Upgrade actions/checkout to v4
Update actions/setup-node action to v4
  • Schedule: ["at any time"]
  • Branch name: renovate/actions-setup-node-4.x
  • Merge into: master
  • Upgrade actions/setup-node to v4
Update dependency @semantic-release/git to v10
  • Schedule: ["at any time"]
  • Branch name: renovate/major-semantic-release-monorepo
  • Merge into: master
  • Upgrade @semantic-release/git to ^10.0.0
Update dependency conventional-changelog-eslint to v5
  • Schedule: ["at any time"]
  • Branch name: renovate/conventional-changelog-eslint-5.x
  • Merge into: master
  • Upgrade conventional-changelog-eslint to ^5.0.0
Update dependency eslint to v9
  • Schedule: ["at any time"]
  • Branch name: renovate/eslint-9.x
  • Merge into: master
  • Upgrade eslint to ^9.0.0
Update dependency get-port to v7
  • Schedule: ["at any time"]
  • Branch name: renovate/get-port-7.x
  • Merge into: master
  • Upgrade get-port to ^7.0.0
Update dependency mocha to v10
  • Schedule: ["at any time"]
  • Branch name: renovate/mocha-10.x
  • Merge into: master
  • Upgrade mocha to ^10.0.0
Update dependency node-fetch to v3
  • Schedule: ["at any time"]
  • Branch name: renovate/node-fetch-3.x
  • Merge into: master
  • Upgrade node-fetch to ^3.0.0
Update dependency rewire to v7
  • Schedule: ["at any time"]
  • Branch name: renovate/rewire-7.x
  • Merge into: master
  • Upgrade rewire to ^7.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 has been generated by Mend Renovate. View repository job log here.

@adobe-bot
Copy link

🎉 Sizewatcher congratulates on the size improvement 📉:

   🎉 git -67.6% (714 kB => 231 kB)

node_modules has no changes (74.8 MB)
Largest production node modules:
┌──────────────────┬────────────┬───────┐
│ name │ children │ size │
├──────────────────┼────────────┼───────┤
│ node-fetch │ 0 │ 0.14M │
├──────────────────┼────────────┼───────┤
│ abort-controller │ 0 │ 0.07M │
├──────────────────┼────────────┼───────┤
│ 2 modules │ 0 children │ 0.22M │
└──────────────────┴────────────┴───────┘
npm_package +0.9% (11.5 kB => 11.6 kB)
Package contents:
npm WARN publish npm auto-corrected some errors in your package.json when publishing.  Please run "npm pkg fix" to address these errors.
npm WARN publish errors corrected:
npm WARN publish "repository" was changed from a string to an object
npm WARN publish "repository.url" was normalized to "git+https://github.com/adobe/node-fetch-retry.git"

📦 @adobe/[email protected]
=== Tarball Contents ===
850B .releaserc.json
3.2kB CODE_OF_CONDUCT.md
171B COPYRIGHT
11.3kB LICENSE
7.0kB README.md
555B index.d.ts
12.5kB index.js
1.1kB package.json
114B renovate.json
=== Tarball Details ===
name: @adobe/node-fetch-retry
version: 2.2.0
filename: adobe-node-fetch-retry-2.2.0.tgz
package size: 11.6 kB
unpacked size: 37.0 kB
shasum: 22e11bf5258911c805bf9d9782eb63d429fe31c8
integrity: sha512-UVyFPDBD1FLF+[...]bNFH6tirwyaUQ==
total files: 9

npm WARN This command requires you to be logged in to https://registry.npmjs.org/ (dry-run)
Publishing to https://registry.npmjs.org/ with tag latest and default access (dry-run)
Notes
  • PR branch: renovate/configure @ 0fbfd39
  • Base branch: master
  • Sizewatcher v1.3.0
  • Effective Configuration:
limits:
  fail: 100%
  warn: 30%
  ok: '-10%'
report:
  githubComment: true
  githubStatus: false
comparators: {}

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.

1 participant