Skip to content

Conversation

@MattSturgeon
Copy link
Member

@MattSturgeon MattSturgeon commented Nov 21, 2025

Remove the deprecated <flake>.lib.<system>.helpers output, deprecated in #2727 during the 25.05 cycle (shortly after 24.11 branch off).

Maybe we should hold off on this until after 25.11 is released and merge this during the 26.05 cycle?

Remove the deprecated <flake>.lib.<system>.helpers output, deprecated in
d39a09d
@khaneliman
Copy link
Contributor

Maybe we should hold off on this until after 25.11 is released and merge this during the 26.05 cycle?

I'm at that mindset with a lot of deprecations right now. Just waiting for release branch to clean a lot of stuff up in HM/Nixpkgs/etc

@GaetanLepage
Copy link
Member

I would slightly lean towards "sooner is better". But I can understand why holding it off is less scary.

+0.5 for dropping it now.

@khaneliman
Copy link
Contributor

Just figured we'd follow the deprecation policy we wrote up

- We **should not** remove it before `n+1` is released unless there is a bug or it is plain wrong
If it hasn't been deprecated in a release yet, doesn't make sense to rush to remove for stable users. (I personally don't live on stable, but have just been trying to adhere to that concept) Also is so close to another cutoff I don't see the benefit of doing it early.

@MattSturgeon
Copy link
Member Author

If it hasn't been deprecated in a release yet

deprecated [during] the 25.05 cycle

The warning was in the 25.05 release, so it has been in a release. But I still consider "one" release (6mo) to be the extreme minimum, 12mo isn't so bad in ordinary circumstances.

My vote also goes to keeping the warning in the 25.11 release, then dropping it early in 26.06.

I still welcome early review and/or approval, but let's hold off a few weeks on actually merging.

@khaneliman
Copy link
Contributor

khaneliman commented Nov 21, 2025

If it hasn't been deprecated in a release yet

deprecated [during] the 25.05 cycle

The warning was in the 25.05 release, so it has been in a release. But I still consider "one" release (6mo) to be the extreme minimum, 12mo isn't so bad in ordinary circumstances.

My vote also goes to keeping the warning in the 25.11 release, then dropping it early in 26.06.

I still welcome early review and/or approval, but let's hold off a few weeks on actually merging.

Sorry, I'm absolutely brain wrecked the last couple months.. I misread it as it wasn't in the last release. I'm fine with removing if it was already in a stable release. (Still think it's close enough to new release we can be nicer by just waiting a slight bit longer since we've already gone this far)

@GaetanLepage
Copy link
Member

Ok, let's hold it then :)

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.

3 participants