renovate

mirror of https://github.com/renovatebot/renovate.git synced 2026-10-25 15:01:49 +00:00

Files

T

Sebastian Poxhofer 16ef1715e9 refactor(linters): add rules for @sindresorhus/is helpers (#45229 )

* feat(lint): add renovate/prefer-is-helpers and renovate/prefer-is-object rules

Flag ad-hoc type checks that have @sindresorhus/is equivalents:
- .filter(Boolean) -> .filter(isTruthy)
- typeof x === 'string' -> isString(x)
- x === null || x === undefined -> isNullOrUndefined(x) (and negation)

The typeof x === 'object' shape lives in a separate suggestion-only rule
(renovate/prefer-is-object, kept at warn) because isObject()/isPlainObject()
are not drop-in equivalents: null, arrays and functions behave differently.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

* refactor: fix renovate/prefer-is-helpers violations

Replace ad-hoc type checks with @sindresorhus/is helpers across lib/:
- 13x .filter(Boolean) -> .filter(isTruthy)
- 36x typeof x ==/!== 'string' -> isString(x) / !isString(x)
- 6x x === null || x === undefined -> isNullOrUndefined(x) (and negation)

Promote renovate/prefer-is-helpers to error now that the codebase is clean.
renovate/prefer-is-object stays at warn: its 15 remaining sites guard
parsed YAML/JSON or unknown values where isObject()/isPlainObject() are
not provably equivalent (null/array/function semantics).

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

* refactor: enforce renovate/prefer-is-object at error level

Resolve the 15 remaining warnings and raise the rule from warn to error:

- Migrate 10 sites to isObject() where the guarded value provably cannot
  be a function (parsed YAML/JSON, typed exec command arguments, or
  test-controlled fixtures): helm-values, woodpecker, bun, pre-commit
  managers, exec utils, file package cache, and the github http spec.
  In the bun manager this also fixes a latent crash where a null
  `workspaces` value would throw on the `in` operator.
- Keep 5 sites as reasoned oxlint-disable comments where excluding
  functions is load-bearing: the byte-exact fingerprint canonicalizer
  (2), the circularity walker, the zod result guard, and the generic
  hasKey helper.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

---------

Co-authored-by: Claude Fable 5 <noreply@anthropic.com>

2026-08-13 14:22:03 +00:00

index.spec.ts

refactor: Rewrite imports with .ts extensions (#40700 )

2026-01-26 22:48:17 +00:00

index.ts

refactor(linters): add rules for @sindresorhus/is helpers (#45229 )

2026-08-13 14:22:03 +00:00

readme.md

feat(versioning): Add a NodeJS Lambda Versioning module (#32480 )

2025-05-06 21:51:26 +00:00

schedule.ts

refactor: Rewrite imports with .ts extensions (#40700 )

2026-01-26 22:48:17 +00:00

readme.md

Renovate's Lambda Node.js versioning is a wrapper around the existing Node.js Versioning module with the only difference being that it lists versions not currently supported by AWS as being unstable. This is intended to be a drop-in replacement for dependencies that follow the node versioning schedule if you need to keep them in line with Lambda Runtime releases.

Its primary purpose is to add Node Runtime support awareness, e.g.:

Old Runtimes that cannot be updated will be marked as unstable
Node.js LTS releases that do not have Runtimes released for them will be marked as unstable

You can not use lambda-node versioning to replace docker versioning if you are using node tags with suffixes like -alpine. This is because npm versioning treats these suffixes as implying pre-releases/instability.