Files
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
..
2024-08-12 06:32:08 +00:00

Unity versioning follow semantic versioning, followed by a letter, number and an optional hash:

  • Major version is the year of release
  • Minor and patch version are incremental, starting at 0
  • The letter denotes a stream (alpha, beta, final release, etc.)
  • The number is a growing index
  • The hash is calculated by Unity internally and irrelevant for comparison

Examples:

  • 2023.2.10f1 (316c1fd686f6)
  • 2023.3.0a17
  • 2023.3.0b4 (2cd31b2a2ee2)