Skip to content

v4.1.0

Choose a tag to compare

View all tags
@mkocansey mkocansey released this 08 Jun 13:31
· 136 commits to main since this release
v4.1.0
bcfca0a

Individual component packages are now available

This release fixes the CI pipeline that splits each packages/* directory into its own installable repo. All 43 individual component packages (mkocansey/bladewind-button, mkocansey/bladewind-table, mkocansey/bladewind-accordion, etc.) are published and installable from Packagist**, alongside the full mkocansey/bladewind package.

If you only need a handful of components, you can now install just what you use:

composer require mkocansey/bladewind-accordion
composer require mkocansey/bladewind-table

…or pull in everything as before:

composer require mkocansey/bladewind

Fixed

  • Split-package publishing was silently broken since the restructuring. The GitHub Action responsible for mirroring each packages/* directory into its own repo was passing the access token through an input the action doesn't support, causing every job to report "success" while pushing nothing. Fixed by passing the token via the correct environment variable. (#3e07eda)
  • Split repos were never receiving version tags, so Packagist had no releases to register even once content started landing. The workflow now passes the triggering tag through to each split destination. (#13f84ae)

Removed

  • Permanently removed the workflow entry that would have split packages/meta into a repo named bladewind — that name belongs to this monorepo's own GitHub remote, and the entry being live caused a serious incident where the split action force-overwrote this repo's main branch with just three files.

Docs

  • Corrected RELEASING.md: fixed an incorrect repo-name reference and replaced an inaccurate claim about how mkocansey/bladewind resolves on Packagist with an accurate description of the architecture, plus a prominent warning against ever naming a split target bladewind. (#bcfca0a)

Internal

  • Bumped inter-package version constraints from ^4.0 to ^4.1 to start the next development iteration, per the standard monorepo-builder release flow. (#b49028b)

Full changelog: [v4.0.0...v4.1.0](https://github.com/mkocansey/bladewind/compare/v4.0.0...v4.1.0)

Assets 2
Loading