-
Notifications
You must be signed in to change notification settings - Fork 2
Bump actions/github-script from 7 to 8 #108
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bump actions/github-script from 7 to 8 #108
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>
|
This repository caches data generated from notebooks stored in other repositories in the To regenerate the cache for this PR, create a comment on this PR consisting only of the string: |
|
/regenerate-cache |
|
A workflow has been dispatched to regenerate the cookbook cache for this PR.
|
|
A workflow dispatched to regenerate the cookbook cache for this PR has just finished.
Changes will only be visible in the ReadTheDocs preview after it has been rebuilt. You will need to be logged in to ReadTheDocs to see the rebuild option. |
|
OK I think I've tested everything I reasonably can:
The following things work, but these are executed from
So there's nothing obviously broken. The only breaking change from 7-8 is upgrading from Node 20 to 24, which has numerous "SEMVER-MAJOR" changes - far too many to manually check. However, you're supposed to be able to update these things! I'm torn as to whether to just tell dependabot to ignore github-script, or to merge this PR. I'll ask for advice at tomorrow morning's check-in. |
|
IIUC these workflows don't publish directly if a run fails? So merging this as-is
Not updating this workflow seems undesirable and updating it seems safe and likely a non-event, so that's what I'd favor |
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.xf28e40cMerge pull request #610 from actions/nebuk89-patch-11ae9958Update README.mdDependabot 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)