feat: make app install fetch fresh resources by default - #2633
Conversation
|
Important Review skippedAuto reviews are limited based on label configuration. 🏷️ Required labels (at least one) (1)
Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
koppor
changed the title
--fresh" to update--fresh to app install update example
|
Not sure I follow - why should we add --fresh here for something that is not using snapshot ? Always fresh is waste of time 99% of the time... ...and update should happen every 24hrs I believe. Wondering if should default to fresh on install ? Be lazy on runs? |
Yeah, good idea :) |
Installing an app is a rare, explicit act, so it now resolves sources and dependencies freshly unless `--no-fresh` or `--offline` is given. Running apps stays cached. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01TbfSDMWfD3o31bg28NJNbS
koppor
changed the title
--fresh to app install update exampleapp install fetch fresh resources by default
2 participants
🤖 Copy-pasting
jbang app install --force <app>did not pick up updated -SNAPSHOT dependencies, because installs reused cached resources. Following the suggestion in the review,app installnow defaults to fresh resolution while runs stay lazy;--no-freshor--offlineopts back out.Test:
jbang app install --force gavsearch@jbangdevpicks up a new snapshot;--no-freshdoes not.🤖 Generated with Claude Code