Update Tea 0.9.0 -> 0.10.1 #85
No reviewers
earl-warren
Labels
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
actions/forgejo-release!85
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "Mynacol/forgejo-release:only-tea-update"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This is generally a good idea.
But it also fixes my issues with this action. For comparison, here is a run with v2.7.2 and with this branch.
This is a split-off from #82 to have small PRs.
@earl-warren can you have a look at this? TIA
You are very patient 👍 Could you please update the description to describe what problem it fixes and how to reproduce it? I'm sure I could figure that out by looking at your workflows but that would take more time and, as you have observed, the attention span of reviewers is not great. Having a crystal clear description as well as bite-sized pull requests go a long way to get them merged.
I'm honestly not quite sure why the runs differ in that way. What I can say is that updating the Tea client fixed at least one problem, which has led to an invalid URL when downloading the latest release of a project.
As already said – this PR should really be merge-able without any specific bug report. It updates a dependency, which in turn updated its dependencies. Standard maintenance stuff.
bc22a9db8a72e579819dI have rebased this PR to differentiate the tests that previously had the same name. Let see if they both are happy about this upgrade.
A release was tagged.