Skip to content
This repository was archived by the owner on Jul 16, 2026. It is now read-only.

chore: Configure Renovate (Sebastian Software)#35

Open
jamesfastnerbot wants to merge 1 commit into
mainfrom
renovate/configure
Open

chore: Configure Renovate (Sebastian Software)#35
jamesfastnerbot wants to merge 1 commit into
mainfrom
renovate/configure

Conversation

@jamesfastnerbot

Copy link
Copy Markdown

Renovate maintained by Sebastian Software GmbH — repository standards live at sebastian-software/standards.

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.

📚 See our Reading List for relevant documentation you may be interested in reading.

🔡 Do you want to change how Renovate upgrades your dependencies? Add your custom config to renovate.json in this branch and select the Retry/Rebase checkbox below. Renovate will update the Pull Request description the next time it runs.


Detected Package Files

  • .github/workflows/ci.yml (github-actions)
  • .github/workflows/pages.yml (github-actions)
  • .github/workflows/publish.yml (github-actions)
  • package.json (npm)
  • renovate.json (renovate-config)

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 (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 Forgejo contains a link to the commit-to-commit diff
  • Ensure that every dependency pinned by digest and sourced from Gitea contains a link to the commit-to-commit diff
  • Ensure that every dependency pinned by digest and sourced from GitHub.com and Github enterprise contains a link to the commit-to-commit diff
  • Ensure that every dependency pinned by digest and sourced from GitLab.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
  • Provide a link to octochangelog's improved breakdown for Renovate's changelogs
  • Wait until the npm package is three days old before raising the update. This a) introduces a short delay to allow for malware researchers and scanners to (possibly) detect any malicious behaviour in packages, and b) prevents the maintainer and/or NPM from unpublishing a package you already upgraded to, breaking builds.
  • 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 Forgejo contains a link to the commit-to-commit diff
  • Ensure that every dependency pinned by digest and sourced from Gitea contains a link to the commit-to-commit diff
  • Ensure that every dependency pinned by digest and sourced from GitHub.com and Github enterprise contains a link to the commit-to-commit diff
  • Ensure that every dependency pinned by digest and sourced from GitLab.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
  • Provide a link to octochangelog's improved breakdown for Renovate's changelogs
  • Evaluate schedules according to timezone Europe/Berlin.
  • Shared Renovate preset for all Sebastian Software repositories.
  • Drives the @sebastian-software/standards rollout: stamps .repometa.json#standards against the package's manifest.json#currentVersion and runs the mechanical sync. Variant A is in force — a human merges every standards: PR after the two external agent runs (apply-judgement + pre-review) have posted their commit/comment; this preset deliberately sets no automerge. The custom datasource reads currentVersion from the PUBLISHED npm package via unpkg (@latest), not from the standards repo main branch: the rollout integer can then never lead the CLI that postUpgradeTasks fetches via dlx, which removes the main-ahead-of-npm race (the older raw.githubusercontent.com/.../main source advanced the moment a feat PR merged, before release-please published, so apply could be handed a version that did not exist on npm yet). currentVersion stays the migration-ledger integer (it maps to changes/NNNN), so CLI-only releases — e.g. the 0.6.0→0.6.1 patch, both currentVersion 4 — still trigger zero rollout; only real standards changes do. unpkg serves @latest with a short CDN TTL (max-age=60 / s-maxage=300), far inside the worker's 4×/day cadence. Relies on Renovate following the unpkg 302 redirect to the resolved version (got default). If unpkg is unavailable the datasource yields no release and no PR is filed — a safe, self-correcting degradation rather than a wrong rollout. jsDelivr was rejected as the source because it caches @latest for up to 7 days.
  • 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 Forgejo contains a link to the commit-to-commit diff
  • Ensure that every dependency pinned by digest and sourced from Gitea contains a link to the commit-to-commit diff
  • Ensure that every dependency pinned by digest and sourced from GitHub.com and Github enterprise contains a link to the commit-to-commit diff
  • Ensure that every dependency pinned by digest and sourced from GitLab.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
  • Provide a link to octochangelog's improved breakdown for Renovate's changelogs
  • Evaluate schedules according to timezone Europe/Berlin.
  • Shared Renovate preset for all Sebastian Software repositories.

What to Expect

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

chore(deps): update dependency @release-it/conventional-changelog to v10.0.6
chore(deps): update eslint monorepo to v9.39.4
  • Schedule: ["at any time"]
  • Branch name: renovate/eslint-monorepo
  • Merge into: main
  • Upgrade @eslint/js to 9.39.4
  • Upgrade eslint to 9.39.4
chore(deps): update dependency @​types/node to v24.13.2
  • Schedule: ["at any time"]
  • Branch name: renovate/node-24.x-lockfile
  • Merge into: main
  • Upgrade @types/node to 24.13.2
chore(deps): update dependency jiti to v2.7.0
  • Schedule: ["at any time"]
  • Branch name: renovate/jiti-2.x-lockfile
  • Merge into: main
  • Upgrade jiti to 2.7.0
chore(deps): update dependency lint-staged to v16.4.0
  • Schedule: ["at any time"]
  • Branch name: renovate/lint-staged-16.x-lockfile
  • Merge into: main
  • Upgrade lint-staged to 16.4.0
chore(deps): update dependency prettier to v3.9.0
  • Schedule: ["at any time"]
  • Branch name: renovate/prettier-3.x-lockfile
  • Merge into: main
  • Upgrade prettier to 3.9.0
chore(deps): update typescript-eslint monorepo to v8.62.0
chore(deps): update vitest monorepo to v4.1.9
  • Schedule: ["at any time"]
  • Branch name: renovate/vitest-monorepo
  • Merge into: main
  • Upgrade vitest to 4.1.9
chore(deps): update actions/checkout action to v7
  • Schedule: ["at any time"]
  • Branch name: renovate/actions-checkout-7.x
  • Merge into: main
  • Upgrade actions/checkout to v7
chore(deps): update actions/configure-pages action to v6
  • Schedule: ["at any time"]
  • Branch name: renovate/actions-configure-pages-6.x
  • Merge into: main
  • Upgrade actions/configure-pages to v6
chore(deps): update actions/deploy-pages action to v5
  • Schedule: ["at any time"]
  • Branch name: renovate/actions-deploy-pages-5.x
  • Merge into: main
  • Upgrade actions/deploy-pages to v5
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 actions/upload-pages-artifact action to v5
chore(deps): update dependency @release-it/conventional-changelog to v11
chore(deps): update dependency lint-staged to v17
  • Schedule: ["at any time"]
  • Branch name: renovate/lint-staged-17.x
  • Merge into: main
  • Upgrade lint-staged to ^17.0.0
chore(deps): update dependency release-it to v20
  • Schedule: ["at any time"]
  • Branch name: renovate/release-it-20.x
  • Merge into: main
  • Upgrade release-it to ^20.0.0
chore(deps): update dependency typescript to v6
  • Schedule: ["at any time"]
  • Branch name: renovate/typescript-6.x
  • Merge into: main
  • Upgrade typescript to ^5.0.0 || ^6.0.0
  • Upgrade typescript to ^6.0.0
chore(deps): update eslint monorepo to v10
  • Schedule: ["at any time"]
  • Branch name: renovate/major-eslint-monorepo
  • Merge into: main
  • Upgrade @eslint/js to ^10.0.0
  • Upgrade eslint to ^9.0.0 || ^10.0.0
  • Upgrade eslint to ^10.0.0
chore(deps): update github artifact actions to v7
  • Schedule: ["at any time"]
  • Branch name: renovate/major-github-artifact-actions
  • Merge into: main
  • Upgrade actions/upload-artifact to v7
chore(deps): update googleapis/release-please-action action to v5

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


  • If you want to rebase/retry this PR, click this checkbox.

This PR has been generated by Mend Renovate.

@jamesfastnerbot jamesfastnerbot added the dependencies Pull requests that update a dependency file label Jun 30, 2026
@greptile-apps

greptile-apps Bot commented Jun 30, 2026

Copy link
Copy Markdown

Greptile Summary

Adds renovate.json to enable automated dependency updates via a Sebastian Software–managed Renovate preset. The file is minimal and correct — it references the official schema and delegates configuration entirely to local>sebastian-software/renovate-config.

  • Introduces renovate.json with $schema and a single extends entry pointing to the shared org-level Renovate preset.
  • Once merged, Renovate will open up to 20 dependency-update PRs (GitHub Actions upgrades and npm package bumps) subject to a 2-per-hour rate limit.

Confidence Score: 5/5

Safe to merge — the only change is a six-line Renovate config that defers all policy to the existing shared org preset.

The change is a single new JSON file with no logic. It delegates entirely to a maintained shared preset, the schema reference is correct, and there are no custom overrides that could cause unexpected behavior.

No files require special attention.

Important Files Changed

Filename Overview
renovate.json New Renovate configuration file that delegates all settings to the shared local>sebastian-software/renovate-config preset; no custom overrides needed.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[renovate.json] -->|extends| B[local>sebastian-software/renovate-config]
    B --> C[Shared Org Preset]
    C --> D[Timezone: Europe/Berlin]
    C --> E[Semantic Commits]
    C --> F[Dependency Dashboard]
    C --> G[standards rollout preset]
    A --> H{Renovate Bot}
    H --> I[GitHub Actions updates - 7 PRs]
    H --> J[npm package updates - 13 PRs]
    H -->|rate-limited| K[2 PRs/hour max]
Loading
%%{init: {'theme': 'base', 'themeVariables': {"darkMode": true, "background": "#0d1117", "primaryColor": "#21262d", "primaryTextColor": "#e6edf3", "primaryBorderColor": "#8b949e", "lineColor": "#8b949e", "textColor": "#e6edf3", "edgeLabelBackground": "#161b22", "actorBkg": "#21262d", "actorBorder": "#8b949e", "actorTextColor": "#e6edf3", "actorLineColor": "#8b949e", "signalColor": "#8b949e", "signalTextColor": "#e6edf3", "noteBkgColor": "#373320", "noteBorderColor": "#d4a72c", "noteTextColor": "#f0e6c0", "labelBoxBkgColor": "#21262d", "labelBoxBorderColor": "#8b949e", "labelTextColor": "#e6edf3", "loopTextColor": "#e6edf3", "activationBkgColor": "#30363d", "activationBorderColor": "#8b949e"}}}%%
flowchart TD
    A[renovate.json] -->|extends| B[local>sebastian-software/renovate-config]
    B --> C[Shared Org Preset]
    C --> D[Timezone: Europe/Berlin]
    C --> E[Semantic Commits]
    C --> F[Dependency Dashboard]
    C --> G[standards rollout preset]
    A --> H{Renovate Bot}
    H --> I[GitHub Actions updates - 7 PRs]
    H --> J[npm package updates - 13 PRs]
    H -->|rate-limited| K[2 PRs/hour max]
Loading

Reviews (1): Last reviewed commit: "Add renovate.json" | Re-trigger Greptile

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

dependencies Pull requests that update a dependency file

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant