Release Process

Releasing packages to pub.dev

• Update package version and add notes to CHANGELOG.md file for it
  • In case of rx_bloc_cli package, make sure rxBlocCliPackageVersion constant is updated to reflect the current version
• Create a PR from develop to the master branch.
• Take notes, which packages need to be released, based on the package change log files shown in the PR.
• Merge the PR.
• Create a release for each package based on the notes
  • Set the tag name in the Choose a tag field, following the established pattern.
    • Pattern: {packageName}-v{major}.{minor}.{patch}
    • Example: rx_bloc_cli-v3.3.1
  • Set the master branch in the Target field.
  • Set the release title (the same as the tag name).
  • Set the release notes based on the package change log.
  • Submit the form by through the Publish release button.
• Inside the Actions tab of the repository, find the active workflow with the name Publish {packageName} to pub.dev
• Review and approve the pending deployment Github workflow pipeline