mirror of
https://github.com/renovatebot/renovate.git
synced 2026-10-25 23:11:31 +00:00
Sebastian Poxhofer
e0cec3dc95
feat(lint): add `types-location` rule and enable it for `lib/modules`
Reviewers consistently ask for exported types to be moved into a
colocated `types.ts`. Add a `renovate/types-location` oxlint rule that
reports `export interface` / `export type` declarations outside such a
file, and turn it on across `lib/modules`.
Re-exports (`export type { X }`, `export type *`), file-local types, and
values (enums, classes, functions) are left alone. `schema.ts` files and
`schema/` directories are excluded via config, matching how
`zod-schema-location` is configured — inferred types belong next to the
schema they are derived from.
Relocating the 87 existing violations means:
- new `types.ts` files for the modules that had none
- `terragrunt/common.ts` folded into its `types.ts`, as it held nothing
else
- `RangeBound` in `versioning/gradle/compare.ts` un-exported, since only
a file-local interface referenced it
- `bazel-module/parser/fragments.ts` split from its inferred types, which
now live in `parser/types.ts` and infer through a namespace import so
each schema keeps its merged name
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.