Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fixing releases to also mark SIPs as released #1546

Merged
merged 1 commit into from
Oct 4, 2021

Conversation

jjgonecrypto
Copy link
Contributor

  • Fixes issue whereby a finalized release (in the release pipeline) does not actually mark the SIPs as released for the given layer
  • Also fixes bug whereby releasing with version -ovm was being incorrectly skipped.

@@ -26,12 +26,12 @@ const finalizeRelease = async ({ layer, release, versionTag }) => {
await versionsUpdate({ release, useOvm: true, versionTag });
}

const prerelease = semver.prerelease(versionTag) && semver.prerelease(versionTag) !== 'ovm';
const prerelease = semver.prerelease(versionTag) && semver.prerelease(versionTag)[0] !== 'ovm';
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this was the bug - semver.prerelease was returning an array

@codecov
Copy link

codecov bot commented Oct 4, 2021

Codecov Report

Merging #1546 (a556d2a) into staging (88a937a) will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff            @@
##           staging    #1546   +/-   ##
========================================
  Coverage    95.92%   95.92%           
========================================
  Files           75       75           
  Lines         1743     1743           
  Branches       547      547           
========================================
  Hits          1672     1672           
  Misses          71       71           

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 88a937a...a556d2a. Read the comment docs.

@@ -26,12 +26,12 @@ const finalizeRelease = async ({ layer, release, versionTag }) => {
await versionsUpdate({ release, useOvm: true, versionTag });
}

const prerelease = semver.prerelease(versionTag) && semver.prerelease(versionTag) !== 'ovm';
const prerelease = semver.prerelease(versionTag) && semver.prerelease(versionTag)[0] !== 'ovm';
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

are we certain that semver.prerelease(versionTag)[0] is not null? otherwise the functionality would not be exactly the same as before.

Copy link
Member

@barrasso barrasso left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, just have same concern that db raised about being certain the first element in the array is not null

@barrasso barrasso merged commit 5656628 into staging Oct 4, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants