Skip to content

Document release process #154

Description

@helmo

To prevent things like #151 it might be good to document the steps taken for a new release version.

What about adding this to the README.md?

Releases

  • Update version number in composer.json
  • Update composer hash with composer update --lock
  • Build a phar file for dist/scanner
  • Update version number in dist/version
  • Commit and set Git tag
  • Add release on GitHub
  • Celebrate 🥳

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions