Skip to content

Update actions/github-script to v5 #7151

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

Merged
merged 7 commits into from
Feb 8, 2022
Merged

Update actions/github-script to v5 #7151

merged 7 commits into from
Feb 8, 2022

Conversation

sobolevn
Copy link
Member

@sobolevn sobolevn commented Feb 7, 2022

No description provided.

@sobolevn sobolevn changed the title Update actions/github-script to `v5 Update actions/github-script to v5 Feb 7, 2022
@sobolevn
Copy link
Member Author

sobolevn commented Feb 7, 2022

Notice, that there's no mypy_primer comment on this issue!

@sobolevn
Copy link
Member Author

sobolevn commented Feb 7, 2022

I have changed a file in stubs/ just to test this.

@github-actions
Copy link
Contributor

github-actions bot commented Feb 7, 2022

According to mypy_primer, this change has no effect on the checked open source code. 🤖🎉

@Akuli
Copy link
Collaborator

Akuli commented Feb 7, 2022

github-script is used in several places, and this PR currently updates only one of them:

$ git grep github-script
.github/workflows/mypy_primer_comment.yml:        uses: actions/github-script@v3
.github/workflows/mypy_primer_comment.yml:        uses: actions/github-script@v3
.github/workflows/stubtest.yml:      - uses: actions/github-script@v3

Why should we update github-script anyway? The current @v3 works.

Copy link
Collaborator

@hauntsaninja hauntsaninja left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I mentioned this in the mypy PR, but Github Actions is not running the code in your pull request for mypy_primer comment. Pretty sure this PR breaks things: https://github.com/actions/github-script#breaking-changes-in-v5

The only way to test (other than iterating on master) is on your fork.

@srittau
Copy link
Collaborator

srittau commented Feb 8, 2022

I'd rather update things sooner than later, so working on this is appreciated. Not updating leads to bugs and security issues down the line that don't get fixed. And that often means it's more complicated to update (due to a larger amount of changes), while being under time pressure to do so.

@sobolevn
Copy link
Member Author

sobolevn commented Feb 8, 2022

Yes, @hauntsaninja, you are right. This action:

  • Was not running from my branch
  • Had breaking changes

After some local experiments, I've managed to make it work:

I've pushed all changed I applied to my version (I ruined my fork comletely 😆).
The only difference is .rest suffix for github http jobs. It is in line with the breaking changes described here.

@hauntsaninja hauntsaninja merged commit b0202f7 into python:master Feb 8, 2022
@hauntsaninja
Copy link
Collaborator

Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants