The Latvian Legion
Documentation

The Latvian Legion Apr 2026

The was a national military formation within the German Waffen-SS, established in 1943 during the Nazi occupation of Latvia. Comprising primarily of the 15th and 19th Waffen Grenadier Divisions, it remains one of the most complex and debated legacies of World War II in the Baltic region. Historical Context: The "Devil's Pact"

For many Latvians, the Legion was viewed as a "lesser evil" compared to the Soviet Union, which had brutally occupied and annexed Latvia in 1940. The Latvian Legion

: The 15th Division was famously the most decorated non-German Waffen-SS unit. Elements of the Legion were among the last Axis forces to surrender, holding the "Courland Pocket" until the very end of the war in May 1945. The Latvian Legion: the Most Topical Research Problems The was a national military formation within the

: While officially named a "Volunteer Legion" to circumvent international laws against drafting occupied populations, roughly 80–85% of members were actually conscripted . : The 15th Division was famously the most

: Many soldiers joined or were conscripted with the hope of restoring Latvian independence, drawing inspiration from the 1918–1920 War of Independence where they fought off both Bolshevik and German forces.

New in InfluxDB 3.7

Key enhancements in InfluxDB 3.7 and the InfluxDB 3 Explorer 1.5.

See the Blog Post

InfluxDB 3.7 is now available for both Core and Enterprise, landing alongside version 1.5 of the InfluxDB 3 Explorer UI. This release focuses on giving developers faster visibility into what their system is doing with one-click monitoring, a streamlined installation pathway, and broader updates that simplify day-to-day operations.

For more information, check out:

InfluxDB Docker latest tag changing to InfluxDB 3 Core

On February 3, 2026, the latest tag for InfluxDB Docker images will point to InfluxDB 3 Core. To avoid unexpected upgrades, use specific version tags in your Docker deployments.

If using Docker to install and run InfluxDB, the latest tag will point to InfluxDB 3 Core. To avoid unexpected upgrades, use specific version tags in your Docker deployments. For example, if using Docker to run InfluxDB v2, replace the latest version tag with a specific version tag in your Docker pull command–for example:

docker pull influxdb:2