feat: stamp the corpus version on the output contract (#54) #355
No reviewers
Labels
No labels
area: build
area: ci
area: compare
area: data
area: engine
area: model
area: provenance
area: rite
area: validation
backport
blocked
breaking
confirmed
dependencies
duplicate
epic
github_actions
invalid
needs-info
needs-triage
php
priority: high
priority: low
priority: medium
regression
type: bug
type: chore
type: correction
type: docs
type: enhancement
type: feature
type: fix
type: perf
type: refactor
type: security
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
Directorium/Core!355
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "feature/54-corpus-version"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Closes #54.
Makes the calendar-data build a first-class provenance axis, distinct from the edition and the engine.
SanctoralData::version()— new interface method;SeedSanctoralDatareturns a dated seed stamp1962-seed-<date>that names only the data build (no edition token, so the same corpus can be resolved under any edition). The cited corpus generator (#38) will supply its own build id in its place.DayResolver::provenance()now sourcescorpusVersionfrom the activeSanctoralDatarather than a placeholder constant, andfor1962()defaults to a concreteSeedSanctoralDataso the stamp is always available.Tests
contractVersion,corpusVersion,engineVersion) are present and well-formed;editionis pinned toroman:rubricae-1960andritetoroman.:, noroman, norubricae).Local gate:
composer lint(0),composer analyse([OK]),composer test(480 tests / 30,369 assertions).