* fix(nix): flake lock refresh
* fix(nix): handle nixpkgs upgrades with not explicit ref correct
* Remove fileMatch hack
* Force lock file updates for nix
* Support new lockable channel
as requested by @Mic92
* Fix lints
* Remove hack and set rangeStrategy instead
* Fix tests
* Add example comments
* Use codeBlock, inline fixtures
* Add test back which went missing while merging
* Simplify code
* Fix tests
* Fix undefined being displayed in dashboard
* revert: Fix undefined being displayed in dashboard
* fix(nix): use lockedVersion, fake confirmations and conditionally set currentValue
* test(nix): check for lockedVersion instead of currentDigest, remove rangeStrategy
* fix: only replace digest
* fix: make sure flake.nix contains new digest
* fix: replace deprecated update-input with flake update
* fix: update tests
* fix: only set lockedVersion for lockable tarballs, cleanup
* fix: don't use special versioning
* fix: get nixpkgs currentValue in tarballs
* test: fill in code coverage gaps
* test: fill in more code coverage gaps
* fix: use correct extract type
* test: improve code coverage
* test: explicitly check flakeLocked and flakeOriginal to see what isn't being covered
* fix: check both original and locked inputs for bad types
* test: add missing root
* Update lib/modules/manager/nix/extract.ts
Co-authored-by: Joshua Spence <josh@spence.com.au>
* Update lib/modules/manager/nix/extract.ts
Co-authored-by: Joshua Spence <josh@spence.com.au>
* fix: explicitly set log messages
* Update lib/modules/manager/nix/extract.ts
Co-authored-by: RahulGautamSingh <rahultesnik@gmail.com>
* Update lib/modules/manager/nix/extract.ts
Co-authored-by: RahulGautamSingh <rahultesnik@gmail.com>
* Update lib/modules/manager/nix/extract.ts
Co-authored-by: RahulGautamSingh <rahultesnik@gmail.com>
---------
Co-authored-by: Sandro Jäckel <sandro.jaeckel@gmail.com>
Co-authored-by: Joshua Spence <josh@spence.com.au>
Co-authored-by: RahulGautamSingh <rahultesnik@gmail.com>
* feat(github-actions): extract and update version for `pypa/hatch@install` action
* docs(managers/github-actions): add pypa install action to community uses-with list
* feat(gitlab-ci): Add `semver-partial` versioning
* Add supported range strategies to semver-partial
* Add test cases for invalid semver inputs
* Remove unused sortVersions spec test
* Add tests for semver-partial versioning edge cases
* Simplify semver-partial version comparison logic
* Rewrite AI slop
* Add tests and improve semver-partial version matching
* Remove support for v-prefixed versions and bump strategy
* Refactor isLessThanRange to use parseVersion/Range
* Remove duplicate test cases in semver-partial spec
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.
* 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>
* 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
renovate[bot]