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 property release_status is useful in combination when using latestBuild for version, but when using a specific build, it's actually a bit of a hindrance. Technically, it could prevent you from accidentally using a draft or prerelease version of a dependency. But when you're already specifying an explicit version string, I think the developer is aware of the type of release they are using.
To keep legacy workflows intact, I propose that the property release_status should also allow the value any, which doesn't filter available releases of a repository by status. If this seems too dangerous when used with latestBuild, it could be only allowed if an explicit version string is given.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
The property
release_status
is useful in combination when usinglatestBuild
forversion
, but when using a specific build, it's actually a bit of a hindrance. Technically, it could prevent you from accidentally using a draft or prerelease version of a dependency. But when you're already specifying an explicit version string, I think the developer is aware of the type of release they are using.To keep legacy workflows intact, I propose that the property
release_status
should also allow the valueany
, which doesn't filter available releases of a repository by status. If this seems too dangerous when used withlatestBuild
, it could be only allowed if an explicit version string is given.Beta Was this translation helpful? Give feedback.
All reactions