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

Receive deprecated warnings at GH workflow step for version trilom/file-changes-action@v1.2.4 #141

Open
conapki opened this issue Nov 15, 2022 · 9 comments · May be fixed by #148
Open

Receive deprecated warnings at GH workflow step for version trilom/file-changes-action@v1.2.4 #141

conapki opened this issue Nov 15, 2022 · 9 comments · May be fixed by #148

Comments

@conapki
Copy link

conapki commented Nov 15, 2022

Describe the bug
Warning: The set-output command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

In our workflow we did fixed the 'set-output' command with help of https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

But still wherever we have used trilom/file-changes-action@v1.2.4 in our workflow steps we receive the above warnings.

Workflow
If applicable, provide a workflow file to help explain your problem.

Expected behavior
Is it something that new version of this repo will fix the warnings list that we get in GH action run ? Please help on same.

Additional context
Add any other context about the problem here.
image

@conapki
Copy link
Author

conapki commented Nov 18, 2022

Hi, Any updates to fix the set-output deprecated warnings?

@lmmentel
Copy link

It seems this repo got abandoned...

@honeyverma
Copy link

honeyverma commented Jan 12, 2023

Anybody knows if they are going to update it or do we need to use another plugin? if yes, can anybody recommend the new one?

@nsandary
Copy link

Yep, looks like we'll need a new one. Maybe someone responsible should fork this repo and maintain it.

@808sAndBR
Copy link

I have added a fix for this and opened a PR here: #148

Given that I opened a documentation PR a while back and it didn't get merged, I have also gone ahead and created a fork with a release of this fix:
https://github.com/808sAndBR/file-changes-action/releases/tag/v1.2.5

I don't plan to actively maintain or be especially "responsible" but it is working for my stack and anyone that wants to update to uses: 808sAndBR/file-changes-action@v1.2.5 is welcome to. If @trilom merges this change into main I will be pointing my actions back to their's but will leave my fork and it's release as is.

@808sAndBR
Copy link

Also I am really more of a pythonista that has dipped their toes into a few hours of JS/TS so if anyone has feedback on anything I should have done differently with this change, I am happy to update and stamp a new release.

@john-jerome
Copy link

this workflow is actively developed and doing pretty much the same thing:
https://github.com/tj-actions/changed-files

@santicarmo31
Copy link

Any update on this?

@jpmckinney
Copy link

I switched to https://github.com/tj-actions/changed-files - it works (even better).

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 a pull request may close this issue.

8 participants