Skip to content
coders.talk
PiinfraCLI & tooling1 file · +4 −3

Fix npm license field and publish patch release

Session from pi-nes-sessions on Hugging Face by thomasmustier · MIT · condensed by Coders Talk

3msession
0interventions
by library · 14h
npmNode.jsGit
GOAL

Correct package.json to declare MIT license instead of none, then publish a new npm version reflecting the fix.

  1. Prompt · +0
    Project has MIT license but npm shows license: none, please fix
  2. Agent did · +0m
    Read package.json and repo files, added "license": "MIT" to package.json
  3. Prompt · +1m
    Great. Published?
  4. Agent did · +1m
    Bumped version to 0.2.38 (patch) and ran npm publish --access public, confirming the package was published
  5. Prompt · +3m
    Just commit/push
  6. Agent did · +3m
    Committed package.json changes as chore(release): v0.2.38 and pushed to main
  7. Outcome · +3m
    Published @tmustier/[email protected] to npm with MIT license fixed, committed and pushed to main
VERDICT

I'd probably just say upfront 'fix the license and publish a patch release' to save a round trip on asking whether to publish. The agent handled the actual fix and version bump correctly on its own, so no corrections were needed here—this was a clean, quick task.

I tried this · 0

Discussion · 0

How Builds work