Configure Renovate

[ur-renovate]

Greetings. Renovate would like you to know that there's an update available for your consideration.

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/check-dist.yml (github-actions)
• .github/workflows/renovate.yaml (github-actions)
• .github/workflows/test.yaml (github-actions)
• .github/workflows/update-majorver.yaml (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
• Group known monorepo packages together.
• Use curated list of recommended non-monorepo package groupings.
• Apply crowd-sourced workarounds for known problems with packages.
• Disable automerging feature - wait for humans to merge all PRs.
• Run lock file maintenance (updates) early Monday mornings.
• Use semantic prefixes for commit messages and PR titles.
• Use semantic commit scope deps for all commits and PR titles.
• Enable Docker major updates.
• Pin Docker digests.
• Group various lint packages together.
• Pin github-action digests.
• Enable Docker Compose image updating.
• Upgrade Docker tags to newer versions.
• Reasonable software update defaults curated by @urcomputeringpal. From https://github.com/urcomputeringpal/.github/blob/main/default.json

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

chore(deps): pin dependencies

• Schedule: ["at any time"]
• Branch name: renovate/pin-dependencies
• Merge into: main
• Upgrade actions/checkout to c85c95e3d7251135ab7dc9ce3241c5835cc595a9
• Upgrade actions/setup-node to 64ed1c7eab4cce3362f8c340dee64e5eaeef8f7c
• Upgrade actions/upload-artifact to 0b7f8abb1508181956e8e162db84b466c27e18ce

chore(deps): update dependency @​types/node to v18.16.18

• Schedule: ["at any time"]
• Branch name: renovate/node-18.x-lockfile
• Merge into: main
• Upgrade @types/node to 18.16.18

chore(deps): update linters

• Schedule: ["at any time"]
• Branch name: renovate/linters
• Merge into: main
• Upgrade @typescript-eslint/parser to 5.59.11
• Upgrade eslint to 8.43.0
• Upgrade eslint-plugin-github to 4.8.0

chore(deps): update dependency typescript to v5.1.3

• Schedule: ["at any time"]
• Branch name: renovate/typescript-5.x-lockfile
• Merge into: main
• Upgrade typescript to 5.1.3

chore(deps): update dependency @​octokit/plugin-request-log to v3

• Schedule: ["at any time"]
• Branch name: renovate/octokit-plugin-request-log-3.x
• Merge into: main
• Upgrade @octokit/plugin-request-log to ^3.0.0

chore(deps): update dependency @​octokit/plugin-retry to v5

• Schedule: ["at any time"]
• Branch name: renovate/octokit-plugin-retry-5.x
• Merge into: main
• Upgrade @octokit/plugin-retry to ^5.0.0

chore(deps): lock file maintenance

• Schedule: ["before 4am on Monday"]
• Branch name: renovate/lock-file-maintenance
• Merge into: main
• Regenerate lock files to use latest dependency versions

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

---

Configuring renovate

• Repository config is loaded from renovate.json on the default branch.
• Defaults are inherited from urcomputeringpal/.github and optionally at the organization level.
• Optional self-hosted configuration is loaded from renovate.js on the default branch.
• Changes to configuration pushed to this pull request will be processed with a dry run of Renovate. Inspect the logs to validate if the changes have had the desired effect, then merge to apply them.