Skip to content

1.0.0-beta.2 - Synchronize Dapter version with release workflow

Pre-release
Pre-release

Choose a tag to compare

@allanmcarvalho allanmcarvalho released this 18 Nov 22:53
· 6 commits to 1.x since this release

Changed

  • Version synchronization with release workflow: Updated Dapter::VERSION from 1.0.0-beta.1 to 1.0.0-beta.2.
  • Extended versioning lifecycle integration: The Dapter class now participates in the versioning lifecycle by implementing BeforeVersioning (in addition to existing Versionable and WithReadmeHead).
  • Pre-versioning hook executes frontend npm steps: Added a beforeVersioning(string $current, string $next): void hook that:
    • Runs npm version $next --no-git-tag-version --allow-same-version --ignore-scripts from the project root.
    • Then runs npm run release:build.

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.1 release line:
    • Updated README references to reflect the move to the beta.1 published behavior/version (including the badge/text and Composer install command).
    • Updated resources/boost/skills/dapter-development/SKILL.md to reference 1.0.0-beta.1, including the stated current version (Dapter::VERSION) and wording around local preview vs. Dapter beta.1.

User-visible impact

  • No runtime/functional changes—documentation consistency only.

Migration

  • None required for users.