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

Remove Summary Warnings #4

Closed
dcamachoj opened this issue Oct 24, 2022 · 4 comments · Fixed by #5
Closed

Remove Summary Warnings #4

dcamachoj opened this issue Oct 24, 2022 · 4 comments · Fixed by #5

Comments

@dcamachoj
Copy link

When executing this action, there are a couple of warnings that appear in the Workflow Summary:

The solutions are described in the provided links.
Thanks

@ApexModder
Copy link

Also running into these warnings when using this action

ApexModder added a commit to ApexStudios-Dev/Commonality that referenced this issue Oct 29, 2022
@hannesa2
Copy link

I see this as well

image

@jimschubert
Copy link
Owner

Reopening because the PR closed this automatically. The first issue should be fixed by #5.

I'll looking at the set-output issue and will close this when completed.

@jimschubert jimschubert reopened this Jan 16, 2023
@jimschubert
Copy link
Owner

These issues should now be resolved.

I moved v2 to point to the new v2.1 release. I was having trouble getting GitHub releases to show the updated commit hash. GitHub's actions runner pulled the correct hash for v2, but I briefly deleted and recreated the release so everything displayed correctly in both GitHub and the actions marketplace.

Tested each version in https://github.com/jimschubert/ossify

image

I still need to update that project's docker/setup-buildx-action@v1, docker/login-action@v1 but all warnings are resolved for this action (see also screenshots in #5).

Shows v2 displaying the new output logging:
image

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.

4 participants