Skip to article frontmatterSkip to article content
Site not loading correctly?

This may be due to an incorrect BASE_URL configuration. See the MyST Documentation for reference.

Scala Kernel Maintenance and Documentation

Status: In Progress · Proposal

August 2026

Summary of Work Completed

During this period, work revolved around preparation work for Spark 4 support then actual Spark 4 support, finishing getting Almond using its fork of its Ammonite dependency (that backs its Scala REPL support), and getting the Almond repositories (Almond itself, its Ammonite fork, ammonite-spark) ready for new releases taking into account Maven Central new publishing limits.

ammonite-spark’s build was refactored, in order to have non-regression tests for many more Spark versions, not just a handful of them (alexarchambault/ammonite-spark#494, alexarchambault/ammonite-spark#495, alexarchambault/ammonite-spark#496, alexarchambault/ammonite-spark#498, alexarchambault/ammonite-spark#499, alexarchambault/ammonite-spark#500, alexarchambault/ammonite-spark#502, alexarchambault/ammonite-spark#504, alexarchambault/ammonite-spark#505, alexarchambault/ammonite-spark#506, alexarchambault/ammonite-spark#509), and ensure support for those doesn’t regress.

Actual support for Spark 4 was added later on, on top of that (alexarchambault/ammonite-spark#507).

Almond’s Ammonite fork was put in shape for Almond’s needs and for easier maintenance (almond-sh/Ammonite#4, almond-sh/Ammonite#5, almond-sh/Ammonite#7, almond-sh/Ammonite#8, almond-sh/Ammonite#10, almond-sh/Ammonite#11), and also to limit the amount of data being shipped during releases, to try to respect Maven Central new publishing limits (almond-sh/Ammonite#6, almond-sh/Ammonite#9, almond-sh/Ammonite#13, almond-sh/Ammonite#14, almond-sh/Ammonite#15).

Almond, alongside ammonite-spark, switched to using its Ammonite fork (almond-sh/almond#1715, alexarchambault/ammonite-spark#508).

Still aiming at respecting Maven Central new publishing limits, work is on-going to limit the number of modules published by Almond while not dropping features (almond-sh/almond#1716, almond-sh/almond#1721, almond-sh/almond#1723).

Some user proposed changes were reworked (almond-sh/almond#1710 resulting in almond-sh/almond#1712 and almond-sh/almond#1713), and a fix for a longstanding issue was finally merged (almond-sh/almond#1666, fixing almond-sh/almond#1499).

Deliverables/Milestones

New features of bug fixes were merged (Spark 4 support, user-reported issues just above), Almond now relies on its fork of Ammonite. But all of this awaits releases (see next steps).

Challenges or Risks

Mostly about time: time spent working on this is a bit behind schedule, but things should be much better now, now that I have a solid AI workflow, and that the holiday period is behind us.

Budget Update

4.5 days of work done since the last report, so 8 days of work done overall, over 39.5 days planned

Next Steps

June 2026

Summary of Work Completed

During this period, mainly on-going work for Spark 4 support, and some more CI stabilization

Deliverables/Milestones

Nothing to report yet, apart from more stable CIs and updated builds

Challenges or Risks

Minor: testing Spark 4 support on the CI when Spark runs on YARN should require emulating a minimal YARN 3 cluster, while the existing tests only emulate a YARN 2 one. But the help of LLMs should greatly lower the time needed to get that working.

Budget Update

2.5 days of work done since the last report, so 3.5 days of work done overall, over 39.5 days planned

Next Steps

April 2026

Summary of Work Completed

Mainly updates, stabilizing CI, on-going work on bugs and satellite projects

Deliverables/Milestones

Nothing to report yet, work has just started

Challenges or Risks

Nothing to report here

Budget Update

One day of work over 39.5 days planned

Next Steps

Keep updating things and stabilizing CI, reviewing opened issues and trying to get agents to work on issues or explore things to help address them