Hi All,
Today i saw that git has been updated to 2.47.1 already by end of November
Release Notes
You can check your current version with the following command
git -v to update use the command below (cmd must be started “As Administrator”)
git update-git-for-windows This will download and start the update installer
Let’s check the git version after the update
Regards
Andres Bohren
vscode Logo
Hi All,
Today i noticed that there is an update for Git
Highlights from Git 2.47 Release Notes 2.47.0 Let’s have a look at the installed version
git -v to update use the command below (cmd must be started “As Administrator”)
git update-git-for-windows This will download and start the update installer
Let’s check the git version after the update
git -v You can also download it here: https://git-scm.com/
Regards
Andres Bohren
Hi All,
Today i noticed that there is an update for Git
Highlights from Git 2.46 Release Notes 2.46.0 Let’s have a look at the installed version
git -v to update use the command below (cmd must be started “As Administrator”)
git update-git-for-windows This will download and start the update installer
Let’s check the git version after the update
git -v You can also download it here: https://git-scm.com/
Regards
Andres Bohren
Hi All,
Today i noticed that there is an update for Git
Securing Git: Addressing 5 new vulnerabilities
CVE-2024-32002 (Critical, Windows & macOS): Git repositories with submodules can trick Git into executing a hook from the .git/ directory during a clone operation, leading to Remote Code Execution. CVE-2024-32004 (High, multi-user machines): An attacker can craft a local repository that executes arbitrary code when cloned. CVE-2024-32465 (High, all setups): Cloning from .
Hi All,
Two days ago, git 2.45 has been released.
Read the Blog post here: Highlights from Git 2.45
Git 2.45 Release Notes
Let’s have a look at the installed version
git -v to update use the command below (cmd must be started “As Administrator”)
git update-git-for-windows This will download and start the update installer
Let’s check the git version after the update
git -v You can also download it here: https://git-scm.
Hi All,
Two days ago, git 2.44 has been released.
Read the Blog post here: Highlights from Git 2.44
Git 2.44 Release Notes
Let’s have a look at the installed version
git -v to update use the command below (cmd must be started “As Administrator”)
git update-git-for-windows This will download and start the update installer
Let’s check the git version after the update
git -v You can also download it here: https://git-scm.
Hi All,
Today i have realized, that git 2.43 has been released already on November 22 2023.
Read the Blog post here: Highlights from Git 2.43
Git 2.43 Release Notes
Let’s have a look at the installed version
git -v to update use the command below (cmd must be started “As Administrator”)
git update-git-for-windows This will download and start the update installer
Let’s check the git version after the update
Hi All,
A few days ago git 2.42 has been released. Read the Blog post here: Highlights from Git 2.42
Git 2.42 Release Notes
Let’s have a look at the installed version
git -v to update use the command below (cmd must be started “As Administrator”)
git update-git-for-windows Let’s check the git version after the update
git -v Regards
Andres Bohren
vscode Logo
Hi All,
I’ve had a warning in my Azure DevOps Pipeline, that deploys this Blog via Hugo to Azure Static Website.
The build number format string Azure Static Web Apps CI/CD generated a build number Azure Static Web Apps CI/CD which contains invalid character(s), is too long, or ends with ‘.’. The maximum length of a build number is 255 characters. Characters which are not allowed include ‘"’, ‘/’, ‘:’, ‘<’, ‘>’, ‘', ‘|’, ‘?
Hi All,
In Microsoft Code 1.79, there has been an update that fixes a security issue.
You can find the details here Closed Issue
A information disclosure vulnerability exists in VS Code 1.79.0 and earlier versions on Windows when file system operations are performed on malicious UNC paths. Examples include reading or resolving metadata of such paths. An authorised attacker must send the user a malicious file and convince the user to open it for the vulnerability to occur.
