Tags give the ability to mark specific points in history as being important
-
v1.3.0-rc1
protectedbc9cf388 · ·Release branch for v1.3 ## [v1.3.0] - 2022-05-25 ### Fixed - tftpboot: don't start docker image if tftpboot directory does not exist - bootstrap: warn if image is already running ### Changed - Replace ISC DHCP server with dnsmasq ### Added - ftps: Support implicit FTPS on port 990 - bootstrap: Add FTP support - bootstrap: Enable remote logging
-
v1.3
protectedRelease: bootstrap v1.3bc9cf388 · ·Release branch for v1.3 ## [v1.3.0] - 2022-05-25 ### Fixed - tftpboot: don't start docker image if tftpboot directory does not exist - bootstrap: warn if image is already running ### Changed - Replace ISC DHCP server with dnsmasq ### Added - ftps: Support implicit FTPS on port 990 - bootstrap: Add FTP support - bootstrap: Enable remote logging
-
v1.2.0-rc1
protectedf635a5d9 · ·Release branch for v1.2 ## [v1.2.0] - 2022-03-04 ### Fixes - imx_usb: Rely on `/sys/bus/usb/devices/` instead of `/sys/bus/hid/devices/` - shellcheck: compliance with v0.8.0 - bootstrap: warn if image is already running - tftpboot: don't start docker image if tftpboot directory does not exist ### Added - bootstrap: Enable remote logging
-
v1.2
protectedRelease: bootstrap v1.2f635a5d9 · ·Release branch for v1.2 ## [v1.2.0] - 2022-03-04 ### Fixes - imx_usb: Rely on `/sys/bus/usb/devices/` instead of `/sys/bus/hid/devices/` - shellcheck: compliance with v0.8.0 - bootstrap: warn if image is already running - tftpboot: don't start docker image if tftpboot directory does not exist ### Added - bootstrap: Enable remote logging
-
v1.1.0-rc1
protected47fbf084 · ·Release branch for 1.1 - Simpler multiarch releases - Sync and Cleanup - USB boot support for i.MX using imx_usb_loader (Auto-created release candidate)
-
v1.0.4
protectedRelease: bootstrap v1.0.40f5ac27f · ·Release of v1.0.4 - logrotate: fix infinite loop
-
v1.0.3
protectedRelease: bootstrap v1.0.3795b1dec · ·Release of v1.0.3 - Follow u-boots naming scheme for fit images
-
v1.0.2
protectedRelease: bootstrap v1.0.2f76923d1 · ·Release of v1.0.2 Use proper U-Boot naming convention Note, that the methodology was changed with regards to multi-arch containers. - CI: Resync .gitlab-ci.yml file with other repositories - Ignore shellcheck warning SC2021 - Use the proper filename for signed U-Boot targets
-
v1.0.1
protectedRelease: bootstrap v1.0.11aa07e70 · ·Fix dhcp start failure A small hotfix to correct a problem with container startup. - dhcp: Fix dhcp config path
-
v1.0.0
protectedRelease: bootstrap v1.0.04cf5fb38 · ·First release! This is our first release creating initial boot support for devices that can boot from the network. Special support exists for the Sitara AM335x series of chips which can boot from the network without any software support on the board itself (other then its own bootrom).
-
v1.0.0-rc1
protected4cf5fb38 · ·First release! This is our first release creating initial boot support for devices that can boot from the network. Special support exists for the Sitara AM335x series of chips which can boot from the network without any software support on the board itself (other then its own bootrom). - Add support for sitara 335x series bootrom - Add a few simple convenience functions - Create basic bootstrapping infrastructure (Auto-created release candidate)
-
v1.0
protected4cf5fb38 · ·First release! This is our first release creating initial boot support for devices that can boot from the network. Special support exists for the Sitara AM335x series of chips which can boot from the network without any software support on the board itself (other then its own bootrom). - Add support for sitara 335x series bootrom - Add a few simple convenience functions - Create basic bootstrapping infrastructure