Skip to content

Sync latest dev-tools assets into framework (issue 1) #1

@coisa

Description

@coisa

Problem

The framework repository needs a full dev-tools asset backfill so newly published DevTools updates can be propagated, including changelog/release metadata. This also needs to run in an ordered way to avoid partial/manual drift.

Proposal

Run the DevTools sync pipeline in repository framework to sync all shared assets and CI resources from php-fast-forward/dev-tools, then review and commit the generated file changes.

Scope

  • Pull latest fast-forward/dev-tools changes into the repo via Composer.
  • Run composer dev-tools:sync --overwrite.
  • Review generated files and include all expected diffs.
  • Perform changelog backfill (changelog metadata consistency for existing releases).
  • Update release description text for already published releases if sync regenerates release-related metadata.

Why this is needed

Maintaining framework aligned with current dev-tools assets reduces configuration drift and guarantees shared governance, workflow behavior, changelog tooling, and release handling are consistent across repositories.

Proposed Execution Plan

  1. Update dependencies (composer update to pull latest fast-forward/dev-tools).
  2. Run composer dev-tools:sync --overwrite.
  3. Validate resulting diffs in:
    • workflows
    • .github resources
    • changelog/release-related metadata.
  4. Backfill changelog artifacts and reconcile release descriptions for previously published releases.
  5. Prepare commit for review once all generated files are validated.

Acceptance Criteria

  • composer update executed and fast-forward/dev-tools updated to current main.
  • composer dev-tools:sync --overwrite completed without errors.
  • All generated changes from sync are committed.
  • Changelog backfill is completed for historical/unresolved entries impacted by resource changes.
  • Release descriptions for existing published releases are updated/normalized according to current sync output.
  • A PR can be opened from this work with all generated files tracked and consistent.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions