Publishing

Commercial license

Renick.Content is proprietary, source-available software (LICENSE.md); only the block content format is MIT. It ships through the October Marketplace and private Composer/Git access, never through public Packagist.

How October distribution works

1. Everything is a Composer package of type: october-plugin: renick/content-plugin installs into plugins/renick/content.
2. Releases are git tags plus updates/version.yaml. Composer installs the latest stable tag and the October gateway reads version.yaml, so the newest entry must equal the latest tag.
3. Tooling reads the repository root, so composer.json must sit at the root of the published repo.

The distribution repo

The plugin is published to renickbuettner/content-editor-plugin, whose root is the plugin, as a single snapshot commit without monorepo history. A push to main updates its main (deploy-plugin.yml). A v* tag publishes the release, the tag and the GitHub Release (release-plugin.yml). A release exists only once its tag is on that repo.

Version discipline

Append the version to plugins/renick/content/updates/version.yaml with the same heading in CHANGELOG.md, commit, then tag:

git tag -a v1.0.7 -m v1.0.7
git push origin v1.0.7

Always bump PATCH, features included; MAJOR is only for breaking changes to the document format or the REST contract. Never rename a released version.yaml entry, or October runs its migrations again.

Dist-only shipping

The plugin's .gitattributes (export-ignore) decides what ships. That is all PHP, blocks, schema, language files and the built assets/dist and assets/frontend, but no editor sources, build configs, tests or internal notes. Installing never needs Node, pnpm or a build step.