release: 0.3.4, and name the implementations that follow openkal 0.7.0

The declarations pointed at versions published before openkal 0.7.0, and
under caret rules those older versions still satisfy the requirement. A
project resolving this package could therefore be handed an
implementation declaring openkal 0.6.0 alongside a specification at
0.7.0, and 0.6.0 and 0.7.0 do not resolve together below 1.0.

Naming the new versions is what makes the resolver reach the
implementations this release was tested against.

Author: Sunrisepeak

mcpp.toml

@@ -1,7 +1,7 @@
 [package]
 namespace   = "mcpplibs"
 name        = "openkal-musl"
-version     = "0.3.3"
+version     = "0.3.4"
 description = "musl 1.2.5 redirected onto openkal: one C library, ported once, above every implementation of the specification rather than above one kernel."
 license     = "Apache-2.0"
 
@@ -30,10 +30,10 @@ openkal = "0.7.0"
 #
 # The consequence for a program is that it names this package and nothing else.
 [target.'cfg(os = "linux")'.dependencies]
-openkal-linux = { version = "0.5.3", features = ["standalone"] }
+openkal-linux = { version = "0.5.4", features = ["standalone"] }
 
 [target.'cfg(os = "macos")'.dependencies]
-openkal-macos = { version = "0.3.3", features = ["standalone"] }
+openkal-macos = { version = "0.3.4", features = ["standalone"] }
 
 # ⚠️ FIRST STEP TOWARD A BARE MACHINE, AND NOT THE WHOLE OF IT.
 #
@@ -44,7 +44,7 @@ openkal-macos = { version = "0.3.3", features = ["standalone"] }
 # runtime that receives control, and a C library configured for an environment
 # with no process to exit from. So this declares the implementation and stops.
 [target.'cfg(os = "none")'.dependencies]
-openkal-opensbi = { version = "0.1.2", features = ["standalone"] }
+openkal-opensbi = { version = "0.1.5", features = ["standalone"] }
 
 # ⭐ WHICH OPENKAL INTERFACES THE IMPLEMENTATION BENEATH IS EXPECTED TO PROVIDE.
 #
@@ -69,7 +69,7 @@ openkal-opensbi = { version = "0.1.2", features = ["standalone"] }
 defines = ["OKM_HAS_FS=0", "OKM_HAS_PROCESS=0", "OKM_HAS_TASK=0"]
 
 [target.'cfg(windows)'.dependencies]
-openkal-windows = { version = "0.1.3", features = ["standalone"] }
+openkal-windows = { version = "0.1.5", features = ["standalone"] }
 
 # The feature macros musl's own build establishes.
 #