* docs(aws-machine-image): fix regex to preserve currentImageName comment
The example regex pattern incorrectly captures `currentImageName` into the `currentDigest` group, causing Renovate to update this comment field. The `currentImageName` field should remain static (typically "unknown") and not be modified during updates.
Remove the named capture group `<currentDigest>` from the `currentImageName` pattern so the comment line is preserved as-is while only the AMI ID is updated.
* chore: revert quote changes
* docs(aws-machine-image): clarify that currentImageName is updated by renovate
Replace `currentImageName=unknown` with realistic AMI names in all examples to accurately reflect that Renovate updates this field to track the actual AMI name. Add note explaining this behavior.
* chore: update structure
Co-authored-by: RahulGautamSingh <rahultesnik@gmail.com>
* docs(aws-machine-image): add examples without currentImageName comment
* chore: add typescript example
---------
Co-authored-by: RahulGautamSingh <rahultesnik@gmail.com>
When a requirements file includes another via the `-r` flag it's always
treated as relative to the directory where the requirements file is, not
the directory where the command is being run. Those are often the same,
but not always.
* feat: update readme.md for rpm datasource
* clarify example
* use managerFilePatterns
* add yum sample
* add hint when no release is found
* feat: update readme.md for rpm datasource
* slight modification for release clarification
* Support useJUnitJupiter under suites.withType
* unify
* fix: change withType maxDepth from 2 to 1
Addresses review comment from @Churro about maxDepth: 2 being too permissive.
With maxDepth: 1, the withType tree will only match:
- withType(JvmTestSuite)
- withType(JvmTestSuite::class)
This prevents unintended matching of nested structures like withType([...])
which are not valid Gradle syntax for this use case and are not covered by tests.
* refactor: merge test suite queries using q.alt pattern
* docs(jsonata): Replace ' with " in JSON config
* docs(jsonata): Mention that `fileFormat` is a required field
When I validated my config, I was informed that `fileFormat` is required
for the jsonata manager.
This change updates the docs accordingly.
* docs(jsonata): Fix prettier lint errors
* docs(jsonata): Attempt to fix docs link…
* docs(jsonata): add missing parent directory to link
* fixup! docs(jsonata): add missing parent directory to link
* docs(jsonata): directory links are from the built sources
---------
Co-authored-by: Jamie Tanna <github@jamietanna.co.uk>
Co-authored-by: Jamie Tanna <jamie.tanna@mend.io>
gomod: Search the parent directories for "vendor" directory.
When the golang workspaces are used, the `go work vendor` generates
the `vendor` and `go.work.sum` files in the same directory where
the `go.work` exists - it means in the parent directory of `go.mod`
files.
The current code does not handle this behaviour correctly - it only
searches for the `vendor` directory next to the `go.mod` file.
In this commit, the code is extended to use `findLocalSiblingOrParent`
function to search for the `vendor` directory the very same way as
we currently search for the `go.work` file.
The code is also extended to search for the `go.work.sum` next to the
`go.work` file.
Related: https://github.com/renovatebot/renovate/discussions/37653
Signed-off-by: Jan Kaluza <jkaluza@redhat.com>
Co-authored-by: Jamie Tanna <jamie.tanna@mend.io>
* fix: Use SHA of fresh branches when reopening PR
* Revert
* Add force push for differing local and PR commit SHAs
* Update GitHub PR reopening with local SHA
* Update GitHub platform PR reopening logic
* Fix
* Remove title-related changes, keep only force-push logic
According to the [GitHub Docs](https://docs.github.com/en/rest/repos/rules?apiVersion=2022-11-28#get-rules-for-a-branch), the definition of the non_fast_forward ruleset is: “Prevent users with push access from force pushing to refs.”
Even if this ruleset is applied, a head branch that lags behind the base branch can still be merged normally. In other words, this ruleset has nothing to do with whether a rebase is required.
* feat(bazel-module): Add support for rules_img use_repo_rule
* feat(bazel-module): Set registryUrls for rules_img repo rule
* feat(bazel-module): Only set registryUrls on non-empty repository
Josi Moore