renovate

mirror of https://github.com/renovatebot/renovate.git synced 2026-10-24 14:34:21 +00:00

Files

T

History

Sebastian Poxhofer e0cec3dc95 refactor(lint): add types-location rule and enable it for lib/modules (#45497 )

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

2026-08-27 19:52:09 +00:00

common.spec.ts

feat(versioning/debian): port Ubuntu date versioning support (#40499 )

2026-03-19 16:05:04 +00:00

common.ts

refactor(lint): add types-location rule and enable it for lib/modules (#45497 )

2026-08-27 19:52:09 +00:00

index.spec.ts

fix(versioning/debian): keep numeric value on dated codename update (#44335 )

2026-07-03 06:28:13 +00:00

index.ts

refactor(lint): add types-location rule and enable it for lib/modules (#45497 )

2026-08-27 19:52:09 +00:00

readme.md

docs: fix typos (#17613 )

2022-09-04 16:21:27 +00:00

readme.md

Debian versioning is used for Debian container images that are referenced by their major release version or a codename.

Versions to which this scheme applies are e.g. 11 and bullseye. Container image tags such as 11-slim, 11.4 or 11.4-slim, bullseye-20220822 or bullseye-backports are not compliant with the current implementation.