gh-actions: support 2.0 slack that contains a breaking change and the signature changed

v1v commented 2 days ago

What is the problem this PR solves?

Bump the version

How does this PR solve the problem?

// Explain HOW you solved the problem in your code. It is possible that during PR reviews this changes and then this section should be updated.

How to test this PR locally

Design Checklist

[ ] I have ensured my design is stateless and will work when multiple fleet-server instances are behind a load balancer.
[ ] I have or intend to scale test my changes, ensuring it will work reliably with 100K+ agents connected.
[ ] I have included fail safe mechanisms to limit the load on fleet-server: rate limiting, circuit breakers, caching, load shedding, etc.

Checklist

[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] I have made corresponding change to the default configuration files
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I have added an entry in ./changelog/fragments using the changelog tool

Related issues

mergify[bot] commented 2 days ago

This pull request does not have a backport label. Could you fix it @v1v? 🙏 To fixup this pull request, you need to add the backport labels for the needed branches, such as:

backport-./d./d is the label to automatically backport to the 8./d branch. /d is the digit

mergify[bot] commented 2 days ago

backport-8.x has been added to help with the transition to the new branch 8.x. If you don't need it please use backport-skip label and remove the backport-8.x label.