Skip to content

build: do generate invalid semver versions for snapshot builds#17267

Merged
mmalerba merged 1 commit intoangular:masterfrom
devversion:build/fix-invalid-semver-versions-for-snapshot-builds
Oct 2, 2019
Merged

build: do generate invalid semver versions for snapshot builds#17267
mmalerba merged 1 commit intoangular:masterfrom
devversion:build/fix-invalid-semver-versions-for-snapshot-builds

Conversation

@devversion
Copy link
Copy Markdown
Member

@devversion devversion commented Oct 2, 2019

Apparently there is a long-standing issue in the snapshot builds
where we generate invalid versions if the snapshot SHA starts with
zero's. In order to fix this, we need to ensure that the commit SHA is
part of a version segment that starts with text (i.e. -sha-{val}).

This happens rarely, but it should be a good idea to fix this.

Note: I guess this should also go into the patch branch for the 8.2.x docs-content.

Fixes #17264

Apparently there is a long-standing issue in the snapshot builds
where we generate invalid versions if the snapshot SHA starts with
zero's. In order to fix this, we need to ensure that the commit SHA is
part of a version segment that starts with text (i.e. `-sha-{val}`).

Fixes angular#17264
@devversion devversion added pr: merge safe target: patch This PR is targeted for the next patch release labels Oct 2, 2019
@devversion devversion requested a review from a team October 2, 2019 08:11
@googlebot googlebot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Oct 2, 2019
@devversion devversion added this to the 9.0.0 milestone Oct 2, 2019
@mmalerba mmalerba added pr: lgtm action: merge The PR is ready for merge by the caretaker labels Oct 2, 2019
@mmalerba mmalerba merged commit 94cec9f into angular:master Oct 2, 2019
@@ -42,7 +42,12 @@ commitAuthorEmail=$(git --no-pager show -s --format='%ae' HEAD)
commitMessage=$(git log --oneline -n 1)
commitTag="${buildVersion}-${commitSha}"
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

We should consider removing this line as it isn't used anymore.

mmalerba pushed a commit that referenced this pull request Oct 8, 2019
Apparently there is a long-standing issue in the snapshot builds
where we generate invalid versions if the snapshot SHA starts with
zero's. In order to fix this, we need to ensure that the commit SHA is
part of a version segment that starts with text (i.e. `-sha-{val}`).

Fixes #17264

(cherry picked from commit 94cec9f)
@angular-automatic-lock-bot
Copy link
Copy Markdown

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Nov 2, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

action: merge The PR is ready for merge by the caretaker cla: yes PR author has agreed to Google's Contributor License Agreement target: patch This PR is targeted for the next patch release

Projects

None yet

Development

Successfully merging this pull request may close these issues.

build(release): generates invalid semver versions and breaks material.angular.io builds

6 participants