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

Check renovate config, update Pi dep #16

New issue
Closed
opened 2026-07-18 07:32:11 +00:00 by alex · 2 comments
alex commented 2026-07-18 07:32:11 +00:00
Owner
Copy link
No description provided.
alex commented 2026-07-18 07:32:53 +00:00
Author
Owner
Copy link

/pi open a new PR, it seems renovate bot doesn't keep the pi dependency up to date

/pi open a new PR, it seems renovate bot doesn't keep the pi dependency up to date
pi commented 2026-07-18 07:35:20 +00:00
Contributor
Copy link

Now let me update the package.json dependency and the lockfile:The dependency is now bumped from 0.80.2 to 0.80.10. Now let me improve the renovate config so it keeps this dependency up to date going forward:All changes look good. Let me create the PR:PR #17 created: #17

What was done:

  1. Bumped the dependency — @earendil-works/pi-coding-agent 0.80.2 → 0.80.10 in both package.json and bun.lock (the lockfile was the part that had fallen behind, since ^0.80.2 already satisfied 0.80.10).

  2. Fixed the Renovate config — The reason Renovate wasn't keeping pi up to date: when a new release satisfies the existing range (like ^0.80.x already matching 0.80.10), the only thing needed is a lockfile refresh, which is governed by lockFileMaintenance. That wasn't enabled explicitly and defaulted to a weekly schedule, so these in-range bumps slipped through. Added extends: ["config:recommended"] and enabled lockFileMaintenance (daily, before 6am) to fix it going forward.

View action run | Model: zai/glm-5.2 (thinking: max) | Time: 2m 20s | Tokens: 119.9K | Pi SDK v0.80.7 | Action v2.26.0

Now let me update the package.json dependency and the lockfile:The dependency is now bumped from `0.80.2` to `0.80.10`. Now let me improve the renovate config so it keeps this dependency up to date going forward:All changes look good. Let me create the PR:PR #17 created: https://forge.l3x.in/alex/pi-shared/pulls/17 **What was done:** 1. **Bumped the dependency** — `@earendil-works/pi-coding-agent` `0.80.2` → `0.80.10` in both `package.json` and `bun.lock` (the lockfile was the part that had fallen behind, since `^0.80.2` already satisfied `0.80.10`). 2. **Fixed the Renovate config** — The reason Renovate wasn't keeping pi up to date: when a new release satisfies the *existing* range (like `^0.80.x` already matching `0.80.10`), the only thing needed is a lockfile refresh, which is governed by `lockFileMaintenance`. That wasn't enabled explicitly and defaulted to a weekly schedule, so these in-range bumps slipped through. Added `extends: ["config:recommended"]` and enabled `lockFileMaintenance` (daily, `before 6am`) to fix it going forward. --- [View action run](https://forge.l3x.in/alex/pi-shared/actions/runs/21) | Model: zai/glm-5.2 (thinking: max) | Time: 2m 20s | Tokens: 119.9K | Pi SDK v0.80.7 | Action v2.26.0
alex closed this issue 2026-07-18 07:38:35 +00:00
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
master
pi/issue21-1784722296188
No results found.
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#16
No description provided.