Skip to content
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

Promote v5 of peter-evans/create-pull-request to GitHub Actions #66384

Closed
AMurkin opened this issue Jun 22, 2023 · 1 comment
Closed

Promote v5 of peter-evans/create-pull-request to GitHub Actions #66384

AMurkin opened this issue Jun 22, 2023 · 1 comment
Labels
Code: Build Issues regarding different builds and build environments stale Closed for lack of activity, but still valid. <Suggestion / Discussion> Talk it out before implementing

Comments

@AMurkin
Copy link
Contributor

AMurkin commented Jun 22, 2023

Is your feature request related to a problem? Please describe.

Pull Tileset Updates, Pull translations from Transifex, Weekly changelog update and TOC Generator actions use v4 of peter-evans/create-pull-request GitHub Action repo.
They produce the following output:

Run peter-evans/create-pull-request@v4
(node:1827) [DEP0005] DeprecationWarning: Buffer() is deprecated due to security and usability issues. Please use the Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() methods instead.
(Use `node --trace-deprecation ...` to show where the warning was created)

Solution you would like.

This was fixed in v5 of peter-evans/create-pull-request.
Latest version is v5.0.2. Example of action used v5.0.2: GitHub Desktop.
It should be strait forward change of version in action configs, AFAICT. Updating from v4 to v5.

Describe alternatives you have considered.

No response

Additional context

No response

@AMurkin AMurkin added the <Suggestion / Discussion> Talk it out before implementing label Jun 22, 2023
@Maleclypse Maleclypse added the Code: Build Issues regarding different builds and build environments label Jun 24, 2023
@github-actions
Copy link
Contributor

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. Please do not bump or comment on this issue unless you are actively working on it. Stale issues, and stale issues that are closed are still considered.

@github-actions github-actions bot added the stale Closed for lack of activity, but still valid. label Jul 24, 2023
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Aug 23, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Code: Build Issues regarding different builds and build environments stale Closed for lack of activity, but still valid. <Suggestion / Discussion> Talk it out before implementing
Projects
None yet
Development

No branches or pull requests

2 participants