chore(deps): bump slackapi/slack-github-action from 3.0.2 to 3.0.5

[dependabot]

Bumps slackapi/slack-github-action from 3.0.2 to 3.0.5.

Release notes

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

Slack GitHub Action v3.0.5

Patch Changes

• 96fddbe: fix: revert multiline yaml parsing indentation change

Slack GitHub Action v3.0.4

Patch Changes

• fa03fe4: refactor: send webhooks with the @slack/webhook package

Slack GitHub Action v3.0.3

Patch Changes

• 66834e4: feat: add instrumentation to address error rates

Changelog

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

3.0.5

Patch Changes

• 96fddbe: fix: revert multiline yaml parsing indentation change

3.0.4

Patch Changes

• fa03fe4: refactor: send webhooks with the @slack/webhook package

3.0.3

Patch Changes

• 66834e4: feat: add instrumentation to address error rates

Commits

• 0d95c9a chore: release
• be88bdd chore: release (#639)
• 96fddbe fix: revert multiline yaml parsing indentation change (#638)
• e1f137c chore: release (#636)
• fa03fe4 refactor: send webhooks with the @​slack/webhook package (#630)
• 0539f0d build(deps): bump js-yaml from 4.2.0 to 5.2.0 (#635)
• 2a27647 build(deps): bump axios from 1.16.0 to 1.18.1 (#634)
• 84efc65 build(deps-dev): bump @​types/node from 24.12.4 to 24.13.2 (#633)
• c61fe04 build(deps-dev): bump @​biomejs/biome from 2.4.16 to 2.5.1 (#632)
• a2a5362 build(deps-dev): bump typescript from 6.0.2 to 6.0.3 (#631)
• 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 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)

[rhacs-bot]

A single node development cluster (infra-pr-1883) was allocated in production infra for this PR.

CI will attempt to deploy quay.io/rhacs-eng/infra-server: to it.

🔌 You can connect to this cluster with:

gcloud container clusters get-credentials infra-pr-1883 --zone us-central1-a --project acs-team-temp-dev

🛠️ And pull infractl from the deployed dev infra-server with:

nohup kubectl -n infra port-forward svc/infra-server-service 8443:8443 &
make pull-infractl-from-dev-server

🔓 You must go to to export an . Your token from the prod infra instance will not work with dev environments.

🚲 You can then use the dev infra instance e.g.:

bin/infractl -k -e localhost:8443 whoami

⚠️ Any clusters that you start using your dev infra instance should have a lifespan shorter then the development cluster instance. Otherwise they will not be destroyed when the dev infra instance ceases to exist when the development cluster is deleted. ⚠️

Further Development

☕ If you make changes, you can commit and push and CI will take care of updating the development cluster.

🚀 If you only modify configuration (chart/infra-server/configuration) or templates (chart/infra-server/{static,templates}), you can get a faster update with:

make helm-deploy

Logs

Logs for the development infra depending on your @redhat.com authuser:

• authuser=0
• authuser=1
• authuser=2

Or:

kubectl -n infra logs -l app=infra-server --tail=1 -f