Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(releasing): Explicitly specify from which branch the release tag should be created from OCRVS-7369 #245

Merged
merged 5 commits into from
Aug 21, 2024

Conversation

rikukissa
Copy link
Member

@rikukissa rikukissa commented Aug 21, 2024

A few small fixes here:

  • Fix tagging mechanism so it always uses the branch defined as the "Branch to build from"
  • Add descriptive commit messages to merge commits created by the pipeline
  • Use the "Release tag" input as the tag to be created instead of reading a version from package.json
  • Remove v___ prefix from tags to allow countries use whatever versioning scheme

This comment has been minimized.

@rikukissa rikukissa changed the title fix(releasing): Explicitly specify from which branch the release tag should be created from fix(releasing): Explicitly specify from which branch the release tag should be created from OCRVS-7369 Aug 21, 2024
@rikukissa rikukissa added this to the v1.6.0 milestone Aug 21, 2024
@rikukissa rikukissa merged commit be333a1 into develop Aug 21, 2024
github-actions bot pushed a commit that referenced this pull request Aug 21, 2024
Zangetsu101 added a commit that referenced this pull request Sep 19, 2024
🍒 Merge changes from PR #245 to release-v1.6.0
@rikukissa rikukissa deleted the fix-publish-pipeline branch January 10, 2025 07:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants