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
When the update pipeline job runs, it sets the .github/pipeline-version file to the version of pipeline-builder that was used. It incorrectly selects the version for v2.
Current Behavior
It uses gh api to fetch the latest release, and uses the version number of the latest release. This is not accurate because what is the latest release is not tied to the code that has been checked out and is running.
Possible Solution
Look at the checked out branch and determine the version that way, like compute-version.sh.
Expected Behavior
When the update pipeline job runs, it sets the
.github/pipeline-version
file to the version of pipeline-builder that was used. It incorrectly selects the version for v2.Current Behavior
It uses
gh api
to fetch the latest release, and uses the version number of the latest release. This is not accurate because what is the latest release is not tied to the code that has been checked out and is running.Possible Solution
Look at the checked out branch and determine the version that way, like
compute-version.sh
.Steps to Reproduce
paketo-buildpacks/pipeline-builder-stool-pigeon#4
Motivations
It should display accurate version information.
The text was updated successfully, but these errors were encountered: