Skip to content

ci: automatically send a slack message for new releases #1356

New issue

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

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

Already on GitHub? # to your account

Open
wants to merge 9 commits into
base: dev
Choose a base branch
from

Conversation

MoKamall
Copy link

@MoKamall MoKamall commented Mar 6, 2025

Description of the change

Send Slack messages automatically upon releasing new versions of the SDK.

Type of change

  • Bug fix (non-breaking change that fixes an issue)
  • New feature (non-breaking change that adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)

Related issues

https://instabug.atlassian.net/browse/MOB-17130

Checklists

Development

  • Lint rules pass locally
  • The code changed/added as part of this pull request has been covered with tests

Code review

  • This pull request has a descriptive title and information useful to a reviewer
  • Issue from task tracker has a link to this pull request

@InstabugCI
Copy link
Collaborator

InstabugCI commented Mar 6, 2025

Coverage Report

Label Coverage Status
JavaScript 95.2%
Android 50.2%
iOS 51.6%

Generated by 🚫 dangerJS against 90ad56b

@MoKamall MoKamall marked this pull request as ready for review March 9, 2025 02:48
@MoKamall MoKamall self-assigned this Mar 9, 2025
Copy link
Contributor

@AndrewAminInstabug AndrewAminInstabug left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@MoKamall Great effort ... Could you take a look at the jobs that failed in the CI?

Copy link
Contributor

@AndrewAminInstabug AndrewAminInstabug left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@MoKamall Could you review the failed jobs? They don't appear to be caused by flakiness and require resolution.

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants