Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 5 additions & 1 deletion CHANGES.md
Original file line number Diff line number Diff line change
Expand Up @@ -3,7 +3,11 @@
## 7.0.0b9 (unreleased)


- Nothing changed yet.
- Prefer the installed `plonecli` (on `PATH`, e.g. via `uv tool install
plonecli`) over `uvx` in the skill's invoke docs, so the user's
installed/pinned version runs instead of a separate PyPI-resolved copy.
`uvx` is now documented as a no-install fallback.
[MrTango]


## 7.0.0b8 (2026-05-24)
Expand Down
3 changes: 2 additions & 1 deletion plonecli/skills/plonecli/SKILL.md
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,8 @@ description: Scaffold and develop Plone packages with plonecli (copier-template

## How to invoke it

- **End users:** `uvx plonecli <command>` (no install needed).
- **Installed (preferred):** `plonecli <command>` — if `plonecli` is on `PATH` (e.g. via `uv tool install plonecli`), always use the bare command so the user's installed/pinned version runs.
- **Not installed / one-off:** `uvx plonecli <command>` (no install needed). Only fall back to this when `plonecli` is not on `PATH`.
- **Inside this repo (plonecli's own source):** it is not on `PATH` — use `uv run plonecli <command>`.

On first run, plonecli clones the copier-templates to `~/.copier-templates/plone-copier-templates`. If a command complains about missing templates, run `plonecli update` first.
Expand Down
Loading