renovate

mirror of https://github.com/renovatebot/renovate.git synced 2026-10-26 07:20:39 +00:00

Files

T

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

index.spec.ts

test(linters): add codeblock linter rule for spec fixtures (#44551 )

2026-07-14 13:00:02 +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

parse.spec.ts

feat(datasource): Implement rust-version data source (#39529 )

2026-04-29 15:23:44 +00:00

parse.ts

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

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

readme.md

feat(datasource): Implement rust-version data source (#39529 )

2026-04-29 15:23:44 +00:00

types.ts

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

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

readme.md

This datasource fetches available Rust compiler versions from the official Rust distribution infrastructure at https://static.rust-lang.org/manifests.txt.

How it works

The datasource retrieves version information from a single source file (manifests.txt) which contains chronological URLs to manifest files for all Rust releases. Rather than fetching each individual manifest TOML file, version information is extracted directly from the URL patterns using regex parsing.

Supported Versions

The datasource only returns versions that correspond to specific Rust releases:

Stable releases: 1.81.0, 1.82.0, etc.
Beta releases: 1.83.0-beta.4, 1.83.0-beta.5, etc.
Dated nightlies: nightly-2025-11-23, nightly-2025-11-24, etc.

Version Extraction

Manifest URLs follow this pattern:

static.rust-lang.org/dist/YYYY-MM-DD/channel-rust-{identifier}.toml

Examples:

static.rust-lang.org/dist/2025-11-24/channel-rust-nightly.toml → Version: nightly-2025-11-24
static.rust-lang.org/dist/2024-10-17/channel-rust-1.82.0.toml → Version: 1.82.0
static.rust-lang.org/dist/2025-01-15/channel-rust-1.83.0-beta.5.toml → Version: 1.83.0-beta.5

Release Timestamps

Release timestamps are derived from the date in the manifest URL and set to midnight UTC (YYYY-MM-DDTHH:MM:SS.000Z). This provides day-level precision for release timing.

Versioning Scheme

This datasource uses the rust-release-channel versioning scheme, which understands Rust's release channels, dated nightlies, and semantic versioning for stable and beta releases.