Repository navigation
Implement --snapshot-url - #33
Merged
Merged
Conversation
Adds --snapshot-url for an easier alternative to --snapshot-path, when all we want to do is pick a different snapshot. We also add another ci job that builds stackage with some fixed "stable" snapshot once a week. As the nightly snapshot runs into problems a few times a month, this gives users a fallback "last known good" snapshot use.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds new
--snapshot-url. There are two reasons for this.A minor advantage is that it is a slightly more convenient version of
--snapshot-path, as we can simply run e.g.--snapshot-url nightly-2026-10-22rather than manually downloading the file to use with--snapshot-path(the latter still works, to be clear).The primary motivation is to better signal to users the current snapshots' health.
We occasionally run into issues (2-3x/month) where
nightlyis broken e.g. a new problematic package is pulled in, or a hackage revision breaks something. This is confusing for any unfortunate soul who happens to useclc-stackagebefore it is fixed, as their only recourse is to try to fix it themselves (if they even realized it is not their GHC's fault), or scan CI for a date that was green.With the new
--snapshot-url, we can easily support two CI jobs: One that builds the latestnightly-- daily as usual -- and one that builds some fixedstablesnapshot weekly. With this, users need only look at the README badges to see which snapshots are working, which hopefully makes usage a little smoother.I also separated the normal build/tests CI from the snapshot builds, as we don't want an irrelevant test error to interfere with the snapshot status. For example, CI is currently red due to an unrelated macos action error (actions/runner-images#14940), even though the snapshot itself is currently fine.