feat: automate announcements for pre release #786
Merged
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
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #786 +/- ##
=======================================
Coverage 82.97% 82.97%
=======================================
Files 37 37
Lines 4200 4200
=======================================
Hits 3485 3485
Misses 715 715 ☔ View full report in Codecov by Sentry. |
RafaelGSS
approved these changes
Mar 27, 2024
|
@marco-ippolito can you fix lint so I can merge it? |
Co-authored-by: Rafael Gonzaga <rafael.nunu@hotmail.com>
marco-ippolito
force-pushed
the
feat/pre-notification
branch
from
581f94f
to
7bf793c
Compare
RafaelGSS
approved these changes
Mar 28, 2024
This was referenced Mar 28, 2024
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.
This pr allows to automatically create an issue on node-docker repository to announce the security release.
Next step is automate the announcement on google groups