User Role Editor Pro version 4.18.2 was published at April 30th, 2015.
The list of changes:

• Calls to the functions add_query_arg(), remove_query_arg() are escaped with esc_url_raw() to exclude potential XSS vulnerabilities, as suggested at
  https://developer.wordpress.org/reference/functions/add_query_arg/

User Role Editor Pro version 4.18.1 was published at February 24th, 2015.
The list of changes:

• Fixed PHP fatal error for “Reset” roles operation.
• Fixed current user capability checking before URE Options page open. Multisite: URE’s options page is prohibited by ‘manage_network_users’ capability instead of ‘ure_manage_options’ in case single site administrators does not have permission to use URE.
• 3 missed phrases were added to the translations files.

Did you meet problems with plugin User Role Editor installation package download or automatic update recent 3 days?
You did not? Fortune loves you :).

If to be serious, there are some problems really. Bad news – they are related to the technical issue introduced by role-editor.com hosting platform – Google Application Engine (GAE). Good news – GAE team works on it. I hope they will fix it quickly. While they search a decision, I applied recommended workaround to the site code. Let’s see, if this will help us to overcome this trouble.

For more information about Google Cloud Storage file access bug introduced at GAE read this post.

User Role Editor Pro 4.18 WordPress plugin was published 11.02.2014. This version changes include:

• Own custom user capabilities, e.g. ‘ure_edit_roles’ are used to restrict access to User Role Editor functionality. More information…
• Posts/pages edit access restriction add-on functionality was extended to the Media Library. Posts/pages attachments becomes unavailable automatically if correspondent post/page edit is prohibited.
• Posts/pages edit access restriction add-on works with custom post types now.
• Posts/pages view access restriction works with custom post types now.
• Admin menu items with empty user capability are available in “Admin menu access” add-on now. “Participants Database” plugin defines its menu this way.
• Some plugins use meta capabilities instead of real user capabilities, like ‘jetpack_admin_page’ in “JetPack” or ‘wpcf7_read_contact_forms’ in “Contact Form 7”.
• “Admin menu access” add-on recognizes such meta capabilities now. These meta-caps are replaced at “Admin menu” window with correspondent (mapped) real user capabilities for your further reference.
• Admin menu access add-on updated: ‘Howdy, …’ menu including ‘Logout’ menu item at top bar admin menu will not disappear after blocking ‘Profile’ menu.
• Top bar menu ‘SEO’ from “WP SEO from Yoast” plugin is blocked if user has no ‘manage_options’ capability or correspondent admin menu is blocked.
• Admin menu blocking is available for ‘administrator’ role under multisite. You should be superadmin. Do not give administrator access to URE in this case.
• More universal checking applied to the custom post type capabilities creation to exclude not existing property notices.
• New option “Edit user capabilities” was added. If it is unchecked – capabilities section of selected user will be shown in the readonly mode. Administrator (except superadmin for multisite) can not assign capabilities to the user directly. He should make it using roles only.
• Fixed JavaScript bug with ‘Reset Roles’ for FireFox v.34.