[pull] main from renovatebot:main#912
Merged
pull[bot] merged 6 commits intoryrodriguez25:mainfrom Mar 2, 2026
Merged
Conversation
refactor: move onboardingConfig to InheritConfig
* chore: Add vitest plugin to oxlint * Remove unused line in versioning spec * Remove coverage threshold check job The coverage threshold check has been removed from the build workflow. This job was redundant as coverage is already handled by the codecov job. * Refine versioning API schema with existence check * Revert "Remove coverage threshold check job" This reverts commit f2c9dd8. * Remove vitest ESLint plugin The vitest ESLint plugin and its configurations have been removed. ESLint will no longer enforce vitest-specific rules. * Remove unused vitest eslint plugin The `@vitest/eslint-plugin` is no longer used and can be safely removed.
…#41597) chore(deps): update dependency eslint-plugin-oxlint to v1.50.0 | datasource | package | from | to | | ---------- | -------------------- | ------ | ------ | | npm | eslint-plugin-oxlint | 1.49.0 | 1.50.0 | Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
* feat(postUpgradeTasks): allow specifying `installTools` As noted in #8111 and #41569, it is possible that when using `binarySource=install`, you can execute a `postUpgradeTasks`' given command without Renovate having the right tools installed, dependent on the Manager used for the update. To make it possible for users to indicate that they explicitly need given tools (at a given `constraint`), we can introduce a new `installTools` option which will allow specifying which tools + constraints to use when invoking the `postUpgradeTasks`'s command. Right now, we're not defining what the `installTools'` interior type is, but leaving it open to extension. Co-authored-by: gpt-4.1 <jamie.tanna+github-copilot@mend.io> * docs: add examples for `toolVersions` --------- Co-authored-by: gpt-4.1 <jamie.tanna+github-copilot@mend.io>
bazelrc spec supports surounding urls with quotes and this PR aligns functionality to match spec
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.
5 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 : )