chore(deps): update dependency slack to v6

[TalkIQ (talkiq-ops)]

This PR contains the following updates:

Package	Type	Update	Change
slack	orb	major	5.2.3 -> 6.0.0

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Renovate Bot.

[github-actions]

Approved 👍

[gemini-code-assist]

Summary of Changes

Hello TalkIQ (@talkiq-ops), I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request updates the slack CircleCI orb to its latest major version. This ensures that the project benefits from the newest features, improvements, and security patches provided by the orb, maintaining compatibility and leveraging the most current tooling for CI notifications.

Highlights

• Dependency Update: The slack CircleCI orb has been updated to its major version 6.0.0 from 5.2.3.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	Gemini (@gemini-code-assist)	Responds in comments when explicitly tagged, both in issue comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on Gemini (@gemini-code-assist) comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request updates the circleci/slack orb from version 5.2.3 to 6.0.0. This is a major version update which introduces breaking changes. I've found a critical issue where the slack-on-fail command will fail due to a change in how custom slack messages are handled. The custom parameter in the slack/notify command now expects a file path instead of a raw JSON string. I've provided a detailed comment on how to fix this by writing the JSON payload to a temporary file and passing its path to the custom parameter. Please review the suggested changes to ensure your CI notifications continue to work correctly.

[gemini-code-assist]

Upgrading the circleci/slack orb to version 6.0.0 introduces a breaking change that will cause the slack-on-fail command to fail.

In v6.0.0, the custom parameter of the slack/notify command no longer accepts a raw JSON string. Instead, it requires a path to a file containing the JSON payload.

To fix this, you need to modify the slack-on-fail command (defined on lines 17-95) to first write the custom JSON payload to a file, and then pass the path to that file to the slack/notify command.

Here is an example of how you could modify the steps in the slack-on-fail command:

    steps:
      - run:
          name: install curl
          command: |
            if which curl >/dev/null; then
              exit 0
            elif which apk >/dev/null; then
              apk add --no-cache --no-progress curl curl-dev
            elif which apt-get >/dev/null; then
              apt-get update -qy
              apt-get install -qy curl
            else
              echo >&2 "ERROR: could not find supported package manager"
              exit 1
            fi
      - run:
          name: Create custom slack message for failed job
          command: |
            cat <<'EOF' > /tmp/slack_fail_template.json
            {
              "blocks": [
                {
                  "type": "header",
                  "text": {
                    "type": "plain_text",
                    "text": "Job Failed :x:",
                    "emoji": true
                  }
                },
                {
                  "type": "section",
                  "fields": [
                    {
                      "type": "mrkdwn",
                      "text": "Job name: `${CIRCLE_JOB}`"
                    },
                    {
                      "type": "mrkdwn",
                      "text": "Repository name: `${CIRCLE_PROJECT_REPONAME}`"
                    },
                    {
                      "type": "mrkdwn",
                      "text": "Branch `${CIRCLE_BRANCH}`"
                    },
                    {
                      "type": "mrkdwn",
                      "text": "Blame :point_right: @${CIRCLE_USERNAME}"
                    }
                  ]
                },
                {
                  "type": "actions",
                  "elements": [
                    {
                      "type": "button",
                      "text": {
                        "type": "plain_text",
                        "text": "View Job"
                      },
                      "url": "${CIRCLE_BUILD_URL}"
                    }
                  ]
                }
              ]
            }
            EOF
      - slack/notify:
          channel: <<parameters.channel>>
          event: fail
          custom: /tmp/slack_fail_template.json

This change preserves the install curl step, adds a new step to create the JSON template file, and updates the slack/notify call to use this file. The empty text field from the original JSON has been removed as it's not necessary when using blocks.