RSS Bot

Description Support for mainline for Rock 5B. Currently working is just EMMC. There is also ethernet support, but rock 5b uses PCIe for ethernet. How Has This Been Tested? Booted my Rock 5B fine, but have no EMMC, so the init could not mount the root drive. If someone can help with the testing... Checklist: [x ] My code follows the style guidelines of this project [ x] I have performed a self-review of my own code [ x] I have commented my code, particularly in hard-to-understand areas [ ] I have made corresponding changes to the documentation [ x] My changes generate no new warnings [ x] Any dependent changes have been merged and published in downstream modules View the full article

Description Jira reference number AR-1449 How Has This Been Tested? [ ] Tested in working branch Checklist: [ ] My code follows the style guidelines of this project [ ] I have performed a self-review of my own code [ ] I have commented my code, particularly in hard-to-understand areas [ ] I have made corresponding changes to the documentation [ ] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article

I had no trouble with my first experience with NanoPi R6S while installing and running the FriendlyWrt/OpenWrt 22.03 image, but that was another story when testing Ubuntu or Debian as the mini PC would not boot at all after flashing the images with eFlasher apparently successfully, but suspiciously fast (under 2 seconds). I spent nearly four hours trying the different images and then the Rockchip Windows utility, but all my attempts failed, and FriendlyElec was not overly helpful. So I decided to connect a serial console to see what was going on. The NanoPi R6S comes with a 3-pin header for the serial console, but it’s not populated. So I soldering one, but not at the top of the bottom, and instead at the bottom since it would allow me to still use the metal enclosure to cool the processor. Some readers, or at least one, often complain about the [...] The post Adding an external serial console port to NanoPi R6S appeared first on CNX Software - Embedded Systems News. View the full article

Description switch sunxi EDGE to 6.1.1; CURRENT to 5.15.85 Checklist: Successfully rebased and updated: v6.1.1; v5.15.85 [ ] Test build sunxi [ ] Test build sunxi64 View the full article

paperd.ink Merlot is a tricolor E-paper display with an open-source hardware control board based on ESP32 wireless SoC that is programmable with Arduino, MicroPython, or the ESP-IDF framework. We first wrote about the paperd.ink 4.2-inch ESP32-based monochrome e-Paper display last year, but the company has now refined its design with the “paperd.ink Classic” replacing the 3D printed enclosure with a vacuum cast enclosure and adding a 1,900 mAh battery. They also launched a new model, the Merlot, based on the same design but with a display supporting three colors: black, white, and red. Merlot specifications: Wireless module – ESP32-WROOM-32 module with ESP32 dual-core processor, 4 MB SPI flash, 2.4 GHz WiFi 4 & Bluetooth LE connectivity Storage – MicroSD card slot for storing images, files, etc Display – 4.2″ tricolor e-Paper display with 400 x 300 resolution; full refresh: ~ 17 seconds; partial update: also 17 seconds… USB – 1x [...] The post Merlot is an open-source hardware tricolor wireless E-paper display appeared first on CNX Software - Embedded Systems News. View the full article

James Brown (aka Ancient) has built a tiny computer inside a LEGO brick with a Raspberry Pi RP2040 microcontroller and a 0.42-inch monochrome OLED display. And yes, it runs Doom. So finally, the LEGO minifigures have access to a computer suitable for their size :). James did not post a lot of information to reproduce the build by yourself, but he still released the “uGrey” code, written in Micropython, to display greyscale on a monochrome OLED. We can learn from the design in a mesmerizing video (embedded at the end of this post) showing how he made a Raspberry Pi RP2040 computer fit into a LEGO brick. The tiny design is comprised of five main boards/modules: Raspberry Pi RP2040 module The micro USB module Two side modules with other components A 0.42-inch OLED display with 72×40 resolution (SSD1306) Since soldering the four modules together by hand only would be really [...] The post LEGO brick with Raspberry Pi RP2040 runs Doom appeared first on CNX Software - Embedded Systems News. View the full article

