Skip to content

Remove exclude mail#1691

Merged
thomas-zahner merged 3 commits intolycheeverse:masterfrom
thomas-zahner:remove-exclude-mail
May 13, 2025
Merged

Remove exclude mail#1691
thomas-zahner merged 3 commits intolycheeverse:masterfrom
thomas-zahner:remove-exclude-mail

Conversation

@thomas-zahner
Copy link
Member

@thomas-zahner thomas-zahner commented May 9, 2025

Updated the documentation in lycheeverse/lycheeverse.github.io#93 accordingly.

@thomas-zahner thomas-zahner force-pushed the remove-exclude-mail branch from a20c151 to 04cfccc Compare May 9, 2025 12:35
@@ -1,5 +1,5 @@
# Needed SHELL since I'm using zsh
SHELL := /bin/bash
SHELL := /usr/bin/env bash
Copy link
Member

Choose a reason for hiding this comment

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

nice

.map(|value| StatusCode::from_u16(*value))
.collect::<Result<HashSet<_>, _>>()?;

// `exclude_mail` will be removed in 1.0. Until then, we need to support it.
Copy link
Member

Choose a reason for hiding this comment

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

Yeah, technically the comment says "removed in 1.0", but I think it's fine to do so earlier. We probably even talked about it at some point. 😆

Copy link
Member Author

Choose a reason for hiding this comment

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

True and yeah we did talk about it 😄

Copy link
Member

@mre mre left a comment

Choose a reason for hiding this comment

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

The change looks good, but it will break a lot of code... 💣 💥
We have to do so at some point, but I wonder if you'd like to go through the list and pick the most prominent examples and we create an issue on their side to notify them about the changes?

@thomas-zahner
Copy link
Member Author

thomas-zahner commented May 12, 2025

@mre I've actually hand checked almost all of them and surprisingly only very few projects would be directly affected. Many projects use a fixed version, so it won't break without notice.

Bigger projects mostly depend on a fixed version of lychee-action. (lycheeverse/lychee-action@hash-or-version) Do I understand correctly that depending on a fixed version of lychee-action means that lychee-bin / lychee-lib are fixed?

@thomas-zahner
Copy link
Member Author

@mre
Copy link
Member

mre commented May 12, 2025

Thanks!

Do I understand correctly that depending on a fixed version of lychee-action means that lychee-bin / lychee-lib are fixed?

Yeah, because of https://github.com/lycheeverse/lychee-action/blob/82202e5e9c2f4ef1a55a3d02563e1cb6041e5332/action.yml#L30

@thomas-zahner
Copy link
Member Author

That makes sense 👍 I will merge then

@thomas-zahner thomas-zahner merged commit a8c0f45 into lycheeverse:master May 13, 2025
6 checks passed
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