chore(deps): bump slackapi/slack-github-action from 2.1.0 to 2.1.1 #1606
Conversation
![dependabot[bot]](https://avatars.githubusercontent.com/in/29110?s=60&v=4){kind=small}
Bumps [slackapi/slack-github-action](https://github.com/slackapi/slack-github-action) from 2.1.0 to 2.1.1. - [Release notes](https://github.com/slackapi/slack-github-action/releases) - [Commits](slackapi/slack-github-action@v2.1.0...v2.1.1) --- updated-dependencies: - dependency-name: slackapi/slack-github-action dependency-version: 2.1.1 dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <[email protected]>
|
The |
|
A single node development cluster (infra-pr-1606) was allocated in production infra for this PR. CI will attempt to deploy 🔌 You can connect to this cluster with: 🛠️ And pull infractl from the deployed dev infra-server with: 🚲 You can then use the dev infra instance e.g.: 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: LogsLogs for the development infra depending on your @redhat.com authuser: Or: |
Bumps slackapi/slack-github-action from 2.1.0 to 2.1.1.
Release notes
Sourced from slackapi/slack-github-action's releases.
Commits
91efab1Releaseb6f4640chore(release): tag version 2.1.1 (#474)d3dc61ebuild(deps-dev): bump@biomejs/biomefrom 1.9.4 to 2.0.6 (#470)f647c89build(deps-dev): bump@types/nodefrom 24.0.3 to 24.0.8 (#472)e6fa633build(deps-dev): bump sinon from 20.0.0 to 21.0.0 (#471)75b7822build(deps-dev): bump mocha-suppress-logs from 0.5.1 to 0.6.0 (#469)d7b6150build(deps-dev): bump mocha from 11.5.0 to 11.7.1 (#468)a7f5b68build: clone repository "docs" and configuration when syncing project docs (#...c69deabbuild(deps-dev): bump@types/nodefrom 22.15.29 to 24.0.3 (#466)1d0943cbuild(deps): bump axios from 1.9.0 to 1.10.0 (#465)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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill 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 versionwill 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 dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)