From 48133806a0284a4c4223f968ff81569fbcb0e66e Mon Sep 17 00:00:00 2001 From: DanMat Date: Tue, 21 Jul 2026 14:46:45 -0400 Subject: [PATCH] docs: state the dev-main dependency and what it costs composer require nimbuscms/markdown does not work outside the project yet: nothing is on Packagist, so this package requires core through a VCS repository at dev-main. Every build here tracks core's main and cannot pin, so a breaking change to core breaks this plugin's CI the moment it merges. That is the right trade while the API is still moving, but it belongs where a plugin author hits it rather than being discovered from a failing build. --- README.md | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/README.md b/README.md index be713f5..4cdcaf1 100644 --- a/README.md +++ b/README.md @@ -14,6 +14,15 @@ the contract rather than its own complexity. composer require nimbuscms/markdown ``` +> **Not on Packagist yet.** Neither this plugin nor core is published, so that +> command does not work outside the project today. Until core tags `0.1.0` and +> both are published, this package requires core through a VCS repository at +> `dev-main` — see `composer.json`. That means every build here tracks core's +> `main` and cannot pin a version, so a breaking change to core breaks this +> plugin's CI the moment it merges. The path out is tracked under +> [Release & packaging](https://github.com/NimbusCMS/nimbus/blob/main/ROADMAP.md) +> in the core roadmap. + That is the whole installation. Nimbus discovers plugins through Composer's `installed.json` — there is no upload step and no in-admin installer, because downloading and executing arbitrary code from the web is a feature that needs