mirror of
https://github.com/renovatebot/renovate.git
synced 2026-11-12 06:44:24 +00:00
Sebastian Poxhofer
3ed45d1efd
* fix(datasource): replace getJsonUnchecked with validated getJson in misc+merge-confidence group Replaces all getJsonUnchecked calls with Zod-validated getJson calls in: - crate: adds CrateMetadataSchema to existing schema.ts - conan: uses existing ConanJSON schema directly - puppet-forge: new schema.ts with PuppetModuleSchema - conda: new schema.ts with CondaPackageSchema - repology: new schema.ts with RepologyPackagesSchema - jenkins-plugins: new schema.ts, parameterizes helper with ZodType<T> - custom/formats/json: uses z.unknown() for user-defined responses - merge-confidence: adds inline MergeConfidenceResponseSchema Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> * fix: correct nullable/optional schema fields for crate, jenkins-plugins, puppet-forge - crate: remove .optional() from all CrateMetadata fields to match string|null type - jenkins-plugins: use .default({}) instead of .optional() for plugins fields so schemas match required Record types; widen ZodType input to unknown; update JenkinsPluginVersion.releaseTimestamp to Timestamp|null to match MaybeTimestamp output - puppet-forge: change releases from .optional() to .default([]) to match Release[] type Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> * chore: migrate zod/v3 imports to zod/v4 in misc datasources and merge-confidence Update remaining zod/v3 imports in files added/modified by the getJsonUnchecked migration to use zod/v4 as required after the upstream migration. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> * chore minor improvements * remove unnecessary types and reintroduce nullable where necessary * refactor: move logic into transform * test: add tests to improve coverage * chore removed some unused types * remove type declaration --------- Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>
Datasources
Datasources are used in Renovate primarily to fetch released versions of packages.
Follow the class-based programming style
New datasources must follow the class-based programming style.
Use the java-version datasource as a reference.
Add the datasource to the API in api.ts so that the new datasource is usable.
If you find Unused HTTP mocks errors in the Vitest tests and your mocked URLs are correct, make sure the datasource is correctly registered.
getReleases
The minimum exported interface for a datasource is a function called getReleases that takes a lookup config as input.
The config has:
packageName: the package's full name including scope if present (e.g.@foo/bar)registryUrls: an array of registry URLs to try
getReleases should return an object having:
releases: an array of strings of matched versions. This is the only mandatory fielddeprecationMessage: a string description of the package's deprecation notice, if applicablesourceUrl: a HTTP URL pointing to the source code (for example on GitHub)homepage: a HTTP URL for the package's homepage. Ideally should be empty if the homepage andsourceUrlare the samechangelogUrl: a URL pointing to the package's changelog (could be a Markdown file, for example). If not present then Renovate will search thesourceUrlfor a changelog filetags: an object mapping tag → version, for exampletags: { latest: '3.0.0' }. This is only used by thefollowTagsfunction
getDigest
Datasources that support digests (like Docker digests and Git commit hashes) can export a getDigest function.
The getDigest function has two inputs:
config: the Renovate config for the package being updated, has the same fields asgetReleasesnewValue: the version or value to retrieve the digest for
The getDigest function returns a string output representing the digest value.
If no digest is found, the getDigest function should return null.