Browse Source

multiboot2: prepare v0.15 release

Philipp Schuster 2 years ago
parent
commit
67fae994c0
2 changed files with 6 additions and 6 deletions
  1. 1 1
      multiboot2/Cargo.toml
  2. 5 5
      multiboot2/Changelog.md

+ 1 - 1
multiboot2/Cargo.toml

@@ -6,7 +6,7 @@ Multiboot2-compliant bootloaders, like GRUB. It supports all tags from the speci
 including full support for the sections of ELF-64. This library is `no_std` and can be
 used in a Multiboot2-kernel.
 """
-version = "0.14.2"
+version = "0.15.0"
 authors = [
     "Philipp Oppermann <dev@phil-opp.com>",
     "Calvin Lee <cyrus296@gmail.com>",

+ 5 - 5
multiboot2/Changelog.md

@@ -1,12 +1,14 @@
 # CHANGELOG for crate `multiboot2`
 
-## 0.15.0 (2023-03-XX)
-- MSRV is 1.56.1
+## 0.15.0 (2023-03-17)
+- **BREAKING** MSRV is 1.56.1
 - **BREAKING** fixed lifetime issues: `VBEInfoTag` is no longer `&static`
 - **BREAKING:** `TagType` is now split into `TagTypeId` and `TagType`
   - `TagTypeId` is a binary-compatible form of a Multiboot2 tag id
   - `TagType` is a higher-level abstraction for either specified or custom tags
-      but not ABI compatible.
+     but not ABI compatible.
+  - There exists a seamless integration between `u32`, `TagType`, and
+    `TagTypeId` via `From` and `PartialEq`-implementations.
 - fixed another internal lifetime issue
 - `BootInformation::framebuffer_tag()` now returns
   `Option<Result<FramebufferTag, UnknownFramebufferType>>` instead of
@@ -17,8 +19,6 @@
   work with custom tags. An example is given in the function documentation.
   (check docs.rs). There is also a small unit test that you can use to learn
   from.
-- There exists a seamless integration between `u32`, `TagType`, and `TagTypeId`
-  via `From` and `PartialEq`-implementations.
 
 ## 0.14.2 (2023-03-17)
 - documentation fixes