New release asset upload 'Deprecation' message in log output
See original GitHub issueInfo
softprops/action-gh-release@v1
failed with a ‘Deprecation’ error.
See gist link for the error message:
https://gist.github.com/nialov/e151ed3511bc55de3dae2bacb91b0ddb
Background
My workflow additionally uses:
# Checkout repository
- name: Checkout
uses: actions/checkout@v2
- name: Set up python
uses: actions/setup-python@v2
with:
python-version: 3.8
- name: Install Poetry
uses: snok/install-poetry@v1.1.6
- name: Zip
uses: papeloto/action-zip@v1
Issue Analytics
- State:
- Created 2 years ago
- Comments:19 (6 by maintainers)
Top Results From Across the Web
How to Patch the Deprecated set-output in GitHub Workflows ...
This post explains how to patch container actions, including example Python functions, while maintaining backwards compatibility for non- ...
Read more >GHE Support · Issue #46 · anton-yurchenko/git-release - GitHub
So it is a bug and will be fixed, here's the response from github support we got this morning: Uploading release assets using...
Read more >Deprecations by version - GitLab Docs
Deprecations by version. In each release, GitLab announces features that are deprecated and no longer recommended for use. Each deprecated feature will be ......
Read more >Azure Media Services v3 release notes - Microsoft Learn
The latest releases; Known issues; Bug fixes; Deprecated functionality ... uploading .vtt or .ttml file format to an existing asset. New ...
Read more >Logging | Elasticsearch Guide [8.5] | Elastic
Elasticsearch also writes deprecation logs to the log directory. These logs record a message when you use deprecated Elasticsearch functionality. You can use ......
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Seem many people are talking about using this action for uploading duplicated files, and I forgot to say but this is my case, I’ve configured my workflow to upload a new set of assets with every new commit so users can test it, the assets are disposable so they aren’t versioned at all, and are always uploaded to the same tag/release. From what you said before:
@softprops
You should consider allow overwriting the assets.
I’m going to update the title of this issue. Releases don’t fail with just the gh api warnings