chore(ci)(deps): bump actions/github-script from 7 to 8#506
chore(ci)(deps): bump actions/github-script from 7 to 8#506dependabot[bot] wants to merge 1 commit intomainfrom
Conversation
Bumps [actions/github-script](https://github.com/actions/github-script) from 7 to 8. - [Release notes](https://github.com/actions/github-script/releases) - [Commits](actions/github-script@v7...v8) --- updated-dependencies: - dependency-name: actions/github-script dependency-version: '8' dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
LabelsThe following labels could not be found: Please fix the above issues or remove invalid values from |
GitHub Runner Execution ResultsPR: #506 - chore(ci)(deps): bump actions/github-script from 7 to 8 ❌ test-firecracker-runner.ymlExecution failed: VM allocation failed: Allocation failed with status: 500 Internal Server Error ❌ vm-execution-tests.ymlExecution failed: VM allocation failed: Allocation failed with status: 500 Internal Server Error ❌ ci-optimized.ymlExecution failed: VM allocation failed: Allocation failed with status: 500 Internal Server Error ❌ python-bindings.ymlExecution failed: VM allocation failed: Allocation failed with status: 500 Internal Server Error ❌ warden.ymlExecution failed: VM allocation failed: Allocation failed with status: 500 Internal Server Error ✅ Powered by terraphim-github-runner |
1 participant
Bumps actions/github-script from 7 to 8.
Release notes
Sourced from actions/github-script's releases.
... (truncated)
Commits
ed59741Merge pull request #653 from actions/sneha-krip/readme-for-v82dc352eBold minimum Actions Runner version in README01e118cUpdate README for Node 24 runtime requirements8b222acApply suggestion from@salmanmkcadc0eeaREADME for updating actions/github-script from v7 to v820fe497Merge pull request #637 from actions/node24e7b7f22update licenses2c81ba0Update Node.js version support to 24.xDependabot 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)