You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The latest release (0.1.1) was created at (running gh release view --json publishedAt --repo ynput/ayon-syncsketch)
{
"publishedAt": "2024-10-07T14:35:57Z"
}
While the release workflow was triggered first at (running gh run list --workflow "🚀 Release Trigger" --limit 1 --json createdAt --jq '.[0].createdAt' --repo ynput/ayon-syncsketch)
2024-10-07T15:30:31Z
So about an hour later.
So from the details I was able to figure out here so far it seems like you created release 0.1.1 before you ran the Release Trigger workflow if I'm not mistaken.
I assume there were no other merged PRs since release 0.1.1- so I need to know, was was your intention here.
And just a side note: the release workflow only cares about merged PRs and not not about single commits since commits don't carry any required metadata for releases.
@jakubjezek001 let me know what you wanted to do so we can figure it out :D
Is there an existing issue for this?
Expected Behavior:
Check latest workflow run
Release workflow should pick up the changes and create a release.
Current Behavior:
Workflow reports:
No merged PRs found since last release.
in jobincrement version
Steps To Reproduce:
Are there any labels you wish to add?
Relevant log output:
No response
Additional context:
No response
The text was updated successfully, but these errors were encountered: