Skip to content

docs: state the dev-main dependency and what it costs #1

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
DanMat merged 1 commit into from
Jul 21, 2026
Merged

docs: state the dev-main dependency and what it costs #1

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
9 changes: 9 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down
Loading