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.

Sign up for GitHub

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

Already on GitHub? Sign in to your account

Jump to bottom

chore(main): release 1.2.0 #21

Merged
merged 1 commit into from
Jun 22, 2022
Merged

chore(main): release 1.2.0 #21

merged 1 commit into from
Jun 22, 2022

Conversation

github-actions[bot]
Copy link
Contributor

@github-actions github-actions bot commented Jun 21, 2022 •
edited by team-integrations-fnm-bot
Loading

馃 I have created a release beep boop

1.2.0 (2022-06-22)

Features

This PR was generated with Release Please. See documentation.

@team-integrations-fnm-bot team-integrations-fnm-bot force-pushed the release-please--branches--main--components--release-please-action branch from 20a2929 to ef904ca Compare June 22, 2022 04:19
@jbristowe jbristowe merged commit a2216cb into main Jun 22, 2022
@jbristowe jbristowe deleted the release-please--branches--main--components--release-please-action branch June 22, 2022 04:20
@team-integrations-fnm-bot
Copy link
Contributor

馃 Release is at https://github.com/OctopusDeploy/message-contracts.ts/releases/tag/v1.2.0 馃尰

@octoreleasebot
Copy link

PR did not have successful (green) build statuses, as required by our PRGB policy.
Justification provided by John Bristowe (@jbristowe) was:

Release management PR for repository via Release-Please

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@jbristowe jbristowe jbristowe approved these changes

Assignees
No one assigned
Labels
autorelease: tagged
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
3 participants
@team-integrations-fnm-bot @octoreleasebot @jbristowe