From b88030871bb64ae030f936e224e0919735d30edf Mon Sep 17 00:00:00 2001 From: Franck Nijhof Date: Fri, 24 Jan 2020 18:09:46 +0100 Subject: [PATCH 01/13] Remove deprecation warnings from 0.42 (#11861) --- source/_docs/automation/trigger.markdown | 6 -- source/_docs/configuration/events.markdown | 69 +++++++++------------- 2 files changed, 28 insertions(+), 47 deletions(-) diff --git a/source/_docs/automation/trigger.markdown b/source/_docs/automation/trigger.markdown index 448da488c73c..329ad28ea601 100644 --- a/source/_docs/automation/trigger.markdown +++ b/source/_docs/automation/trigger.markdown @@ -22,12 +22,6 @@ automation: mood: happy ``` -
- -Starting 0.42, it is no longer possible to listen for event `homeassistant_start`. Use the 'homeassistant' platform below instead. - -
- ### Home Assistant trigger Triggers when Home Assistant starts up or shuts down. diff --git a/source/_docs/configuration/events.markdown b/source/_docs/configuration/events.markdown index 4d5de172b7f7..14ce423dab96 100644 --- a/source/_docs/configuration/events.markdown +++ b/source/_docs/configuration/events.markdown @@ -8,62 +8,49 @@ The core of Home Assistant is the event bus. The event bus allows any integratio Home Assistant contains a few built-in events that are used to coordinate between various components. -### Event `homeassistant_start` -Event `homeassistant_start` is fired when all integrations from the configuration have been initialized. This is the event that will start the timer firing off `time_changed` events. - -
- - Starting 0.42, it is no longer possible to listen for event `homeassistant_start`. Use the 'homeassistant' [platform](/docs/automation/trigger) instead. - -
- -### Event `homeassistant_stop` -Event `homeassistant_stop` is fired when Home Assistant is shutting down. It should be used to close any open connection or release any resources. - - ### Event `state_changed` Event `state_changed` is fired when a state changes. Both `old_state` and `new_state` are state objects. [Documentation about state objects.](/topics/state_object/) -Field | Description ------ | ----------- -`entity_id` | Entity ID of the changed entity. Example: `light.kitchen` -`old_state` | The previous state of the entity before it changed. This field is omitted if the entity is new. -`new_state` | The new state of the entity. This field is omitted if the entity is removed from the state machine. +| Field | Description | +| ----------- | --------------------------------------------------------------------------------------------------- | +| `entity_id` | Entity ID of the changed entity. Example: `light.kitchen` | +| `old_state` | The previous state of the entity before it changed. This field is omitted if the entity is new. | +| `new_state` | The new state of the entity. This field is omitted if the entity is removed from the state machine. | ### Event `time_changed` Event `time_changed` is fired every second by the timer and contains the current time. -Field | Description ------ | ----------- -`now` | A [datetime object](https://docs.python.org/3.4/library/datetime.html#datetime.datetime) containing the current time in UTC. +| Field | Description | +| ----- | ---------------------------------------------------------------------------------------------------------------------------- | +| `now` | A [datetime object](https://docs.python.org/3.4/library/datetime.html#datetime.datetime) containing the current time in UTC. | ### Event `service_registered` Event `service_registered` is fired when a new service has been registered within Home Assistant. -Field | Description ------ | ----------- -`domain` | Domain of the service. Example: `light`. -`service` | The service to call. Example: `turn_on` +| Field | Description | +| --------- | ---------------------------------------- | +| `domain` | Domain of the service. Example: `light`. | +| `service` | The service to call. Example: `turn_on` | ### Event `call_service` Event `call_service` is fired to call a service. -Field | Description ------ | ----------- -`domain` | Domain of the service. Example: `light`. -`service` | The service to call. Example: `turn_on` -`service_data` | Dictionary with the service call parameters. Example: `{ 'brightness': 120 }`. -`service_call_id` | String with a unique call id. Example: `23123-4`. +| Field | Description | +| ----------------- | ------------------------------------------------------------------------------ | +| `domain` | Domain of the service. Example: `light`. | +| `service` | The service to call. Example: `turn_on` | +| `service_data` | Dictionary with the service call parameters. Example: `{ 'brightness': 120 }`. | +| `service_call_id` | String with a unique call id. Example: `23123-4`. | ### Event `service_executed` Event `service_executed` is fired by the service handler to indicate the service is done. -Field | Description ------ | ----------- -`service_call_id` | String with the unique call id of the service call that was executed. Example: `23123-4`. +| Field | Description | +| ----------------- | ----------------------------------------------------------------------------------------- | +| `service_call_id` | String with the unique call id of the service call that was executed. Example: `23123-4`. |
@@ -75,15 +62,15 @@ Field | Description Event `platform_discovered` is fired when a new platform has been discovered by the [`discovery`](/integrations/discovery/) component. -Field | Description ------ | ----------- -`service` | The platform that is discovered. Example: `zwave`. -`discovered` | Dictionary containing discovery information. Example: `{ "host": "192.168.1.10", "port": 8889}`. +| Field | Description | +| ------------ | ------------------------------------------------------------------------------------------------ | +| `service` | The platform that is discovered. Example: `zwave`. | +| `discovered` | Dictionary containing discovery information. Example: `{ "host": "192.168.1.10", "port": 8889}`. | ### Event `component_loaded` Event `component_loaded` is fired when a new integration has been loaded and initialized. -Field | Description ------ | ----------- -`component` | Domain of the integration that has just been initialized. Example: `light`. +| Field | Description | +| ----------- | --------------------------------------------------------------------------- | +| `component` | Domain of the integration that has just been initialized. Example: `light`. | From 752f1a46d166c393720c54c3dbbd7d806e9a5237 Mon Sep 17 00:00:00 2001 From: Gert Date: Sat, 25 Jan 2020 12:53:02 +0000 Subject: [PATCH 02/13] Document Recorder event_type exclude option (#11865) * Document event_type exclude option * Update source/_integrations/recorder.markdown Co-Authored-By: Franck Nijhof Co-authored-by: Franck Nijhof --- source/_integrations/recorder.markdown | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/source/_integrations/recorder.markdown b/source/_integrations/recorder.markdown index 7002f58b2789..793883fc4c65 100644 --- a/source/_integrations/recorder.markdown +++ b/source/_integrations/recorder.markdown @@ -54,6 +54,10 @@ recorder: description: The list of entity ids to be excluded from recordings. required: false type: list + event_types: + description: The list of event types to be excluded from recordings. + required: false + type: list include: description: Configure which integrations should be included in recordings. If set, all other entities will not be recorded. required: false @@ -85,6 +89,8 @@ recorder: - sun.sun # Don't record sun data - sensor.last_boot # Comes from 'systemmonitor' sensor platform - sensor.date + event_types: + - call_service # Don't record service calls ``` define domains and entities to record by using the `include` configuration (aka. whitelist) is convenient if you have a lot of entities in your system and your `exclude` lists possibly get very large, so it might be better just to define the entities or domains to record. From c05458e9278aa46487b4dfcb5772936b2a6103d2 Mon Sep 17 00:00:00 2001 From: Aleks Date: Sat, 25 Jan 2020 13:54:21 +0100 Subject: [PATCH 03/13] Update netgear.markdown (#11866) --- source/_integrations/netgear.markdown | 1 + 1 file changed, 1 insertion(+) diff --git a/source/_integrations/netgear.markdown b/source/_integrations/netgear.markdown index 5638dc9c27e2..62e9d62b4698 100644 --- a/source/_integrations/netgear.markdown +++ b/source/_integrations/netgear.markdown @@ -69,5 +69,6 @@ The use of `devices` or `exclude` is recommended when using `accesspoints` to av List of models that are known to use port 80: - Nighthawk X4S - AC2600 (R7800) - Orbi +- XR500 See the [device tracker integration page](/integrations/device_tracker/) for instructions how to configure the people to be tracked. From ff54ae67a0bd926b57bea8e18e470fdb567108b2 Mon Sep 17 00:00:00 2001 From: Jay Date: Sat, 25 Jan 2020 06:55:25 -0600 Subject: [PATCH 04/13] Slight addition to step 8 (#11862) * Slight addition to step 8 Some new users have expressed confusion about not being able to access the frontend at `http://hassio.local:8123` when the IP address works. Adding this note should hopefully reduce questions of this type. * Update index.markdown --- source/getting-started/index.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/getting-started/index.markdown b/source/getting-started/index.markdown index f908d0b56982..107182cbdd44 100644 --- a/source/getting-started/index.markdown +++ b/source/getting-started/index.markdown @@ -62,7 +62,7 @@ We will need a few things to get started with installing Home Assistant. The Ras 5. Insert the SD card into your Raspberry Pi. If you are going to use an Ethernet cable, connect that too. 6. Connect your power supply to the Raspberry Pi. 7. The Raspberry Pi will now boot up, connect to the Internet and download the latest version of Home Assistant. This will take about 20 minutes. -8. Home Assistant will be available at `http://hassio.local:8123`. If you are running an older Windows version or have a stricter network configuration, you might need to access Home Assistant at `http://hassio:8123`. +8. Home Assistant will be available at `http://hassio.local:8123`. If you are running an older Windows version or have a stricter network configuration, you might need to access Home Assistant at `http://hassio:8123` or `http://X.X.X.X:8123` (replace `X.X.X.X` with your Pi's IP address). 9. If you used a USB stick for configuring the network, you can now remove it. [the examples]: https://github.com/home-assistant/hassos/blob/dev/Documentation/network.md From 87d2e493a95df7693ac1db8f3106479a491a4e67 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Fran=C3=A7ois=20LASSERRE?= Date: Sat, 25 Jan 2020 14:02:09 +0100 Subject: [PATCH 05/13] Update xiaomi_aqara.markdown (#11860) Add a line for one gateway don't use mac address because it's doesn't works. --- source/_integrations/xiaomi_aqara.markdown | 2 ++ 1 file changed, 2 insertions(+) diff --git a/source/_integrations/xiaomi_aqara.markdown b/source/_integrations/xiaomi_aqara.markdown index 6a962e321ffe..f5928ddfe6e0 100644 --- a/source/_integrations/xiaomi_aqara.markdown +++ b/source/_integrations/xiaomi_aqara.markdown @@ -68,6 +68,8 @@ xiaomi_aqara: - key: xxxxxxxxxxxxxxxx ``` +For one gateway to avoid errors, don't provide the MAC address. + ### Multiple Gateways ```yaml From ab15c5a73144227916866c750744319acba566ce Mon Sep 17 00:00:00 2001 From: Scott Walsh Date: Sat, 25 Jan 2020 09:02:45 -0400 Subject: [PATCH 06/13] Adding clarity on plugs. (#11859) Adding clarity to how plugs should be added when doing manual discovery. --- source/_integrations/tplink.markdown | 2 ++ 1 file changed, 2 insertions(+) diff --git a/source/_integrations/tplink.markdown b/source/_integrations/tplink.markdown index 10ff20ae4a0d..073d61d567bf 100644 --- a/source/_integrations/tplink.markdown +++ b/source/_integrations/tplink.markdown @@ -30,6 +30,8 @@ The following devices are known to work with this component. ### Plugs +Plugs are type `switch` when autodiscovery has been disabled. + - HS100 - HS103 - HS105 From 3081aacda5c17669936b5f353cf73337ca1897a6 Mon Sep 17 00:00:00 2001 From: starkillerOG Date: Sat, 25 Jan 2020 14:07:09 +0100 Subject: [PATCH 07/13] Easier way to retrieve Access Token by uptodate app (#11852) * Easier way to retrieve Access Token by uptodate app IMPORTANTANT: I actually do not have a "Xiaomi Mi Robot Vacuum", I have a "Xiaomi Aqara Gateway", therefore this method schould be checked by someone owning a robot vacuum!!! I actualy am setting up the xiaomi_gateway_alarm through this custom component: https://github.com/hekm77/homeassistant-config/tree/master/custom_components/xiaomi_gateway_alarm For that component I need the same 32 character "token" as this component uses and the docs of xiaomi_gateway_alarm refered to these instructions. I found these current instructions to difficult/to much work, so I tryed to do it simpler and for me it worked. I just tryed the develepor mode of the gateway and even in the latest app 5.6.46 (january 2020) the token is just there in plain text. I use: gateway model: lumi.gateway.v3 gateway firmware_version: 1.4.1_175 gateway hardware_version: MW300 Android app (Samsung Galaxy S8) version: 5.6.46 steps to get there are in this PR. Can someone ferify this works for the robot vacuum??? * :pencil2: Tweaks Co-authored-by: Franck Nijhof --- source/_integrations/vacuum.xiaomi_miio.markdown | 14 ++++++++++++++ 1 file changed, 14 insertions(+) diff --git a/source/_integrations/vacuum.xiaomi_miio.markdown b/source/_integrations/vacuum.xiaomi_miio.markdown index cb87f950b2d3..0a0c47b0f56e 100644 --- a/source/_integrations/vacuum.xiaomi_miio.markdown +++ b/source/_integrations/vacuum.xiaomi_miio.markdown @@ -215,6 +215,20 @@ The following table shows the units of measurement for each attribute: ## Retrieving the Access Token +### Xiaomi Home app (Xiaomi Aqara Gateway, android?) + +1. Install the Xiaomi Home app. +2. Sign In/make an account. +3. Make sure you set your region to: Mainland China (Seems to be the longest line with Chines characters) under settings -> Region (language can later be set on English). +4. Select your Gateway in Xiaomi Home app. +5. Then the 3 dots at the top right of the screen. +6. Then click on about. +7. Tap the version number (Plug-in version 2.77.1 as of January 2020) at the bottom of the screen repeatedly. +8. You should now see 2 extra options listed in English, this means you enabled developer mode. [if not, try all steps again!]. +9. Under "Hub info" there is quite some text in JSON format, this includes the "token" that you need. + +### Alternative methods +
If using an Android device to retrieve the Access Token only `v5.4.49` of Mi Home is confirmed working (December 2019). Use `v5.4.49` of Mi Home locate a text file under the `Smarthome/logs` folder where the 32 character token is stored. There will likely be several text files in this directory, search all of them for the word 'token' and you should find it there. Be advised that the latest version of Mi Home does not store the token in clear text. From e20231575d72752ac68b4fd924f4055db683900c Mon Sep 17 00:00:00 2001 From: OscarHanzely <39314151+OscarHanzely@users.noreply.github.com> Date: Sat, 25 Jan 2020 13:04:29 -0700 Subject: [PATCH 08/13] Added purpose of database (#11871) --- source/_docs/backend/database.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_docs/backend/database.markdown b/source/_docs/backend/database.markdown index 6eb9b5df2078..e71bc6babf16 100644 --- a/source/_docs/backend/database.markdown +++ b/source/_docs/backend/database.markdown @@ -4,7 +4,7 @@ description: "Details about the database used by Home Assistant." redirect_from: /details/database/ --- -The default database used by Home Assistant is [SQLite](https://www.sqlite.org/), and the database file is stored in your [configuration directory](/getting-started/configuration/) (e.g., `/.homeassistant/home-assistant_v2.db`). If you prefer to run a database server (e.g. PostgreSQL), use the [`recorder` component](/integrations/recorder/). +Database is used in by Home Assistant as history and tracker only, to store the events and its parameters. The default database used by Home Assistant is [SQLite](https://www.sqlite.org/), and the database file is stored in your [configuration directory](/getting-started/configuration/) (e.g., `/.homeassistant/home-assistant_v2.db`). If you prefer to run a database server (e.g. PostgreSQL), use the [`recorder` component](/integrations/recorder/). To work with the SQLite database manually from the command-line, you will need an [installation](http://www.sqlitetutorial.net/download-install-sqlite/) of `sqlite3`. Alternatively [DB Browser for SQLite](http://sqlitebrowser.org/) provides a viewer for exploring the database data and an editor for executing SQL commands. First load your database with `sqlite3`: From 2cc03ae6f4cd2dc9a09b3fd8e3b27fb714c2c11a Mon Sep 17 00:00:00 2001 From: Brenda Wallace Date: Mon, 27 Jan 2020 09:46:09 +1300 Subject: [PATCH 09/13] Corrected a yaml snippet that was labelled as json. (#11872) --- source/_integrations/python_script.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_integrations/python_script.markdown b/source/_integrations/python_script.markdown index 7f312483f386..a6b80ec01bad 100644 --- a/source/_integrations/python_script.markdown +++ b/source/_integrations/python_script.markdown @@ -56,7 +56,7 @@ if entity_id is not None: service_data = {"entity_id": entity_id, "rgb_color": rgb_color, "brightness": 255} hass.services.call("light", "turn_on", service_data, False) ``` -The above `python_script` can be called using the following JSON as an input. +The above `python_script` can be called using the following YAML as an input. ```yaml entity_id: light.bedroom From 55cd92517e51c4504dbede78e4638eedbff46b76 Mon Sep 17 00:00:00 2001 From: Tim van der Heide Date: Mon, 27 Jan 2020 14:07:59 +0800 Subject: [PATCH 10/13] Update remote.xiaomi_miio.markdown (#11884) Added configuration example to create UI button in Lovelace to send IR command. --- .../_integrations/remote.xiaomi_miio.markdown | 19 +++++++++++++++++++ 1 file changed, 19 insertions(+) diff --git a/source/_integrations/remote.xiaomi_miio.markdown b/source/_integrations/remote.xiaomi_miio.markdown index d06af7d90436..ec4686169f97 100644 --- a/source/_integrations/remote.xiaomi_miio.markdown +++ b/source/_integrations/remote.xiaomi_miio.markdown @@ -85,6 +85,25 @@ remote: - pronto:pronto_hex:[optional_repeat] ``` +## Add command as entity button in Lovelace UI + +```yaml +type: entity-button +tap_action: + action: call-service + service: remote.send_command + service_data: + command: activate_towel_heater + entity_id: remote.xiaomi_miio_ir +hold_action: + action: more-info +show_icon: true +show_name: true +entity: remote.xiaomi_miio_ir +icon: 'mdi:radiator' +name: Activate Towel Heater +``` + ## Use named commands to create UI buttons ```yaml From ba7c4fdb6f52f1124d37cf209f881307bb3fed21 Mon Sep 17 00:00:00 2001 From: sverleysen Date: Mon, 27 Jan 2020 11:13:01 +0100 Subject: [PATCH 11/13] Link media_player was wrong (#11889) --- source/_docs/configuration/customizing-devices.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_docs/configuration/customizing-devices.markdown b/source/_docs/configuration/customizing-devices.markdown index e3d7d0da8fe7..8db4c27b1430 100644 --- a/source/_docs/configuration/customizing-devices.markdown +++ b/source/_docs/configuration/customizing-devices.markdown @@ -81,7 +81,7 @@ Device class is currently supported by the following components: * [Binary Sensor](/integrations/binary_sensor/) * [Sensor](/integrations/sensor/) * [Cover](/integrations/cover/) -* [Media Player](integrations/media_player/) +* [Media Player](/integrations/media_player/) ### Manual customization From f7cc22352045acd6cb3511957a728ddbe6aeda4d Mon Sep 17 00:00:00 2001 From: Franck Nijhof Date: Mon, 27 Jan 2020 15:24:22 +0100 Subject: [PATCH 12/13] Add multiple TVs example to webostv (#11819) * Add multiple TVs example to webostv * Some heading fixes --- source/_integrations/webostv.markdown | 67 ++++++++++++++++----------- 1 file changed, 41 insertions(+), 26 deletions(-) diff --git a/source/_integrations/webostv.markdown b/source/_integrations/webostv.markdown index f0c43aaf9829..a6dc2b6acd9b 100644 --- a/source/_integrations/webostv.markdown +++ b/source/_integrations/webostv.markdown @@ -18,14 +18,13 @@ There is currently support for the following device types within Home Assistant: - [Media Player](#media-player) - [Notifications](#notifications) - To begin with enable *LG Connect Apps* feature in *Network* settings of the TV [instructions](https://www.lg.com/uk/support/product-help/CT00008334-1437131798537-others). Once basic configuration is added to your `configuration.yaml` file. A notification should be visible in the frontend's **Notification** section. Follow the instructions and accept the pairing request on your TV. Pairing information will be saved to a configuration file `webostv.conf` in the Home Assistant configuration directory. This process is IP address-sensitive, in case the IP address of your TV would change in future. -### Configuration +## Configuration To add a TV to your installation, add the following to your `configuration.yaml` file: @@ -63,7 +62,7 @@ customize: type: list {% endconfiguration %} -### Example +### Full configuration example A full configuration example will look like the sample below: @@ -83,7 +82,7 @@ webostv: - youtube - makotv - netflix - + media_player: notify: @@ -91,7 +90,23 @@ notify: Avoid using `[ ]` in the `name:` of your device. -### Turn on action +### Using multiple TVs + +It is also possible to use multiple TVs with this integration. + +```yaml +# Example configuration.yaml entry with multiple TVs +webostv: + - name: Living Room TV + host: 192.168.1.100 + - name: Bedroom TV + host: 192.168.1.101 +``` + +Please note, the above provides a minimal example, however, all options are +available for each individual TV. + +## Turn on action Home Assistant is able to turn on a LG webOS Smart TV if you specify an action, like HDMI-CEC or WakeOnLan. @@ -118,11 +133,11 @@ notify: Any other [actions](/docs/automation/action/) to power on the device can be configured. -### Sources +## Sources To obtain complete list of available sources currently configured on the TV, once the webOS TV is configured and linked, while its powered on head to the **Developer Tools** > **States**, find your `media_player.` and use the sources listed in `source_list:` remembering to split them per line into your `sources:` configuration. -### Change channel through play_media service +## Change channel through play_media service The `play_media` service can be used in a script to switch to the specified tv channel. It selects the best matching channel according to the `media_content_id` parameter: @@ -146,32 +161,32 @@ data: media_content_type: "channel" ``` -### Next/Previous buttons +## Next/Previous buttons The behaviour of the next and previous buttons is different depending on the active source: - - if the source is 'LiveTV' (television): next/previous buttons act as channel up/down - - otherwise: next/previous buttons act as next/previous track +- if the source is 'LiveTV' (television): next/previous buttons act as channel up/down +- otherwise: next/previous buttons act as next/previous track -### Generic commands and buttons +## Services Available services: `button`, `command` -#### Service `webostv.button` - -| Service data attribute | Optional | Description | -|------------------------|----------|---------------------------------------------------------| -| `entity_id` | no | Target a specific webostv media player. | -| `button` | no | Name of the button. Known possible values are `LEFT`, `RIGHT`, `DOWN`, `UP`, `HOME`, `BACK`, `ENTER`, `DASH`, `INFO`, `ASTERISK`, `CC`, `EXIT`, `MUTE`, `RED`, `GREEN`, `BLUE`, `VOLUMEUP`, `VOLUMEDOWN`, `CHANNELUP`, `CHANNELDOWN`, `0`, `1`, `2`, `3`, `4`, `5`, `6`, `7`, `8`, `9` | - -#### Service `webostv.command` - -| Service data attribute | Optional | Description | -|------------------------|----------|---------------------------------------------------------| -| `entity_id` | no | Target a specific webostv media player. | -| `command` | no | Endpoint for the command, e.g. `media.controls/rewind`. The full list of known endpoints is available at https://github.com/bendavid/aiopylgtv/blob/master/aiopylgtv/endpoints.py | - -#### Example +### Service `webostv.button` + +| Service data attribute | Optional | Description | +| ---------------------- | -------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `entity_id` | no | Target a specific webostv media player. | +| `button` | no | Name of the button. Known possible values are `LEFT`, `RIGHT`, `DOWN`, `UP`, `HOME`, `BACK`, `ENTER`, `DASH`, `INFO`, `ASTERISK`, `CC`, `EXIT`, `MUTE`, `RED`, `GREEN`, `BLUE`, `VOLUMEUP`, `VOLUMEDOWN`, `CHANNELUP`, `CHANNELDOWN`, `0`, `1`, `2`, `3`, `4`, `5`, `6`, `7`, `8`, `9` | + +### Service `webostv.command` + +| Service data attribute | Optional | Description | +| ---------------------- | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `entity_id` | no | Target a specific webostv media player. | +| `command` | no | Endpoint for the command, e.g. `media.controls/rewind`. The full list of known endpoints is available at | + +### Example ```yaml script: From 8a7e31a955d14356a91f5ed1f7f4632f74b02487 Mon Sep 17 00:00:00 2001 From: "dependabot-preview[bot]" <27856297+dependabot-preview[bot]@users.noreply.github.com> Date: Mon, 27 Jan 2020 15:45:55 +0100 Subject: [PATCH 13/13] Bump jekyll-redirect-from from 0.15.0 to 0.16.0 (#11890) Bumps [jekyll-redirect-from](https://github.com/jekyll/jekyll-redirect-from) from 0.15.0 to 0.16.0. - [Release notes](https://github.com/jekyll/jekyll-redirect-from/releases) - [Changelog](https://github.com/jekyll/jekyll-redirect-from/blob/master/History.markdown) - [Commits](https://github.com/jekyll/jekyll-redirect-from/compare/v0.15.0...v0.16.0) Signed-off-by: dependabot-preview[bot] --- Gemfile | 2 +- Gemfile.lock | 20 ++++++++++---------- 2 files changed, 11 insertions(+), 11 deletions(-) diff --git a/Gemfile b/Gemfile index bd668c466be7..1610c7107143 100644 --- a/Gemfile +++ b/Gemfile @@ -12,7 +12,7 @@ end group :jekyll_plugins do gem 'jekyll-paginate', '1.1.0' - gem 'jekyll-redirect-from', '0.15.0' + gem 'jekyll-redirect-from', '0.16.0' gem 'jekyll-sitemap', '1.4.0' gem 'jekyll-time-to-read', '0.1.2' gem 'jekyll-commonmark', '1.3.1' diff --git a/Gemfile.lock b/Gemfile.lock index 49dcc096717a..38b8e529df22 100644 --- a/Gemfile.lock +++ b/Gemfile.lock @@ -25,11 +25,11 @@ GEM http_parser.rb (~> 0.6.0) eventmachine (1.2.7) eventmachine (1.2.7-x64-mingw32) - ffi (1.11.2) - ffi (1.11.2-x64-mingw32) + ffi (1.12.1) + ffi (1.12.1-x64-mingw32) forwardable-extended (2.6.0) http_parser.rb (0.6.0) - i18n (1.7.0) + i18n (1.8.2) concurrent-ruby (~> 1.0) jekyll (4.0.0) addressable (~> 2.4) @@ -50,7 +50,7 @@ GEM commonmarker (~> 0.14) jekyll (>= 3.7, < 5.0) jekyll-paginate (1.1.0) - jekyll-redirect-from (0.15.0) + jekyll-redirect-from (0.16.0) jekyll (>= 3.3, < 5.0) jekyll-sass-converter (2.0.1) sassc (> 2.0.1, < 3.0) @@ -64,7 +64,7 @@ GEM kramdown-parser-gfm (1.1.0) kramdown (~> 2.0) liquid (4.0.3) - listen (3.2.0) + listen (3.2.1) rb-fsevent (~> 0.10, >= 0.10.3) rb-inotify (~> 0.9, >= 0.9.10) mercenary (0.3.6) @@ -78,15 +78,15 @@ GEM mini_portile2 (~> 2.4.0) pathutil (0.16.2) forwardable-extended (~> 2.6) - public_suffix (4.0.1) + public_suffix (4.0.3) rack (2.0.8) rack-protection (2.0.8.1) rack rake (13.0.1) rb-fsevent (0.10.3) - rb-inotify (0.10.0) + rb-inotify (0.10.1) ffi (~> 1.0) - rouge (3.13.0) + rouge (3.15.0) ruby-enum (0.7.2) i18n ruby2_keywords (0.0.1) @@ -111,7 +111,7 @@ GEM concurrent-ruby (~> 1.0) tzinfo-data (1.2019.3) tzinfo (>= 1.0.0) - unicode-display_width (1.6.0) + unicode-display_width (1.6.1) PLATFORMS ruby @@ -122,7 +122,7 @@ DEPENDENCIES jekyll (= 4.0.0) jekyll-commonmark (= 1.3.1) jekyll-paginate (= 1.1.0) - jekyll-redirect-from (= 0.15.0) + jekyll-redirect-from (= 0.16.0) jekyll-sitemap (= 1.4.0) jekyll-time-to-read (= 0.1.2) nokogiri (= 1.10.7)