Skip to content

trigger release pipeline after reverting MR !235

Jannik Lehmannrequested to merge
trigger-release-pipeline into main

This MR creates an empty commit with conventional commit formatting to trigger the release pipeline.

Background

  • MR !235 (merged) successfully reverted the changes from MR !227 (merged) that were causing users to be unable to type 'y' and 'z' in Duo chat input
  • However, the revert merge commit did not follow conventional commit format
  • This prevented our semantic-release pipeline from automatically creating a new release
  • We need to publish a new version to ensure the revert reaches users

Changes

  • Empty commit with conventional commit message: chore: trigger release pipeline after reverting MR !235
  • No code changes - this is purely to trigger the automated release process

Merge request reports