Migrating to v0.50.1

One flag now refuses where it used to be ignored.

sparks update --nameSection anchor link

  • Before: sparkwing pipeline sparks update --name LIB checked that LIB was declared and then re-resolved every library in the manifest, so pinning one library forward bumped the rest in the same overlay write.
  • After: the flag is refused. sparkwing pipeline sparks update with no flag re-resolves the whole manifest, which is what the command has always done.
  • Why: resolution rebuilds the overlay modfile from the whole manifest in one pass, so a filtered update would drop the other libraries' resolved versions. The flag's documented purpose was never implemented.
  • Gotchas: a script or CI step passing --name now exits non-zero. Drop the flag to update everything, or give a library an exact version: in .sparkwing/sparkwing.yaml to hold it still while the others move.