Skip to content

build: handle prerelease versions in deletion target rule #10101

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

Merged
merged 1 commit into from
May 4, 2018

Conversation

crisbeto
Copy link
Member

@crisbeto crisbeto commented Feb 22, 2018

Currently the deletion target rule doesn't handle comparing something like 6.0.0-beta.2 and 6.0.0. With these changes both versions will be considered the same.

Note: lint failures are to be expected, because the rule now compares the beta version correctly. We may have to delay merging this in until we've done all the breaking changes.

Currently the deletion target rule doesn't handle comparing something like `6.0.0-beta.2` and `6.0.0`. With these changes both versions will be considered the same.
@googlebot googlebot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Feb 22, 2018
@jelbourn
Copy link
Member

Yeah, we should hold off on merging this until we remove the deprecated stuff.

@crisbeto
Copy link
Member Author

@jelbourn this one is unblocked now.

Copy link
Member

@jelbourn jelbourn left a comment

Choose a reason for hiding this comment

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

LGTM

@jelbourn jelbourn added pr: lgtm action: merge The PR is ready for merge by the caretaker and removed pr: needs review labels May 3, 2018
@ngbot
Copy link

ngbot bot commented May 3, 2018

I see that you just added the pr: merge ready label, but the following checks are still failing:
    failure status "continuous-integration/travis-ci/pr" is failing
    pending 1 pending code review

If you want your PR to be merged, it has to pass all the CI checks.

If you can't get the PR to a green state due to flakes or broken master, please try rebasing to master and/or restarting the CI job. If that fails and you believe that the issue is not due to your change, please contact the caretaker and ask for help.

@josephperrott josephperrott merged commit 01ec602 into angular:master May 4, 2018
@angular-automatic-lock-bot
Copy link

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 Sep 8, 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
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants