Decouple build nixpkgs from released nixpkgs #401
Closed
+29
−7
Conversation
This file contains 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
The eager update to use 20.03 to *build* the flake accidentally made the site use the 20.03 manual. This change allows us to move forward the infrastructure of the site in preparation for a release, without actually using that version's manual. Additionally, it's not much of an issue, the list of AMIs could have been using the wrong list (of an unreleased branch), though as it requires manual involvement of the team it wouldn't have been an issue. Fixes #400.
|
Merged
|
This is included in #392 |
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.
The eager update to use 20.03 to build the flake accidentally made the
site use the 20.03 manual.
This change allows us to move forward the infrastructure of the site
in preparation for a release, without actually using that version's
manual.
Additionally, it's not much of an issue, the list of AMIs could have
been using the wrong list (of an unreleased branch), though as it
requires manual involvement of the team it wouldn't have been an issue.
Fixes #400.