-
Notifications
You must be signed in to change notification settings - Fork 1
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
chore(main): Release transformation-azure-compliance-premium v0.3.0 #476
Merged
john-s58
merged 3 commits into
main
from
release-please--branches--main--components--transformation-azure-compliance-premium
Jan 17, 2024
Merged
chore(main): Release transformation-azure-compliance-premium v0.3.0 #476
john-s58
merged 3 commits into
main
from
release-please--branches--main--components--transformation-azure-compliance-premium
Jan 17, 2024
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
cq-bot
force-pushed
the
release-please--branches--main--components--transformation-azure-compliance-premium
branch
4 times, most recently
from
January 4, 2024 10:12
012538e
to
d9af3e0
Compare
cq-bot
force-pushed
the
release-please--branches--main--components--transformation-azure-compliance-premium
branch
3 times, most recently
from
January 16, 2024 14:20
f263daa
to
2d49eb4
Compare
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
cq-bot
force-pushed
the
release-please--branches--main--components--transformation-azure-compliance-premium
branch
from
January 17, 2024 09:04
2d49eb4
to
30a302d
Compare
cq-bot
changed the title
chore(main): Release transformation-azure-compliance-premium v0.2.1
chore(main): Release transformation-azure-compliance-premium v0.3.0
Jan 17, 2024
cq-bot
force-pushed
the
release-please--branches--main--components--transformation-azure-compliance-premium
branch
from
January 17, 2024 11:01
30a302d
to
5485eee
Compare
…transformation-azure-compliance-premium
…transformation-azure-compliance-premium
john-s58
approved these changes
Jan 17, 2024
john-s58
deleted the
release-please--branches--main--components--transformation-azure-compliance-premium
branch
January 17, 2024 16:37
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
🤖 I have created a release beep boop
0.3.0 (2024-01-17)
Features
Bug Fixes
This PR was generated with Release Please. See documentation.