From ca5f9700f521fdae4562a1afbc60012b87b34a09 Mon Sep 17 00:00:00 2001 From: Olaoluwa Mustapha <37044906+OlaoluwaM@users.noreply.github.com> Date: Tue, 3 Dec 2024 10:12:42 -0600 Subject: [PATCH] Revert "fix(ci): Force CI to use specific nightly snapshot version" This reverts commit 26622b971e90172a0d58e0e86bac32e3a8023246. Looks like the stack-nightly.yaml is meant more as a placeholder to get CI to try to build this package with `--resolver nightly`. This tends to fail, but that's okay. Moreover, since this file is meant more as a placeholder of sorts, we don't need to include more info than what's necessary for this to be considered a valid `stack.yaml` file. Thus, simply upgrading the resolver version to the latest nightly version at the time of upgrading will often suffice --- stack-nightly-2023-12-26.yaml | 8 ------- stack-nightly.yaml | 1 + ...12-26.yaml.lock => stack-nightly.yaml.lock | 22 +++++++++---------- 3 files changed, 12 insertions(+), 19 deletions(-) delete mode 100644 stack-nightly-2023-12-26.yaml create mode 100644 stack-nightly.yaml rename stack-nightly-2023-12-26.yaml.lock => stack-nightly.yaml.lock (100%) diff --git a/stack-nightly-2023-12-26.yaml b/stack-nightly-2023-12-26.yaml deleted file mode 100644 index 11cba12..0000000 --- a/stack-nightly-2023-12-26.yaml +++ /dev/null @@ -1,8 +0,0 @@ -resolver: nightly-2023-12-26 -extra-deps: - - amazonka-2.0 - - amazonka-core-2.0 - - amazonka-s3-2.0 - - amazonka-sso-2.0 - - amazonka-sts-2.0 - - crypton-1.0.0 diff --git a/stack-nightly.yaml b/stack-nightly.yaml new file mode 100644 index 0000000..00c2a55 --- /dev/null +++ b/stack-nightly.yaml @@ -0,0 +1 @@ +resolver: nightly-2024-12-03 diff --git a/stack-nightly-2023-12-26.yaml.lock b/stack-nightly.yaml.lock similarity index 100% rename from stack-nightly-2023-12-26.yaml.lock rename to stack-nightly.yaml.lock index 15c0e09..42ea7b7 100644 --- a/stack-nightly-2023-12-26.yaml.lock +++ b/stack-nightly.yaml.lock @@ -4,6 +4,13 @@ # https://docs.haskellstack.org/en/stable/lock_files packages: +- completed: + hackage: crypton-1.0.0@sha256:637e58581978c84ef1288d14fa9cac1d2905ef60e319924293bc11250aca882d,14527 + pantry-tree: + sha256: 4b5e5511567c0fe735a224cb8b2b278e1caa79344f2940d030d169e69b1b81e1 + size: 23275 + original: + hackage: crypton-1.0.0 - completed: hackage: amazonka-2.0@sha256:d401ac9094bb331d1bfb9be879d9007ca6bc94085ab745de5aa827128ad7917c,3522 pantry-tree: @@ -18,13 +25,6 @@ packages: size: 3222 original: hackage: amazonka-core-2.0 -- completed: - hackage: amazonka-s3-2.0@sha256:1d93bec43e0fc9bc3a57c43aeeb010c74a60afd3af5acd077731aad923f99802,13870 - pantry-tree: - sha256: 0b88c93134287ca43f169d2163acce45700bab1ea81e97f11de4d4330db7c9fa - size: 38690 - original: - hackage: amazonka-s3-2.0 - completed: hackage: amazonka-sso-2.0@sha256:dfb9232d66fac2a912f63aa5ddaf56ea495649cc3ab451b5102f8ec579dedc4f,3012 pantry-tree: @@ -40,12 +40,12 @@ packages: original: hackage: amazonka-sts-2.0 - completed: - hackage: crypton-1.0.0@sha256:637e58581978c84ef1288d14fa9cac1d2905ef60e319924293bc11250aca882d,14527 + hackage: amazonka-s3-2.0@sha256:1d93bec43e0fc9bc3a57c43aeeb010c74a60afd3af5acd077731aad923f99802,13870 pantry-tree: - sha256: 4b5e5511567c0fe735a224cb8b2b278e1caa79344f2940d030d169e69b1b81e1 - size: 23275 + sha256: 0b88c93134287ca43f169d2163acce45700bab1ea81e97f11de4d4330db7c9fa + size: 38690 original: - hackage: crypton-1.0.0 + hackage: amazonka-s3-2.0 snapshots: - completed: sha256: b69a06c70e1092e2aa60ce69a4877c6181fbe53dfb7ea041cb98d97617d6007f