Description Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change. Jira reference number AR-1438 Tony McKahan an issue complaining that rockpis, among others, was overwriting the mainline kernels devtree. This patch replaces the existing sequence of board-rockpis-* patches doing that with a single one that starts from the rockpi-s devtree newly included in the mainline kernel. In reviewing the devtree, I noticed that the Bluetooth items for UART4 had somehow been lost. So, I restored them. How Has This Been Tested? Build new image. Verified WiFi, ethernet and USB still worked. Also verified that Bluetooth did not work before this patch was applied. Bluetooth works now. Checklist: [x] My code follows the style guidelines of this project [x] I have performed a self-review of my own code [x] I have commented my code, particularly in hard-to-understand areas [x] I have made corresponding changes to the documentation [x] My changes generate no new warnings [x] Any dependent changes have been merged and published in downstream modules View the full article

Description Update u-boot patches for JetHub D1/D1+ add rescue boot from microSD revert JetHub D1 eth mac generation with manufacturer OUI Jira reference number AR-1448 How Has This Been Tested? Please describe the tests that you ran to verify your changes. Please also note any relevant details for your test configuration. [ ] Test A [ ] Test B Checklist: [ ] My code follows the style guidelines of this project [ ] I have performed a self-review of my own code [ ] I have commented my code, particularly in hard-to-understand areas [ ] I have made corresponding changes to the documentation [ ] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article

Wilderness Labs Meadow F7v2 Feather is an STM32F7 Arm Cortex-M7 development board following the Adafruit Feather form factor and programmable with C# through a lightweight implementation of the .NET framework. We had previously seen the .NET Framework running on Android and Linux thanks to Xamarin’s Mono, but I don’t think I had ever a microcontroller-class board supporting the .NET framework and C# programming. But that’s exactly what the Meadow F7v2 Feather does. Meadow F7v2 Feather specifications: MCU – STMicro STM32F7 Arm Cortex-M7 microcontroller @ 216 MHz with 2D graphics and JPEG accelerators Memory – 32MB RAM Storage – 64MB flash Connectivity – 2.4 GHz WiFi and BLE (ESP32) with onboard and external u.FL antennas USB – 1x Micro USB port for power and programming Expansion with through and castellated holes with up to 25x GPIO, 12x PWM, 6x analog inputs, 2x DAC, I2C, I2S input/output, SPI, UART, CAN Bus Misc [...] The post Meadow F7v2 Feather STM32F7 MCU board supports .NET, C# programing appeared first on CNX Software - Embedded Systems News. View the full article

When PricelessToolkit failed to find an affordable (indoor) irrigation system that works with Home Assistant and ESPHome, he built the DROPLET board based on ESP32 wireless SoC and supporting up to five micro-pumps and soil moisture sensors. The board also comes with switches to manually control the pump, a built-in DS18B20 temperature sensor, a buzzer, and a I/O header to connect an expansion header for relay control, I2C, GPIOs, and an external DS18B20 temperature sensor. DROPLET specifications: Wireless module – ESP32-S with ESP32 dual-core 32-bit microcontroller @ 240 MHz with 2.4 GHz WiFi and Bluetooth connectivity, 4MB SPI flash Display – I2C header for 5V/3.3V OLED display Pump interfaces – 5x 2-pin connectors for micropumps Sensors and sensor interfaces DS18B20 temperature sensor 5x 3-pin connectors for soil moisture sensors; pulled low with a 1 MΩ resistor. Expansion – 2x 16-pin right-angle female header with GPIOs, UART, 5V, and GND Debugging [...] The post DROPLET irrigation system works with ESPhome and Home assistant appeared first on CNX Software - Embedded Systems News. View the full article

Description mipi_dsi_driver adjust function remove return void on linux6.1 (this patch also add new: orientation custom, reset level custom) nanopct4 rt5651 sound repeat pinctrl cause problem [ 7.395164] rockchip-pinctrl pinctrl: pin gpio4-0 already requested by ff880000.i2s; cannot claim for 1-001a [ 7.395192] rockchip-pinctrl pinctrl: could not request pin 128 (gpio4-0) from group i2s-8ch-mclk on device rockchip-pinctrl How Has This Been Tested? [x] product panel_simple_dsi.ko on linux6.1 [x] nanopct4 rt5651 sound normal on linux6.1 Checklist: [x] My code follows the style guidelines of this project [x] I have performed a self-review of my own code [ ] I have commented my code, particularly in hard-to-understand areas [ ] I have made corresponding changes to the documentation [x] My changes generate no new warnings [x] Any dependent changes have been merged and published in downstream modules View the full article

Banana BPI-Bit-S2 is a board for the education market that’s compatible with the BBC Micro:bit V2, but offers WiFi connectivity instead of Bluetooth LE through an Espressif Systems ESP32-S2 wireless microcontroller. The BPI-Bit-S2 succeeds the earlier Banana Pi BPI-Bit with ESP32 WiFi & BLE microcontroller that was a closer match to the original BBC Micro:bit than the new ESP32-S2 board for which I see little benefit, except for the slightly lower price tag. Banana BPI-Bit-S2 specifications: Wireless MCU – Espressif Systems ESP32-S2FN4R2 single core LX7 microcontroller with 320 kB SRAM, 2MB PSRAM, 4MB flash, 2.4 GHz WiFi connectivity LEDs – 25x RGB LED matrix USB – 1x USB Type-C port for power and programming Sensors – 2x light sensors, 1x thermistor sensor Expansion – 3x I/O rings, 3V/GND rings, 20-pin edge connector (compatible with BBC Micro:bit V2 design) with up to 16x GPIO, I2C, SPI, 3.3V, and GND Misc – [...] The post Banana BPI-Bit-S2 BBC Micro:bit compatible board supports WiFi appeared first on CNX Software - Embedded Systems News. View the full article

Description moving out cleaning TBD: handling of parameters, removing of parameter "build repo as its not needed" edit aptly.conf in mktemp folder Jira reference number AR-1444 How Has This Been Tested? ./repo input output "update" "/home/igorp/Devel/build/" password sid,jammy,bullseye,focal This looks into input and make a repo in output, for sid,jammy, ... Checklist: [ ] My code follows the style guidelines of this project [ ] I have performed a self-review of my own code [ ] I have commented my code, particularly in hard-to-understand areas [ ] I have made corresponding changes to the documentation [ ] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article

Qualcomm QCX216 is a new IoT-optimized LTE Cat1 bis modem with a data rate of up to 10 Mbps at ultra-low power and support for WiFi-based terrestrial positioning thanks to the company’s database of billions of geolocated beacons. LTE Cat1 bis is an update to LTE Cat1 that does not require software and hardware upgrades to the base stations, enables smaller, simpler, and cheaper designs with a single antenna, and delivers higher speeds than LTE Cat M1 typically used in IoT applications. Qualcomm QCX216 LTE IoT modem will be used in smart utility meters, trackers, e-mobility solutions, parking meters, home automation and security equipment, and other location-based solutions. Qualcomm QCX216 specifications: SoC – Qualcomm 216 LTE IoT modem with dual-core Cortex-M3 @ 204 MHz, cellular modem-RF Wireless Cellular Peak Download Speed: 10 Mbps Peak Upload Speed: 5 Mbps Cellular Technology: Rel.14 LTE, Global LTE Cat 1bis Multi SIM: Dual SIM/eSIM [...] The post Qualcomm QCX216 LTE Cat1 bis IoT-optimized modem integrates WiFi-based terrestrial positioning appeared first on CNX Software - Embedded Systems News. View the full article

We’ve previously covered the EdgeBox-RPi4 industrial controller powered by a Raspberry Pi Compute Module 4 and plenty of I/Os such as RS485, RS232, digital inputs and outputs, and connectivity options such as Gigabit Ethernet, WiFi 5, Bluetooth 5, and 4G LTE. But if you don’t quite need the power of a Linux controller, the EdgeBox-ESP-100 industrial edge controller based on an ESP32-S3 dual-core WiFi and Bluetooth microcontroller and offering a similar set of features, albeit with twists, may be an interesting option. EdgeBox-ESP-100 specifications: Microcontroller – Espressif Systems ESP32-S3 dual-core Tensilica LX7 microcontroller @ 240 MHz with AI vector instructions, 512KB RAM Memory – 8MB PSRAM Storage – 16MB Flash Network connectivity 10/100M Ethernet RJ45 port 2.4 GHz WiFi 4 and Bluetooth 5.0 LE via ESP32-S3 4G LTE cellular via SIMCom A7670G LTE Cat 1 module Optional support for LoRa (replaces the A7670G module) Serial & I/Os via terminal blocks [...] The post EdgeBox-ESP-100 – An ESP32-S3 industrial controller with RS485, CAN Bus, DIO, 4G LTE, and more appeared first on CNX Software - Embedded Systems News. View the full article

Description Patch was already eliminated in 5.15, resolve "edge" https://github.com/armbian/build/commit/9680fc46a01f70984e7b4b4c975b8dc4ecd8798e View the full article

Arducam Mega is a 3MP or 5MP camera specifically designed for microcontrollers with an SPI interface, and the SDK currently supports Arduino UNO and Mega2560 boards, ESP32/ESP8266 boards, Raspberry Pi Pico and other boards based on RP2040 MCU, BBC Micro:bit V2, as well as STM32 and MSP430 platform. Both cameras share many of the same specifications including their size, but the 3MP model is a fixed-focus camera, while the 5MP variant supports autofocus. Potential applications include assets monitoring, wildfire monitoring, remote meter reading, TinyML applications, and so on. Arducam Mega specifications: Camera Type 3MP with fixed focus 5MP with auto-focus from 8cm to infinity Optical size – 1/4-inch Shutter type – Rolling Focal ratio 3MP – F2.8 5MP – F2.0 Still Resolutions 320×240, 640×480, 1280×720 x 1600 x1200x 1920 x 1080 3MP – 2048 x 1536 5MP – 2592×1944 Output formats – RGB, YUV, or JPEG Wake-up time 3MP – [...] The post Arducam Mega – A 3MP or 5MP SPI camera for microcontrollers (Crowdfunding) appeared first on CNX Software - Embedded Systems News. View the full article

BPI-M2S is a small form factor SBC based on the Amlogic A311D chipset (or s922x, not supported yet): Amlogic A311D (Quad A73 + Dual A53) CPU 4GB LPDDR4 RAM 16GB eMMC Mali G52-MP4 GPU HDMI 2.1 output 2 Gigabit ports 40 pins GPIO 1x USB-A 2.0 1 USB-C (5V power) Not working/tested: 2nd ethernet port MIPI DSI/CSI Description I created a dts from existing A311D board (vim3 and radxa zero2). I use the radxa zero2 u-boot that allows to launch armbian linux kernel for this board. The dts is basic for now, since I'm not an expert with device trees. Jira reference number [AR-9999] How Has This Been Tested? Please describe the tests that you ran to verify your changes. Please also note any relevant details for your test configuration. [ x] Test A : the board starts and CLI works, details here: https://paste.armbian.com/piyuqajeye [ ] Test B Checklist: [ ] My code follows the style guidelines of this project [ x] I have performed a self-review of my own code [ ] I have commented my code, particularly in hard-to-understand areas [ ] I have made corresponding changes to the documentation [ ] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article

The development of Monado's inside-out tracking solution keeps improving and more devices are now supported. Here's an overview of where things stand, as presented at the FOSS XR conference in October. View the full article

