Skip to content

Conversation

@Yikun
Copy link
Owner

@Yikun Yikun commented Oct 21, 2022

What changes were proposed in this pull request?

Upgrade actions/github-scripts to v6

Why are the changes needed?

Node.js 12 actions are deprecated. For more information see: https://github.blog/changelog/2022-09-22-github-actions-all-actions-will-begin-running-on-node16-instead-of-node12/

Does this PR introduce any user-facing change?

No, dev only

How was this patch tested?

@Yikun
Copy link
Owner Author

Yikun commented Oct 22, 2022

Notify works well:
image

and update status set to failed as expeceted:
image

And See test results set right.
https://github.com/Yikun/spark/pull/181/checks?check_run_id=9029035780

HyukjinKwon pushed a commit to apache/spark that referenced this pull request Oct 22, 2022
…fy workflow

### What changes were proposed in this pull request?
Upgrade actions/github-scripts from v3 to v6 and fix notify workflow

### Why are the changes needed?
Node.js 12 actions are deprecated. For more information see: https://github.blog/changelog/2022-09-22-github-actions-all-actions-will-begin-running-on-node16-instead-of-node12/.

- Since github-script V5,  change from `github.*` to `github.rest.*`, but `request`, `paginate` are unchanged.
  see also https://github.com/actions/github-script#breaking-changes-in-v5
- Since github-script V6, upgrade node12 to node16

### Does this PR introduce _any_ user-facing change?
No, dev only

### How was this patch tested?
- Due to `pull_request_target`, the current PR is not in effect, we can only do test on local : set default branch to V6, and submit the PR Yikun#181

Notify works well:
<img width="850" alt="image" src="https://user-images.githubusercontent.com/1736354/197310102-6c709716-8a99-422d-8d38-3f770b6925f0.png">

Update status set to failed as expeceted:
<img width="898" alt="image" src="https://user-images.githubusercontent.com/1736354/197310119-30332769-0553-4ffa-816c-97a5ec0b3c27.png">

And `See test results` set right.
https://github.com/Yikun/spark/pull/181/checks?check_run_id=9029035780

Closes #38341 from Yikun/upgrade-actions.

Authored-by: Yikun Jiang <[email protected]>
Signed-off-by: Hyukjin Kwon <[email protected]>
SandishKumarHN pushed a commit to SandishKumarHN/spark that referenced this pull request Dec 12, 2022
…fy workflow

### What changes were proposed in this pull request?
Upgrade actions/github-scripts from v3 to v6 and fix notify workflow

### Why are the changes needed?
Node.js 12 actions are deprecated. For more information see: https://github.blog/changelog/2022-09-22-github-actions-all-actions-will-begin-running-on-node16-instead-of-node12/.

- Since github-script V5,  change from `github.*` to `github.rest.*`, but `request`, `paginate` are unchanged.
  see also https://github.com/actions/github-script#breaking-changes-in-v5
- Since github-script V6, upgrade node12 to node16

### Does this PR introduce _any_ user-facing change?
No, dev only

### How was this patch tested?
- Due to `pull_request_target`, the current PR is not in effect, we can only do test on local : set default branch to V6, and submit the PR Yikun#181

Notify works well:
<img width="850" alt="image" src="https://user-images.githubusercontent.com/1736354/197310102-6c709716-8a99-422d-8d38-3f770b6925f0.png">

Update status set to failed as expeceted:
<img width="898" alt="image" src="https://user-images.githubusercontent.com/1736354/197310119-30332769-0553-4ffa-816c-97a5ec0b3c27.png">

And `See test results` set right.
https://github.com/Yikun/spark/pull/181/checks?check_run_id=9029035780

Closes apache#38341 from Yikun/upgrade-actions.

Authored-by: Yikun Jiang <[email protected]>
Signed-off-by: Hyukjin Kwon <[email protected]>
@github-actions
Copy link

We're closing this PR because it hasn't been updated in a while. This isn't a judgement on the merit of the PR in any way. It's just a way of keeping the PR queue manageable.
If you'd like to revive this PR, please reopen it and ask a committer to remove the Stale tag!

@github-actions github-actions bot added the Stale label Jan 31, 2023
@github-actions github-actions bot closed this Feb 1, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants