Bump time upper bound#11129
Closed
bgamari wants to merge 64 commits into
Closed
Conversation
Also bumps the cabal-install used during the release process to 3.14.2.0.
* Drop deb9, ubuntu18 and centos7 jobs which are all EOL * Add ubuntu24_04 * Build a very old alpine bindist (3.12) and a new one (3.20) * Only build 3_20 bindist for alpine i386. The list of release platforms after this commit is Linux * x86_64 - deb10 - deb11 - deb12 - fedora33 - fedora36 - fedora38 - rocky8 - ubuntu20_04 - ubuntu22_04 - ubuntu24_04 - alpine3_12 - alpine3_20 * i386 - deb10 - alpine3_20 * aarch64 - deb10 - deb11 - deb12 - alpine3_18 Darwin * x86_64 * aarch64 Windows * x86_64
Co-authored-by: Phil de Joux <philderbeast@gmail.com>
…piler Update release CI scripts (boot compiler and platform support)
Found while un-bumping for 3.16.
add paragraph mentioning stackage
…iles missed version bumps
It just inappropriately used a backport queue (luckily with no ill effects) for a release branch non-backport PR. Use the label we set on backports (which has a better pattern for matching them) instead of a body check. Also undid the attempted hack to stop the Mergify upgrade bot from breaking our priorities.
adjust Mergify queue rules for release branches
The main goal is to add an intermediate log message type to the processing of the solver log. There are zero known changes to the cabal solver's output. Co-Authored-By: Erik de Castro Lopo <erikd@mega-nerd.com>
The official capitalisation is “AArch”, see https://developer.arm.com/documentation/102374/latest/.
Refactor cabal-install solver config log output
Capitalise “AArch” properly
Allow relocatable builds on FreeBSD
missed updating all the copyrights in the cabal files
…l#11006) The cabal developers are interested to adopt a proposal process, the details are found in the `proposals.md` file. The process is designed to make developers feel empowered to make decisions. * It is light-weight, a PR is opened and discussed on a repo with a fixed discussion period. * It is developer-led, final decisions are made by developers at the Cabal developers meeting. * It is flexible, there is no formal voting procedure, decisions are made by rough consensus. Overall, we hope that this will allow developers to move the cabal project forward.
* Add changelog files for 3.16 * Integrate Brandon’s suggestions. * Integrate Brandon’s suggestions /II. * Integrate Bodigrim’s suggestions. * Integrate Artem’s suggestions. * Correctly capitalize “AArch” in preparation of haskell#11047 backport * Integrate Artem’s suggestions /II. * Remove changelog.d bits
Cabal-3.14.1.0 release notes minor fix: dedup "Other Changes" header
When calling `cabal update` with an empty state (empty CABAL_DIR or new machine), cabal writes out a default config file with many fields commented out to show their defaults. This suggests that the user can uncomment the field and override the default. This is wrong for fields that aren't allowed in the config file like `builddir`. This patch avoids generating a comment with `builddir` in the default config. Fix haskell#11050.
Add 3.16 release notes
…n-default-config-t11050 cabal update: don't show comment with builddir in the default config
If extra-lib-dirs and/or extra-include-dirs are specified via either command line or project files, they’re going to be added for each package in the dendency graph. With enough long enough directories the command-line length limits for gcc may be hit and calls to the C compiler made from hsc2hs will start failing. Ideally hsc2hs should be using repsonse files, but needlessly specifying myriad of command-line parameters is redundant anyway.
Fix typo in haddock comment
* Error messages are indented by 2 spaces * 0:0 positions are never shown * More attempts are made to remove extra newlines.
Bump to hlint-3.10
CI: add GHC 8.6.5 to validate-old-ghcs
Replace cabal project parsing with Parsec
Typo in Makefile .PHONY target
Simply disabling the step causes all non-Windows to fail, so we now skip it only on Windows.
Update Hackage root keys
work around git locking issue on Windows
Mark Terminate package test as flaky wrt haskell#11087
Fix typos in release script comments
- Follow hlint suggestion: Use isJust - Follow hlint suggestion: Use isNothing - Follow hlint suggestion: Redundant == - Follow hlint suggestion: Redundant fmap - Follow hlint suggestion: Use minimumBy - Follow hlint suggestion: Use lefts - Follow hlint suggestion: Use fromRight - Follow hlint suggestion: Use for - Follow hlint suggestion: Use forM_ - Follow hlint suggestion: Use when - Follow hlint suggestion: Use uncurry - Follow hlint suggestion: Use traverse - Follow hlint suggestion: Use ?~ - Follow hlint suggestion: Fuse traverse_/map - Follow hlint suggestion: Fuse traverse_/fmap - Follow hlint suggestion: Use replicateM - Follow hlint suggestion: Missing NOINLINE pragma - Rerun hlint --default - Redo hlint counts after rebase - Use Data.Foldable.minimumBy Co-Authored-By: ˌbodʲɪˈɡrʲim <andrew.lelechenko@gmail.com>
Skip T5634 on Alpine
Fix typo folowing
Apply hlint suggestions with a single count
Collaborator
|
See #11127. |
To allow time-1.15.
Contributor
Author
|
Thanks, @geekosaur ! |
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
12 participants
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.
To allow time-1.15.
See GHC #26268.