Bump slackapi/slack-github-action from 1.27.0 to 2.0.0 in /.github/workflows

[dependabot]

Bumps slackapi/slack-github-action from 1.27.0 to 2.0.0.

Release notes

Sourced from slackapi/slack-github-action's releases.

Slack Send v2.0.0

YAML! And more API methods! With improved erroring! And more!

Sending data to Slack can now be done with the YAML format, and that data can be sent to [a Slack API method][methods] or technique of choice with the provided payload. And additional configurations can improve error handling or customize values between steps.

Breaking changes happen with this update and recommended migration strategies are detailed below. Adding this step to new workflows might prefer to follow the README instead 📚

What's changed

Both inputs of payload variables, techniques for sending the payload, additional configurations, and expected outputs were changed:

• Sending variables
  • Breaking changes
    • Only one payload input can be provided
    • Only one technique to send can be provided
    • Variable replacements no longer happen by default
    • Payload file path parsed option was removed
  • Enhancements
    • Payloads can now be written in YAML
    • Payload can now be written in unwrapped JSON
• Sending techniques
  • Technique 1: Slack Workflow Builder
    • Breaking changes
      • The webhook type must be specified in webhook inputs
      • Payload flattening no longer happens by default
    • Enhancements
      • The webhook URL can be specified in webhook inputs
  • Technique 2: Slack API method
    • Breaking changes
      • The Slack API method now must be specified in inputs
      • A token must be provided with other inputs
      • Inputs to the Slack API method must be provided in payloads
      • Messages cannot be sent to multiple channels in one step
  • Technique 3: Slack incoming webhook
    • Breaking changes
      • The webhook type must be specified for incoming webhooks
    • Enhancements
      • The webhook URL can be specified for incoming webhook
• Additional configurations
  • Enhancements
    • Steps can exit with an error after a failed Slack API call
    • Failed requests can be retried various amounts of times
    • Provided payloads can be flattened with a delimiter
    • Provided payloads can have templated variables replaced
    • Proxying HTTPS requests can be done within inputs
• Expected outputs
  • Breaking changes
    • The time value is now returned as the Unix epoch time
  • Enhancements
    • An ok value is added to represent response success

... (truncated)

Commits

• 485a9d4 Release
• e598089 chore(release): tag version 2.0.0
• e9b3a6b feat!: wrap payloads to send to a "method" with "token" or "webhook" (#333)
• 74ae656 chore(release): tag version 1.27.1
• bd0e281 build(deps): bump codecov/codecov-action from 4.5.0 to 4.6.0 (#355)
• e127529 build(deps): bump @​actions/core from 1.10.1 to 1.11.1 (#354)
• 6b51022 build(deps-dev): bump eslint-plugin-jsdoc from 50.3.1 to 50.4.3 (#353)
• 555e4ad build(deps-dev): bump eslint-plugin-import from 2.30.0 to 2.31.0 (#352)
• 8d4500e build(deps): bump @​slack/web-api from 7.5.0 to 7.7.0 (#351)
• d0dece6 build(deps-dev): bump mocha from 10.7.3 to 10.8.2 (#350)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

🛠️ PR Summary

_{Made with ❤️ by Ultralytics Actions}

🌟 Summary

The GitHub Actions workflow for YOLOv3 has been updated to improve integration with Slack notifications.

📊 Key Changes

• Updated the Slack GitHub Action from version 1.27.0 to 2.0.0 in the continuous integration (CI) workflow configuration.

🎯 Purpose & Impact

• Improved Notifications: The update to the latest Slack GitHub Action ensures more reliable and feature-rich notifications in Slack channels when CI tests fail or are cancelled. 🛠️
• Enhanced Compatibility: Upgrading to the newer version potentially fixes bugs and provides better performance and compatibility with other GitHub Actions. 🚀

[UltralyticsAssistant]

👋 Hello @dependabot[bot], thank you for submitting a 🚀 PR to the ultralytics/yolov3 repository! To ensure smooth integration of your updates, please consider the points below:

• ✅ Purpose Explanation: Clearly outline the purpose of the action version upgrade in the PR description. Link to any related issues within the project on the Ultralytics Issues Page.
• ✅ Branch Syncing: Make sure your PR is up-to-date with the main branch of ultralytics/yolov3. If needed, click the 'Update branch' button or execute git pull and git merge main locally to resolve any conflicts.
• ✅ CI Check Verification: Ensure all Continuous Integration (CI) processes for Ultralytics are passing. Any failures should be addressed promptly.
• ✅ Documentation Update: If your changes introduce new behavior, the relevant sections in the Ultralytics Documentation should reflect these changes.
• ✅ Test Coverage: Include tests that sufficiently cover modifications in your PR. Validate that all tests, including new ones, pass successfully.
• ✅ CLA Signature: Signing of our Contributor License Agreement is necessary if this is your first contribution. Indicate your acknowledgment by stating "I have read the CLA Document and I sign the CLA" in this PR.
• ✅ Conciseness in Modification: Ensure that the changes are minimal and strictly necessary for your update. "Less is more," as they say.

Feel free to refer to our Contributing Guide for more information. An Ultralytics engineer will be on hand to assist you soon. Thank you for your contributions to the YOLOv3 project! 🌟