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

updated electron #286

Closed
wants to merge 6 commits into from
Closed

updated electron #286

wants to merge 6 commits into from

Conversation

oluoluoxenfree
Copy link
Contributor

@oluoluoxenfree oluoluoxenfree commented Jan 7, 2019

Summary

Updated electron to 4.0.1

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)

Issue

#274

@oluoluoxenfree
Copy link
Contributor Author

I had an error locally which was the (ongoing?) --help indentation thing, but my errors on CI are completely different; anyone have any idea why that would be?

@ChrisBAshton
Copy link
Contributor

Might want to update to 2.0.8 as per #274, rather than 4.0.1 which is two major versions ahead (so likely to have breaking API changes).

HISTORY.md Outdated Show resolved Hide resolved
Copy link
Contributor

@ChrisBAshton ChrisBAshton left a comment

Choose a reason for hiding this comment

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

Nice! I'll try and get it merged this week, unless another a11y maintainer can get there first :)

@andymsuk
Copy link
Contributor

Version bumping is done as part of the release process as it needs to be done elsewhere too, so can you remove the version change in package.json and remove change in HISTORY?

@EmmaJP
Copy link
Contributor

EmmaJP commented Jan 31, 2019

Version bumping is done as part of the release process as it needs to be done elsewhere too, so can you remove the version change in package.json and remove change in HISTORY?

Did the bbc-a11y version change get removed yet from this PR? Asking because I'm still seeing it in the 'Files changed'.

@oluoluoxenfree
Copy link
Contributor Author

oluoluoxenfree commented Jan 31, 2019 via email

@oluoluoxenfree
Copy link
Contributor Author

Is there anything else I need to do for this? @ChrisBAshton @andymsuk @EmmaJP

@andymsuk
Copy link
Contributor

The update to the HISTORY file should be removed as it's done as part of the release process.

other than that, it's ready to merge and release - just need to find time to do it. Maybe @ChrisBAshton is more free than me?

@ChrisBAshton
Copy link
Contributor

I'm not, unfortunately!

@andymsuk
Copy link
Contributor

Hi @oluoluoxenfree
Apologies, I'd forgotten about this PR and now there's conflicts.
If you can resolve the conflicts, I can look to get this merged.

@andymsuk andymsuk added the awaiting-reply-from-creator Awaiting a reply from the person who created the issue or PR label Apr 30, 2019
@oluoluoxenfree
Copy link
Contributor Author

I think I might close this one and start a new PR with the updated master branch; there are a lot of changes in the package,.json

@github-actions
Copy link

This pull request has already been merged/closed. If you experience issues related to these changes, please open a new issue referencing this pull request.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Aug 11, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
awaiting-reply-from-creator Awaiting a reply from the person who created the issue or PR
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants