alex/pi-shared
Watch
1
0
Fork
You've already forked pi-shared
 0
Code Issues 1 Pull requests Activity Actions

chore(deps): bump @earendil-works/pi-coding-agent to 0.80.10 and fix renovate config #17

Merged
alex merged 2 commits from pi/issue16-1784360113294 into master 2026-07-18 07:38:35 +00:00
Conversation 0 Commits 2 Files changed 3 +11 -6
pi commented 2026-07-18 07:35:14 +00:00
Contributor
Copy link

Summary

Closes #16.

The @earendil-works/pi-coding-agent dependency had fallen behind: the lockfile was pinned at 0.80.2 while 0.80.10 was already published (and the ^0.80.2 range in package.json already satisfied it). Renovate was not picking up these in-range lockfile bumps.

Changes

1. Bump the dependency (package.json + bun.lock)

  • @earendil-works/pi-coding-agent: ^0.80.2 → ^0.80.10
  • Lockfile regenerated with bun install, which also bumps the related in-workspace packages (pi-agent-core, pi-ai, pi-tui) to 0.80.10.

2. Fix the Renovate config (renovate.json)

The root cause of Renovate not keeping pi up to date: when a new release satisfies the existing range in package.json (e.g. ^0.80.x already matching 0.80.10), the only change needed is a lockfile refresh. That is governed by lockFileMaintenance, which wasn't explicitly enabled and defaulted to a weekly schedule, so these updates slipped through.

  • Added extends: ["config:recommended"] to pick up the standard best-practice defaults.
  • Enabled lockFileMaintenance (daily, before 6am) so in-range version bumps like 0.80.2 → 0.80.10 get a lockfile refresh PR automatically.
  • Kept the existing rule that disables the alex/.profile Forgejo reusable workflow.

Verification

  • bun install resolved cleanly to @earendil-works/pi-coding-agent@0.80.10.
  • Both package.json and renovate.json validated as well-formed JSON.
## Summary Closes #16. The `@earendil-works/pi-coding-agent` dependency had fallen behind: the lockfile was pinned at `0.80.2` while `0.80.10` was already published (and the `^0.80.2` range in `package.json` already satisfied it). Renovate was not picking up these in-range lockfile bumps. ## Changes **1. Bump the dependency** (`package.json` + `bun.lock`) - `@earendil-works/pi-coding-agent`: `^0.80.2` → `^0.80.10` - Lockfile regenerated with `bun install`, which also bumps the related in-workspace packages (`pi-agent-core`, `pi-ai`, `pi-tui`) to `0.80.10`. **2. Fix the Renovate config** (`renovate.json`) The root cause of Renovate not keeping pi up to date: when a new release satisfies the *existing* range in `package.json` (e.g. `^0.80.x` already matching `0.80.10`), the only change needed is a lockfile refresh. That is governed by `lockFileMaintenance`, which wasn't explicitly enabled and defaulted to a weekly schedule, so these updates slipped through. - Added `extends: ["config:recommended"]` to pick up the standard best-practice defaults. - Enabled `lockFileMaintenance` (daily, `before 6am`) so in-range version bumps like `0.80.2 → 0.80.10` get a lockfile refresh PR automatically. - Kept the existing rule that disables the `alex/.profile` Forgejo reusable workflow. ## Verification - `bun install` resolved cleanly to `@earendil-works/pi-coding-agent@0.80.10`. - Both `package.json` and `renovate.json` validated as well-formed JSON.
Co-authored-by: alex <alex@forge.l3x.in>
alex merged commit 6115c35b75 into master 2026-07-18 07:38:35 +00:00
alex deleted branch pi/issue16-1784360113294 2026-07-18 07:38:35 +00:00
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels   
dependencies
Renovate stuff

No labels
dependencies
Milestone
Clear milestone
No items
No milestone
Assignees
Clear assignees
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
alex/pi-shared!17
No description provided.