Repository navigation
1.0.0-beta.2 - Synchronize Dapter version with release workflow
Pre-release
Pre-release
·
6 commits
to 1.x
since this release
Changed
- Version synchronization with release workflow: Updated
Dapter::VERSIONfrom1.0.0-beta.1to1.0.0-beta.2. - Extended versioning lifecycle integration: The
Dapterclass now participates in the versioning lifecycle by implementingBeforeVersioning(in addition to existingVersionableandWithReadmeHead). - Pre-versioning hook executes frontend npm steps: Added a
beforeVersioning(string $current, string $next): voidhook that:- Runs
npm version $next --no-git-tag-version --allow-same-version --ignore-scriptsfrom the project root. - Then runs
npm run release:build.
- Runs
User-visible impact
- During versioning/release, the versioning workflow will now automatically trigger the npm commands above to keep the frontend/package version aligned and to rebuild/validate the frontend.
Compatibility and migration
- Library consumers: No migration required.
- Maintainers/release operators: Be aware that versioning will execute npm commands; if the npm steps fail, the versioning process may fail as well.
Documentation
- Aligned README and Boost skill docs with the published
beta.1release line:- Updated README references to reflect the move to the
beta.1published behavior/version (including the badge/text and Composer install command). - Updated
resources/boost/skills/dapter-development/SKILL.mdto reference1.0.0-beta.1, including the stated current version (Dapter::VERSION) and wording around local preview vs.Dapter beta.1.
- Updated README references to reflect the move to the
User-visible impact
- No runtime/functional changes—documentation consistency only.
Migration
- None required for users.