here's my december adventure log. it would be mostly coding sbt, but some mix of food, music, skate stuff too

day 1: fixed a Scala 3 compiler warning in sbt 2.x that gets displayed to the user
https://eed3si9n.com/december-adventure-2024/ #DecemberAdventure

#DecemberAdventure day 2
sent 'Artifact publishing proposal' proposal to Scala Center. the gist of the proposal is to consolidate the effort around publishing changes.

released sbt-jupiter-interface 0.13.3, featuring bug fix contributed by Li Haoyi

at night, worked on the december mixtape
https://eed3si9n.com/december-adventure-2024/

#DecemberAdventure day 3
went skating in the morning before work. 8.25 inch + AF-1 still feels heavy compared to previous setups

no night hacking but did a small writeup of sbt 2.x bug fix (https://github.com/sbt/sbt/pull/7925) wherein source dependency `ProjectRef(file("a1"), "a1")` was resulting in "Invalid build URI" on sbt 2.x
https://eed3si9n.com/december-adventure-2024/#3

#DecemberAdventure day 4
`java.net.URL` infamously calls out to the network to perform `equals`, so likely we should avoid the use of it in setting keys and data types, which might be involved in caching. so I've sent https://github.com/sbt/sbt/pull/7927 to change all the keys to `URI`

this also cherry picks a commit from a dormant PR that changes licenses from a tuple `(String, URL)` to a data type
https://eed3si9n.com/december-adventure-2024/#4

#DecemberAdventure day 5
my two cents on compilers: compilers should be silent if it did exactly what was told. any warnings should be actionable such that the user can get rid of the warning somehow. `-Xmigration` notices might be an exception.

as a low effort exploration, I decided to try the next Scala 3.x, Scala 3.6.2-RC3. unfortunately the compilation failed under `-Xfatal-warnings` because Scala 3.6.2-RC3 threw unactionable notices as warning.
https://eed3si9n.com/december-adventure-2024/#5