-
Notifications
You must be signed in to change notification settings - Fork 684
Update dependency ember-router-scroll to v3 #2699
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
Conversation
|
Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @smarnach (or someone else) soon. If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. Due to the way GitHub handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes. Please see the contribution instructions for more information. |
|
☔ The latest upstream changes (presumably #2697) made this pull request unmergeable. Please resolve the merge conflicts. |
37b1581 to
b915ece
Compare
|
☔ The latest upstream changes (presumably #2701) made this pull request unmergeable. Please resolve the merge conflicts. |
b915ece to
8926e64
Compare
|
☔ The latest upstream changes (presumably #2712) made this pull request unmergeable. Please resolve the merge conflicts. |
8926e64 to
26b9aac
Compare
|
☔ The latest upstream changes (presumably #2726) made this pull request unmergeable. Please resolve the merge conflicts. |
26b9aac to
d43e411
Compare
|
☔ The latest upstream changes (presumably #2738) made this pull request unmergeable. Please resolve the merge conflicts. |
d43e411 to
fe6cdca
Compare
|
☔ The latest upstream changes (presumably #2755) made this pull request unmergeable. Please resolve the merge conflicts. Note that reviewers usually do not review pull requests until merge conflicts are resolved! Once you resolve the conflicts, you should change the labels applied by bors to indicate that your PR is ready for review. Post this as a comment to change the labels: |
fe6cdca to
010f920
Compare
|
☔ The latest upstream changes (presumably #2691) made this pull request unmergeable. Please resolve the merge conflicts. Note that reviewers usually do not review pull requests until merge conflicts are resolved! Once you resolve the conflicts, you should change the labels applied by bors to indicate that your PR is ready for review. Post this as a comment to change the labels: |
010f920 to
c54e869
Compare
|
☔ The latest upstream changes (presumably #2713) made this pull request unmergeable. Please resolve the merge conflicts. Note that reviewers usually do not review pull requests until merge conflicts are resolved! Once you resolve the conflicts, you should change the labels applied by bors to indicate that your PR is ready for review. Post this as a comment to change the labels: |
c54e869 to
f95b960
Compare
|
☔ The latest upstream changes (presumably #2849) made this pull request unmergeable. Please resolve the merge conflicts. Note that reviewers usually do not review pull requests until merge conflicts are resolved! Once you resolve the conflicts, you should change the labels applied by bors to indicate that your PR is ready for review. Post this as a comment to change the labels: |
f95b960 to
400b163
Compare
|
☔ The latest upstream changes (presumably #2852) made this pull request unmergeable. Please resolve the merge conflicts. Note that reviewers usually do not review pull requests until merge conflicts are resolved! Once you resolve the conflicts, you should change the labels applied by bors to indicate that your PR is ready for review. Post this as a comment to change the labels: |
53190b5 to
7bb0c97
Compare
Switch from npm to yarn As discussed in the meeting on friday, yarn currently has better UX and allows us to use `resolutions` to work around transitive dependency version conflicts. This should unblock #2699, for example. r? `@jtgeibel`
|
☔ The latest upstream changes (presumably #2901) made this pull request unmergeable. Please resolve the merge conflicts. Note that reviewers usually do not review pull requests until merge conflicts are resolved! Once you resolve the conflicts, you should change the labels applied by bors to indicate that your PR is ready for review. Post this as a comment to change the labels: |
7bb0c97 to
a0ade62
Compare
|
☔ The latest upstream changes (presumably #2914) made this pull request unmergeable. Please resolve the merge conflicts. Note that reviewers usually do not review pull requests until merge conflicts are resolved! Once you resolve the conflicts, you should change the labels applied by bors to indicate that your PR is ready for review. Post this as a comment to change the labels: |
a0ade62 to
7c31691
Compare
... to resolve the conflict caused by the `ember-app-scheduler` dependency
7c31691 to
ccc6c81
Compare
|
@bors r+ |
|
📌 Commit ccc6c81 has been approved by |
|
☀️ Test successful - checks-travis |
This PR contains the following updates:
2.0.2->3.3.3Release Notes
dockyard/ember-router-scroll
v3.3.3Compare Source
v3.3.2Compare Source
v3.3.1Compare Source
v3.3.0Compare Source
v3.2.0Compare Source
v3.1.3Compare Source
v3.1.2Compare Source
v3.1.1Compare Source
v3.1.0Compare Source
v3.0.0Compare Source
Renovate configuration
📅 Schedule: At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻️ Rebasing: Renovate will not automatically rebase this PR, because other commits have been found.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by WhiteSource Renovate. View repository job log here.