-
Notifications
You must be signed in to change notification settings - Fork 0
ci: bump actions/github-script from 7 to 8 #19
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
base: main
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -48,7 +48,7 @@ jobs: | |
|
|
||
| - name: Create success comment | ||
| if: success() && github.event_name == 'release' | ||
| uses: actions/github-script@v7 | ||
| uses: actions/github-script@v8 | ||
| with: | ||
| script: | | ||
| github.rest.issues.createComment({ | ||
|
Comment on lines
49
to
54
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. P1 | Confidence: High This update to actions/github-script@v8 introduces a breaking change requiring GitHub Actions Runner v2.327.1 or higher; failure to update self-hosted runners will cause runtime failures. Additionally, the Node.js runtime is updated to 24.x, which may impact future script compatibility. |
||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
P2 | Confidence: High
The CI results show that the 'Test Coverage' job failed. While this failure may be unrelated to the version bump, a best practice for dependency updates, especially major versions, is to verify that all core CI pipelines pass. The success of the 'Build', 'Lint & Type Check', and 'Test (Fast)' jobs is positive, but the coverage failure should be investigated to ensure the update doesn't indirectly affect test execution or reporting environments. This is a speculative linkage, but the presence of a CI failure alongside a major version bump warrants a check.