Skip to content

docs(changelog): fix version 6.1.5 typo#25760

Closed
livthomas wants to merge 1 commit intoangular:masterfrom
livthomas:patch-2
Closed

docs(changelog): fix version 6.1.5 typo#25760
livthomas wants to merge 1 commit intoangular:masterfrom
livthomas:patch-2

Conversation

@livthomas
Copy link
Copy Markdown
Contributor

PR Checklist

Please check if your PR fulfills the following requirements:

PR Type

What kind of change does this PR introduce?

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[x] Documentation content changes
[ ] angular.io application / infrastructure changes
[ ] Other... Please describe:

What is the current behavior?

Issue Number: N/A

What is the new behavior?

Does this PR introduce a breaking change?

[ ] Yes
[x] No

Other information

Just fixing typo in changelog.

@brandonroberts
Copy link
Copy Markdown
Contributor

Thanks for the PR @livthomas ! This is duplicate of #25739. We'll leave it open for now just in case no progress is made on the other.

@brandonroberts brandonroberts self-assigned this Aug 31, 2018
@brandonroberts brandonroberts added comp: docs target: patch This PR is targeted for the next patch release state: community Someone from the Angular community is working on this issue or submitted this PR labels Aug 31, 2018
@IgorMinar IgorMinar removed the request for review from mhevery September 4, 2018 23:56
@IgorMinar IgorMinar added the action: merge The PR is ready for merge by the caretaker label Sep 4, 2018
@ngbot
Copy link
Copy Markdown

ngbot bot commented Sep 4, 2018

I see that you just added the PR action: merge label, but the following checks are still failing:
    failure status "ci/circleci: test" is failing
    pending status "code-review/pullapprove" is pending

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.

@IgorMinar IgorMinar added the merge: caretaker note Alert the caretaker performing the merge to check the PR for an out of normal action needed or note label Sep 4, 2018
@IgorMinar
Copy link
Copy Markdown
Contributor

caretaker note: the ci results are flaky.

@mhevery mhevery closed this in 2c66523 Sep 5, 2018
mhevery pushed a commit that referenced this pull request Sep 5, 2018
@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 Sep 14, 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 merge: caretaker note Alert the caretaker performing the merge to check the PR for an out of normal action needed or note state: community Someone from the Angular community is working on this issue or submitted this PR target: patch This PR is targeted for the next patch release

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants