[pull] main from renovatebot:main#1006
Merged
pull[bot] merged 20 commits intoryrodriguez25:mainfrom Mar 31, 2026
Merged
Conversation
…2262) chore(deps): update rhysd/actionlint docker tag to v1.7.12 | datasource | package | from | to | | ---------- | ---------------- | ------ | ------ | | docker | rhysd/actionlint | 1.7.11 | 1.7.12 | Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Set `SKIP_GITHUB_ISSUES=true` when issues are disabled (e.g. in a fork).
…42279) docs(usage): add nuget to list of supported registries for minimum release age
* docs: explicitly document `depTypes` each manager supports A long-standing question we receive is "what `depTypes` can I match against in my project". Although the best recommendation we usually have is "check the `packageFiles with updates" log line (as a very key log line for users), we can go one step further and try and create a stronger contract. To do this, I've used Claude Sonnet 4.6 to work through the codebase, determine areas that a `depType` is set in a manager (statically or dynamically) and generate a structured, typed, means to document how they're used. Through a few iterations of the process, and attempts at human-written documentation, we've settled on: - prioritising autogenerated documentation (for humans to read) to note what `depTypes` are known, and what they are - `knownDepTypes`, to describe any known, static, `depType`s and their human-readable meaning - with the `prettyDepType`, if used - `supportsDynamicDepTypesNote`, to add a Markdown note to the generated documentation While here, we also: - make sure to note this in the "adding a new package manager" documentation - remove any hand-written references to `depTypes` in each manager's documentation page - correct the Gleam `depTypes` - make sure to use the `knownDepTypes`'s `prettyDepType` definition if we know it, for a given `depType` The descriptions have been generated by Claude Sonnet, with some human-written tweaks where appropriate. [0]: #15176 Co-authored-by: Claude Sonnet 4.6 <jamie.tanna+claude-code@mend.io> * fixup! docs: explicitly document `depTypes` each manager supports * docs(manager): display `depTypes` documentation if none present For consistency, and to make it more explicit. --------- Co-authored-by: Claude Sonnet 4.6 <jamie.tanna+claude-code@mend.io>
feat(presets): Fix Aspire preset Fix Aspire preset due to repository being moved from the dotnet organization to microsoft.
chore(deps): update dependency graphql to v16.13.2 | datasource | package | from | to | | ---------- | ------- | ------- | ------- | | npm | graphql | 16.13.1 | 16.13.2 | Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
When trying to work out how Renovate's internal presets work, it can be a little awkward trying to jump between the different `extends`, as it requires copy-pasting and searching. We can utilise the annotations functionality in Material for MkDocs[0] and generate the relevant annotations for each of the `extends` that appears. In the case that a preset has a description (which is most of them) we can add that for a more interesting annotation. This requires we: - look up the presets' `description` ahead-of-time, as the generation process removes descriptions - traverse the preset's `extends` and link it through to the destination preset - create an ordered list after the code block to note the annotations - handle parameterised presets [0]: https://squidfunk.github.io/mkdocs-material/reference/code-blocks/#adding-annotations Co-authored-by: Claude Sonnet 4.6 <jamie.tanna+claude-code@mend.io>
Add both the new and old URLs.
….2 (main) (#42282) fix(deps): update ghcr.io/renovatebot/base-image docker tag to v13.32.2 | datasource | package | from | to | | ---------- | ------------------------------ | ------- | ------- | | docker | ghcr.io/renovatebot/base-image | 13.32.1 | 13.32.2 | Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
* chore(deps): update linters to v1.57.0 | datasource | package | from | to | | ---------- | -------------------- | ------ | ------ | | npm | eslint-plugin-oxlint | 1.56.0 | 1.57.0 | | npm | oxlint | 1.56.0 | 1.57.0 | * chore: fix oxlint --------- Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com> Co-authored-by: Michael Kriese <michael.kriese@visualon.de>
fix the type for pattern groups
…in) (#42289) build(deps): update dependency @pnpm/parse-overrides to v1001.0.4 | datasource | package | from | to | | ---------- | --------------------- | -------- | -------- | | npm | @pnpm/parse-overrides | 1001.0.3 | 1001.0.4 | Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
…42290) chore(deps): update docker/dockerfile docker tag to v1.23.0 | datasource | package | from | to | | ---------- | ----------------- | ------ | ------ | | docker | docker/dockerfile | 1.22.0 | 1.23.0 | Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
) * fix(http): fallback to github hostType for GHE platform endpoint When running against GitHub Enterprise Server, datasources not listed in GITHUB_API_USING_HOST_TYPES (e.g. github-digest) fail to authenticate because the existing fallback only covers api.github.com URLs. This adds a host-matching fallback: when the active platform is github and the request URL targets the same host as the configured endpoint, credentials from the github hostType rule are applied. * Refactor * Fix
chore(deps): update dependency pnpm to v10.33.0 | datasource | package | from | to | | ---------- | ------- | ------- | ------- | | npm | pnpm | 10.32.1 | 10.33.0 | Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
…40930) * feat(types): export additional types for downstream log consumers Export types commonly needed by downstream consumers parsing Renovate logs: - BunyanRecord: Log entry structure - RepositoryResult, ProcessStatus, ProcessResult: Repository processing outcomes - ValidationMessage, RenovateSplit: Validation/error types - BranchResult, PrBlockedBy: Branch processing outcomes - UpdateType, MergeStrategy: Update and merge configuration - MergeConfidence: Merge confidence levels - BranchUpgradeCache, BranchCache: Branch info from logs These types enable tools like log ingesters to parse Renovate output without redefining types locally. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com> * style(types): consolidate export comments into single section header Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * chore: remove unnecessary types --------- Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com> Co-authored-by: Jamie Tanna <jamie.tanna@mend.io>
…3.0 (main) (#42292) feat(deps): update ghcr.io/renovatebot/base-image docker tag to v13.33.0 | datasource | package | from | to | | ---------- | ------------------------------ | ------- | ------- | | docker | ghcr.io/renovatebot/base-image | 13.32.2 | 13.33.0 | Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
) * refactor: extract `applyHostRules` and `applyNpmrc` to functions * Reuse applyHostRules in inherited.ts * Restore original log message for npmrc * Simplify applyNpmrc log context handling * Remove redundant config word * Apply Jamie's suggestion * Restore log messages again * Revert "Restore log messages again" This reverts commit 7a67c5d. * chore: re-add log line --------- Co-authored-by: Jamie Tanna <jamie.tanna@mend.io>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
7 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
See Commits and Changes for more details.
Created by
pull[bot] (v2.0.0-alpha.4)
Can you help keep this open source service alive? 💖 Please sponsor : )