chore: prep 4.1.0 release

CHANGELOG.md

@@ -1,6 +1,6 @@
 # SingularityCE Changelog
 
-## Changes Since Last Release
+## 4.1.0 \[2024-01-25\]
 
 ### Changed defaults / behaviours
 
@@ -12,15 +12,6 @@
 
   The container / instance will be started in the current cgroup, and information
   about the configuration issue displayed to the user as warnings.
-
-### Bug Fixes
-
-- Added missing `tmp sandbox` directive to `singularity.conf` template.
-
-## 4.0.1-rc.1 Release Candidate \[2024-01-12\]
-
-### Changed defaults / behaviours
-
 - In native mode, SIF/SquashFS container images will now be mounted with
   squashfuse when kernel mounts are disabled in `singularity.conf`, or cannot be
   used (non-setuid / user namespace workflow). If the FUSE mount fails,
@@ -60,6 +51,10 @@
   to a temporary sandbox before running it, when it would otherwise perform a
   kernel or FUSE mount.
 
+### Bug Fixes
+
+- Added missing `tmp sandbox` directive to `singularity.conf` template.
+
 ### Deprecated Functionality
 
 - The experimental `--sif-fuse` flag, and `sif fuse` directive in

INSTALL.md

@@ -232,11 +232,11 @@ cd singularity
 By default your clone will be on the `main` branch which is where development
 of SingularityCE happens. To build a specific version of SingularityCE, check
 out a [release tag](https://github.com/sylabs/singularity/tags) before
-compiling. E.g. to build the 4.1.0-rc.1 release candidate, checkout the
-`v4.1.0-rc.1` tag:
+compiling. E.g. to build the 4.1.0 release, checkout the
+`v4.1.0` tag:
 
 ```sh
-git checkout --recurse-submodules v4.1.0-rc.1
+git checkout --recurse-submodules v4.1.0
 ```
 
 ## Compiling SingularityCE
@@ -287,7 +287,7 @@ build and install the RPM like this:
 <!-- markdownlint-disable MD013 -->
 
 ```sh
-export VERSION=4.1.0-rc.1 # this is the singularity version, change as you need
+export VERSION=4.1.0  # this is the singularity version, change as you need
 
 # Fetch the source
 wget https://github.com/sylabs/singularity/releases/download/v${VERSION}/singularity-ce-${VERSION}.tar.gz