Skip to main content

Module compatibility

Module compatibility 

Source
Expand description

What a release needs of the engine that lands it.

A bundle can be authentic, intact, and still wrong for this engine: it may need a newer one, or a version the interval must pass through. Both are declared by the release rather than inferred, because only the release knows what it asked of the tool that wrote it.

The declaration is required. An absence that means “no requirement” cannot be told from an absence that means somebody forgot, so a schema-one bundle without the file is invalid and says which file.

Structs§

Compatibility
What one release needs of its engine.
Interval
What the plan checks the compatibility against.

Enums§

CompatibilityError
A declaration this engine cannot read.

Constants§

DECLARATION_PATH
Where the declaration sits inside a bundle.
SCHEMA
The schema this engine reads.

Functions§

preconditions
Every compatibility precondition one interval carries.