Skip to content

Backport #12341: fix(CI): bootstrap.py no longer reuses a stale package database - #12353

Merged
mergify[bot] merged 1 commit into
3.18from
mergify/bp/3.18/pr-12341
Sep 12, 2026
Merged

Backport #12341: fix(CI): bootstrap.py no longer reuses a stale package database#12353
mergify[bot] merged 1 commit into
3.18from
mergify/bp/3.18/pr-12341

Conversation

@mergify

@mergify mergify Bot commented Sep 12, 2026

Copy link
Copy Markdown
Contributor

fix: #12311

The package database is now deleted and recreated from scratch on every
bootstrap run, making the script idempotent with respect to a dirty or
polluted _build. Additionally, the Bootstrap workflow now hashes the
.cabal files of the local packages into its cache key, so caches are no
longer shared between branches that build different versions of the local
packages.

  $ python3 bootstrap/bootstrap.py --bootstrap-sources bootstrap-sources.tar.gz
+ Deleting stale package database _build/packages.conf
  Creating package database _build/packages.conf
  Using ...

Template B: This PR does not modify behaviour or interface

E.g. the PR only touches documentation or tests, does refactorings, etc.

Include the following checklist in your PR:

  • Patches conform to the coding conventions.
  • Is this a PR that fixes CI? If so, it will need to be backported to older cabal release branches (ask maintainers for directions).

This is an automatic backport of pull request #12341 done by [Mergify](https://mergify.com).

(cherry picked from commit 72fa62f)
@zlonast zlonast added the merge me Tell Mergify Bot to merge label Sep 12, 2026
@mergify

mergify Bot commented Sep 12, 2026

Copy link
Copy Markdown
Contributor Author

Merge Queue Status

  • Entered queue2026-09-12 10:25 UTC · Rule: default · triggered by rule Put backports in the rebase+merge queue
  • Checks skipped · PR is already up-to-date
  • Merged2026-09-12 10:36 UTC · at f3cd6926cf08e6a44a7e2e9ab2b7e4cac4ed2bf0 · merge

This pull request spent 10 minutes 53 seconds in the queue, including 5 seconds running CI.

Required conditions to merge
  • #review-threads-unresolved = 0 [🛡 GitHub branch protection]
  • github-review-approved [🛡 GitHub branch protection]
  • any of [🛡 GitHub branch protection]:
    • check-success = Doctest Cabal
    • check-neutral = Doctest Cabal
    • check-skipped = Doctest Cabal
  • any of [🛡 GitHub branch protection]:
    • check-success = Meta checks
    • check-neutral = Meta checks
    • check-skipped = Meta checks
  • any of [🛡 GitHub branch protection]:
    • check-success = Validate post job
    • check-neutral = Validate post job
    • check-skipped = Validate post job
  • any of [🛡 GitHub branch protection]:
    • check-success = docs/readthedocs.org:cabal
    • check-neutral = docs/readthedocs.org:cabal
    • check-skipped = docs/readthedocs.org:cabal
  • any of [🛡 GitHub branch protection]:
    • check-success = Bootstrap post job
    • check-neutral = Bootstrap post job
    • check-skipped = Bootstrap post job
  • any of [🛡 GitHub branch protection]:
    • check-success = whitespace
    • check-neutral = whitespace
    • check-skipped = whitespace
  • any of [🛡 GitHub branch protection]:
    • check-success = Check sdist post job
    • check-neutral = Check sdist post job
    • check-skipped = Check sdist post job
  • any of [🛡 GitHub branch protection]:
    • check-success = Changelogs
    • check-neutral = Changelogs
    • check-skipped = Changelogs

@mergify
mergify Bot merged commit f3cd692 into 3.18 Sep 12, 2026
59 checks passed
@mergify
mergify Bot deleted the mergify/bp/3.18/pr-12341 branch September 12, 2026 10:36
@mergify mergify Bot removed the queued label Sep 12, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport merge me Tell Mergify Bot to merge

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant