ift-ts:nim:ift:2026q4-nimble
Description
Continue improving Nimble as a reliable package and build tool for downstream teams. Build on the Q3 development track and review how Messaging, Storage, and Nimbus use Nimble in CI, identifying integration gaps and coordinating fixes with each team.
Task List
Nimble development
- fully qualified name:
ift-ts:nim:ift:2026q4-nimble:development - owner: Juan/Constantine
- status: in progress (25%)
- start-date: 2026/10/01
- end-date: 2026/12/31
Description
Continue Nimble development, stabilization, and issue resolution from Q3. Prioritize outstanding development goals, dependency resolution and lockfile reliability, package installation, and build behavior needed by downstream projects. Add regression coverage for fixes and update usage documentation when behavior changes.
Deliverables
- nim-lang/nimble#1879 Warn when updating nimble from a nimble in a different path
- nim-lang/nimble#1878 Resolve the version of a named package instead of reusing its cached…
- nim-lang/nimble#1880 Docs: Add a note about when to use lock files.
- nim-lang/nimble#1884 Refactor: Split dependency resolution into nimblesolver, nimblesat and nimblepubgrub
- nim-lang/nimble#1883 Parse each version once in PubGrub instead of on every comparison
- nim-lang/nimble#1882 Add —solver:pubgrub
CI integration review
- fully qualified name:
ift-ts:nim:ift:2026q4-nimble:ci-integration-review - owner: TBD
- status: not started
- start-date: 2026/10/01
- end-date: 2026/12/31
Description
Review Nimble integration into the CI workflows of Logos Messaging, Logos Storage, and Nimbus. For each project, inspect the current integration, dependency and lockfile handling, toolchain selection, caching, and build/test execution on its supported CI platforms. Identify gaps or failures, agree follow-up work with the project owners, and contribute Nimble or workflow fixes where needed.
Deliverables
- A review for each of Messaging, Storage, and Nimbus documenting current integration, findings, and recommended changes.
- Issues or PRs addressing integration gaps, with ownership for remaining follow-ups.
- CI validation results for changes made during the review.