Skip to content

Config file up to date#1906

Merged
mre merged 5 commits into
lycheeverse:masterfrom
thomas-zahner:config-file-up-to-date
Nov 11, 2025
Merged

Config file up to date#1906
mre merged 5 commits into
lycheeverse:masterfrom
thomas-zahner:config-file-up-to-date

Conversation

@thomas-zahner

Copy link
Copy Markdown
Member

This PR addresses the following (also see commit history)

  • Reject unknown TOML keys, which is quite a nice addition, as I've struggled in the past with this. Also, I found quite a few mistakes in the fixtures because of this.
  • Ensure full documentation coverage in lychee.example.toml
  • files_from is now usable within the config file
  • Refactor to simplify CLI tests

Addresses #1768

@mre mre left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Great! I don't see any issues. 👍

@mre mre merged commit 1fa74d6 into lycheeverse:master Nov 11, 2025
7 checks passed
dmitryax added a commit to dmitryax/opentelemetry-collector that referenced this pull request Mar 5, 2026
Fixes the CI job https://github.com/open-telemetry/opentelemetry-collector/actions/runs/22696233513/job/65804104304

The changelog link checker CI started failing after open-telemetry#14676 bumped `lycheeverse/lychee-action` from v2.7.0 to v2.8.0, which bundles lychee v0.23.0.

lycheeverse/lychee#1906 ("Config file up to date") made unknown TOML keys a hard error instead of silently ignoring them. The two keys in `.github/lychee.toml` used hyphens (`include-fragments`, `max-retries`), but the actual struct field names use underscores (`include_fragments`, `max_retries`).

I'm disabling the options for now to keep the behavior as as. Will try to bring back fragments check after that. I assume they might fail
github-merge-queue Bot pushed a commit to open-telemetry/opentelemetry-collector that referenced this pull request Mar 5, 2026
Fixes the CI job
https://github.com/open-telemetry/opentelemetry-collector/actions/runs/22696233513/job/65804104304

The changelog link checker CI started failing after #14676 bumped
`lycheeverse/lychee-action` from v2.7.0 to v2.8.0, which bundles lychee
v0.23.0.

lycheeverse/lychee#1906 made unknown TOML keys a hard error instead of
silently ignoring them. The two keys in `.github/lychee.toml` used
hyphens (`include-fragments`, `max-retries`), but the actual struct
field names use underscores (`include_fragments`, `max_retries`).

I'm disabling the options for now to keep the behavior as is. Will try
to actually introduce the fragments check after that. I assume they
might fail
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants