Add support for Smithy

[secustor]

Tell us more.

Smithy is similar to OpenAPI and its ecosystem of generators used to generate Server stubs and clients in different languages.
It originates from AWS and is used heavily in adjacent companies.

[secustor]

New package manager questionnaire

Did you read our documentation on adding a package manager?

• I've read the adding a package manager documentation.

Basics

What's the name of the package manager?

Smithy

What language(s) does this package manager support?

It is rather a framework but uses Java artifacts for customizing in its smithy-build.json
https://smithy.io/2.0/guides/smithy-build-json.html

How popular is this package manager?

Somewhat in companies working with AWS resources

Does this language have other (competing?) package managers?

• Yes (give names).
• No.

What are the big selling points for this package manager?

n/a

Detecting package files

What kind of package files, and names, does this package manager use?

It uses smithy-build.json exclusively.

Which managerFilePatterns pattern(s) should Renovate use?

["(^|/)smithy-build\\.json$"]

Do many users need to extend the managerFilePatterns pattern for custom file names?

• Yes, provide details.
• No.

Is the managerFilePatterns pattern going to get many "false hits" for files that have nothing to do with package management?

No

Parsing and Extraction

Can package files have "local" links to each other that need to be resolved?

No

Package file parsing method

The package files should be:

• Parsed together (in serial).
• Parsed independently.

Which format/syntax does the package file use?

• JSON
• TOML
• YAML
• Custom (explain below)

How should we parse the package files?

• Off the shelf parser.
• Using regex.
• Custom-parsed line by line.
• Other.

Does the package file have different "types" of dependencies?

• Yes, production and development dependencies.
• No, all dependencies are treated the same.

List all the sources/syntaxes of dependencies that can be extracted

Smithy uses Maven packageNames and versions

groupId:artifactId:version

https://smithy.io/2.0/guides/smithy-build-json.html#maven-configuration

Describe which types of dependencies above are supported and which will be implemented in future

Only Maven packages so far

Versioning

What versioning scheme does the package file(s) use?

https://docs.renovatebot.com/modules/versioning/maven/

Does this versioning scheme support range constraints, like ^1.0.0 or 1.x?

• Supports range constraints (for example: ^1.0.0 or 1.x), provide details.
• No.

Uses standard maven ranges, with some features not supported

Unsupported version requirements
LATEST, RELEASE, latest-status, and latest.* versions are not supported.

Gradle style + versions are not supported.

Lookup

Is a new datasource required?

• Yes, provide details.
• No.

Will users want (or need to) set a custom host or custom registry for Renovate's lookup?

• Yes, provide details.
• No.

They will want to set custom Maven registries

Where can Renovate find the custom host/registry?

• No custom host or registry is needed.
• In the package file(s), provide details.
• In some other file inside the repository, provide details.
• User needs to configure Renovate where to find the information, provide details.

They are the same file under the maven.repositories field.
https://smithy.io/2.0/guides/smithy-build-json.html#maven-repositories

Are there any constraints in the package files that Renovate should use in the lookup procedure?

• Yes, there are constraints on the parent language (for example: supports only Python v3.x), provide details.
• Yes, there are constraints on the parent platform (for example: only supports Linux, Windows, etc.), provide details.
• Yes, some other kind of constraint, provide details.
• No constraints.

Will users need the ability to configure language or other constraints using Renovate config?

• Yes, provide details.
• No.

Artifacts

Does the package manager use a lock file or checksum file?

• Yes, uses lock file.
• Yes, uses checksum file.
• Yes, uses lock file and checksum file.
• No lock file or checksum.

Is the locksum or checksum mandatory?

• Yes, locksum is mandatory.
• Yes, checksum is mandatory.
• Yes, lock file and checksum are mandatory.
• No mandatory locksum or checksum.
• Package manager does not use locksums or checksums.

If lockfiles or checksums are used: what tool and exact commands should Renovate use to update one (or more) package versions in a dependency file?

n/a

Package manager cache

Does the package manager use a cache?

• Yes, provide details.
• No.

If the package manager uses a cache, how can Renovate control the cache?

• Package manager does not use a cache.
• Controlled via command line interface, provide details.
• Controlled via environment variables, provide details.

Should Renovate keep a cache?

• Yes, ignore/disable the cache.
• No.

Generating a lockfile from scratch

Renovate can perform "lock file maintenance" by getting the package manager to generate a lockfile from scratch.
Can the package manager generate a lockfile from scratch?

• Yes, explain which command Renovate should use to generate the lockfile.
• No, the package manager does not generate a lockfile from scratch.
• No, the package manager does not use lockfiles.

Other

What else should we know about this package manager?