Sebastian Poxhofer
00043d193e
* ci(linter): add renovate/codeblock-in-spec-fixtures rule Add a custom oxlint rule that requires the codeBlock (or stripIndent) template helper from common-tags for multi-line string fixtures in spec files (enabled for **/*.spec.ts and test/** only). The rule only flags shapes whose value can round-trip through the common-tags helpers unchanged, since both codeBlock and stripIndent trim the end result and strip the shortest line indentation: - only literals spanning multiple source lines are flagged (escaped \n one-liners are left alone: tagging them is not value-preserving in general and gains nothing) - values with leading/trailing whitespace (e.g. fixtures ending in a newline) are not flagged - tagged templates, describe/it titles, and inline snapshot arguments are skipped All 55 pre-existing violations (22 files) were fixed with a one-off codemod that re-emits each fixture indented to the statement depth and verifies value preservation by evaluating codeBlock on the rewritten template (substitutions kept as opaque placeholders). One site (pip_requirements/artifacts.spec.ts) mixes line continuations with escaped newlines and was tagged verbatim instead of re-indented. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> * ci(linter): address review findings Make getSimpleRequirementsFile in pip-compile/extract.spec.ts value-preserving again: tagging the whole template with codeBlock trimmed the trailing blank line when deps is empty (the headerOnly.txt case), silently changing the fixture from ending in '#\n\n' to '#'. Tag only the static header and append the deps section via a single-line template, which reproduces the original string exactly for both empty and non-empty deps (verified by executing old vs new in node). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> --------- Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
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-24static.rust-lang.org/dist/2024-10-17/channel-rust-1.82.0.toml→ Version:1.82.0static.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.