cross-rs/cross · error
some files were not validated
Error message
some files were not validated
What it means
Aggregated failure from the changelog validation xtask: while validating every changelog entry file, at least one file failed JSON parsing or ChangelogEntry::from_value extraction; all individual errors were collected (with their file path context) and this error is returned with the section reports so every problem is shown at once.
Solutions
- Fix each reported changelog file so it parses as valid JSON and satisfies the ChangelogEntry schema
- Re-run the changelog xtask until no validation errors remain
- Check recently added/edited files under the changelog directory against an existing valid entry
Defensive patterns
Strategy: validation
When it happens
Trigger: Thrown at xtask/src/changelog.rs:572 when the library encounters an invalid state.
Common situations: See trigger scenarios.
AI-assisted analysis of cross-rs/cross@8c1a8aa4b6 (2026-09-13).
Data as JSON: /api/errors/a98f50badd57136b.
Report an issue: GitHub.
Appendix: source
Thrown at xtask/src/changelog.rs:572
let value = match serde_json::from_str(&contents)
.wrap_err_with(|| format!("unable to parse JSON for \"{}\"", path.display()))
{
Ok(value) => value,
Err(e) => {
errors.push(e);
continue;
}
};
let res = ChangelogEntry::from_value(id, value)
.wrap_err_with(|| format!("unable to extract changelog from \"{}\"", path.display()))
.map(|_| ());
errors.extend(res.err());
}
if !errors.is_empty() {
return Err(crate::util::with_section_reports(
eyre::eyre!("some files were not validated"),
errors,
));
}
// also need to validate the existing changelog
let _ = read_changelog(&root)?;
Ok(())
}
#[cfg(test)]
mod tests {
use super::*;
macro_rules! s {
($x:literal) => {
$x.to_owned()
};View on GitHub (pinned to 8c1a8aa4b6)