Description of changes by commit Fix variable $root_partition_device to be a device path - as it is intended to be. Otherwise at least this line would fail: https://github.com/armbian/build/blob/8cc5b2664c8e49e252e5d383b983b8601440d8e7/packages/bsp/common/usr/sbin/armbian-install#L539 root_partition_device is all time equal to root_partition_device_name, since the lsblk does not list device path names rather than just the device (end-)name. Fixed to get e.g.: root_partition_device=/dev/mmcblk0 root_partition_device_name=mmcblk0 commit: d7cf33ae3ce9850d4b9e0f9edb4ec7595fb2220a Fix determination and usage of variable $sduuid Issue: The last grep filter in the following line is useless, since blkid -o export provides a multiline output with the device name being on another line than UUID=... https://github.com/armbian/build/blob/8cc5b2664c8e49e252e5d383b983b8601440d8e7/packages/bsp/common/usr/sbin/armbian-install#L97 So it has been fixed as follows: a) lookup mmc devices excluding the mmc device probably providing the current root partition b) if there is no sduuid determined by this lookup, then lookup any mmc partition matching /dev/mmcblk*p1 c) move the sduuid calculation to the script header to enable usage for scenario selection filtering d) hide installation scenario 1) selection, if $sduuid is empty, since $sduuid is essential for that scenario commit: 7e9ebe1861f6db6f30cd6fae5eff5594d6e5bdd9 Hide current root partition device from destination selection add new variable $root_partition_name use this variable to filter current root partition from destination selection in check_partitions() commit: e791261c65152c504aa0a0ece5af72031e2af800 Fix behavior in case of no available partition The logic in check_partitions() in case of no available partition is improved not to fail for a hidden reason and UX for fresh disk devices is improved Fix the calculation of $FREE_SPACE for devices without or with an empty partition table Ask the user to proceed AFTER the minimum free capacity required is verified Improve the logic for auto-creating initial partitions as follows: a) Check for a minimum free space of 4GB for a partition b) Ask user to proceed with auto-created partition(s) or not c) Distinguish between UEFI and non UEFI device d) Create a partition of full free size for non UEFI devices also commit: 6173bb24e4b0ec7b00c13ed2153ccbb7d7e4cda5 Add support for MTD char driven flash replace $spicheck by $mtdcheck add probable MTD char device partitions to $mtdcheck update comments and dialog content: replace "SPI Flash" by "MTD Flash" replace call of "create_armbian 'spi' ..." by "create_armbian 'mtd' ..." update description for /dev/nand1 /dev/nand2 as "legacy SUNXI NAND" additional parameters passed to import function "write_uboot_platform_mtd": $3 - Log file name $4 - SPACE separated list of all MTD device partition(s) commit: 660e181beadb11a2176ee6c5b42147a3534b9a99 How Has This Been Tested? [x] Tested on a Cubietruck board: booted from SD card Select "MTD Flash boot | USB/SATA/NVMe root install" installing to a SATA SSD without any partition table initialized MTD char driven partitions mtd0-mtd3 matching SPL and U-Boot partition labels / names. Would be good, if somebody else could run a test on: EFI board Board with mtdblock driven SPI flash Checklist: [x] My code follows the style guidelines of this project [x] I have performed a self-review of my own code [x] I have commented my code, particularly in hard-to-understand areas [ ] I have made corresponding changes to the documentation [x] My changes generate no new warnings [n/a] Any dependent changes have been merged and published in downstream modules View the full article

LilyGO has launched a new ESP32-S3 WiFi & BLE camera board with the T-Camera S3 also featuring a small display, a PIR motion sensor, and a microphone, as well as an optional plastic shell. The T-Camera S3 is an evolution of the TTGO T-Camera ESP32 board introduced in 2019 with many of the same features, but the ESP32 microcontroller has been replaced with an ESP32-S3 microcontroller with vector extensions that makes it suitable for machine learning and computer vision applications. The new board also comes with a larger 16 MB SPI flash, more I/Os, and a few other small changes. T-Camera S3 specifications: ESP32-S3-WROOM-1 wireless module SoC – ESP32-S3FN16R8 dual-core Tensilica LX7 microcontroller @ 240 MHz (Note: this SKU is not listed in the official ESP32-S3 datasheet) with 2.4 GHz 802.11n WiFI 4 and Bluetooth 5.0 LE connectivity Memory – 8MB PSRAM Storage – 16MB SPI flash Camera – 2MP [...] The post T-Camera S3 – An ESP32-S3 board with camera, display, PIR motion sensor, and microphone appeared first on CNX Software - Embedded Systems News. View the full article

Description Add armbian patches to EDGE 6.1 Switch CURRENT to v5.15.84 Checklist: [x] Test build sunxi [x] Test build sunxi64 View the full article

