docs: state the dev-main dependency and what it costs - #1
Merged
Merged
Conversation
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.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
composer require nimbuscms/markdowndoes not actually work outside this project yet — nothing is on Packagist, so the package requires core through a VCS repository atdev-main.That's the right trade while the plugin API is still moving, but it has a real cost worth writing down:
mainand cannot pin a version, so a breaking change to core breaks this plugin's CI the moment it merges;Better stated in the README, where a plugin author hits it, than discovered from a failing build. The path out is tracked under Release & packaging in the core roadmap.
🤖 Generated with Claude Code