The Banana Pi PPI-M2S is a single board computer (SBC) powered by either Amlogic A311D or S922X processor with 4GB RAM, 16GB eMMC flash, HDMI 2.1 and MIPI DSI display interfaces, one MIPI CSI camera connector, two Gigabit Ethernet ports with one PoE capable, as well as optional WiFi 5 & Bluetooth support. When we first covered the Banana Pi BPI-M2S over a year ago, all we had were some 3D renders of the board and some preliminary specifications. The company has now manufactured the board, provided some documentation, and started to take orders for the board on Aliexpress for $95.79 or $100 depending on whether Amlogic S922X or A311D is selected. Banana Pi BPI-M2S specifications: SoC – Amlogic A311D or S922X hexa-core processor with 4x Arm Cortex-A73 cores @ 2.21 GHz, 2x Arm Cortex-A53 cores @ 1.8 GHz, Arm Mali-G52 MP4 (6EE) GPU with OpenGL ES 3.2, Vulkan 1.0 [...] The post $96+ Banana Pi BPI-M2S Amlogic A311D/S922X SBC offers dual GbE, optional PoE and WiFi 5 appeared first on CNX Software - Embedded Systems News. View the full article

Bumps ossf/scorecard-action from 2.0.6 to 2.1.0. Release notes Sourced from ossf/scorecard-action's releases. v2.1.0 What's Changed Scorecard version This release uses scorecard v4.10.0. Improvements Docker build workflow by @​naveensrinivasan in ossf/scorecard-action#981 Use root user in distroless to support GitHub Actions by @​spencerschrock in ossf/scorecard-action#994 Disable pull_request_target by @​laurentsimon in ossf/scorecard-action#1031 Documentation Add PAT section explaining risks by @​olivekl in ossf/scorecard-action#1024 Make the badge text easier to copy by @​rajbos in ossf/scorecard-action#1026 New Contributors @​joycebrum made their first contribution in ossf/scorecard-action#984 @​rajbos made their first contribution in ossf/scorecard-action#1026 Full Changelog: https://github.com/ossf/scorecard-action/compare/v2.0.6...v2.1.0 Commits 937ffa9 Minor release v2.1.0 (#1040) a42a080 Create scorecards.yml (#1041) cf93e24 :seedling: Bump github.com/ossf/scorecard/v4 from 4.8.0 to 4.10.0 (#1039) b2f0d4e :seedling: Bump golang from 04f76f9 to 54184d6 (#1038) bff7712 :seedling: Bump actions/checkout from 3.1.0 to 3.2.0 (#1035) cd50e39 :seedling: Bump github/codeql-action from 2.1.35 to 2.1.36 (#1036) 420fff2 update (#1031) 8d8c1ec :seedling: Bump golang.org/x/net from 0.2.0 to 0.4.0 (#1033) c694c35 feat: update logging (#1032) f27f8fe :seedling: Bump golang from 84ac6d8 to 04f76f9 (#1029) Additional commits viewable in compare view Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase. Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: @dependabot rebase will rebase this PR @dependabot recreate will recreate this PR, overwriting any edits that have been made to it @dependabot merge will merge this PR after your CI passes on it @dependabot squash and merge will squash and merge this PR after your CI passes on it @dependabot cancel merge will cancel a previously requested merge and block automerging @dependabot reopen will reopen this PR if it is closed @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) View the full article

Bumps cirrus-actions/rebase from 1.7 to 1.8. Release notes Sourced from cirrus-actions/rebase's releases. 1.8 What's Changed docs: Fix errors in the example in README.md (#1) by @​martolini in cirrus-actions/rebase#98 runs-on property missing. by @​dim0627 in cirrus-actions/rebase#102 fix(chore): bugs autosquash always set true by @​adeherysh in cirrus-actions/rebase#103 New Contributors @​martolini made their first contribution in cirrus-actions/rebase#98 @​dim0627 made their first contribution in cirrus-actions/rebase#102 @​adeherysh made their first contribution in cirrus-actions/rebase#103 Full Changelog: https://github.com/cirrus-actions/rebase/compare/1.7...1.8 Commits b87d481 fix(chore): bugs autosquash always set true (#103) 5000741 runs-on property missing. (#102) 418e518 docs: Fix errors in the example in README.md (#1) (#98) See full diff in compare view Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase. Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: @dependabot rebase will rebase this PR @dependabot recreate will recreate this PR, overwriting any edits that have been made to it @dependabot merge will merge this PR after your CI passes on it @dependabot squash and merge will squash and merge this PR after your CI passes on it @dependabot cancel merge will cancel a previously requested merge and block automerging @dependabot reopen will reopen this PR if it is closed @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) View the full article