chore: Prepare v0.13.1 release

[RuoqingHe]

Summary of the PR

Release v0.13.1 to consume kernel commandline parameter validation fix
and image header for ARM and RISC-V visibility change.

Requirements

Before submitting your PR, please make sure you addressed the following
requirements:

• All commits in this PR have Signed-Off-By trailers (with
  git commit -s), and the commit message has max 60 characters for the
  summary and max 75 characters for each description line.
• All added/changed functionality has a corresponding unit/integration
  test.
• All added/changed public-facing functionality has entries in the "Upcoming
  Release" section of CHANGELOG.md (if no such section exists, please create one).
• Any newly added unsafe code is properly documented.

[roypat]

I think because of the validation fix, this needs to be 0.14.0, because its a change in behavior. Since linux-loader is a "leaf" crate in the rust-vmm ecosystem, that should be fine though tbh.

Do you need the new version urgently though? I think we'll have a new vm-memory release soon (next week, fingers crossed), so am wondering if we could wait instead until linux-loader can pick that up, instead of doing two releases in quick succession here.

[RuoqingHe]

I think because of the validation fix, this needs to be 0.14.0, because its a change in behavior. Since linux-loader is a "leaf" crate in the rust-vmm ecosystem, that should be fine though tbh.

Do you need the new version urgently though? I think we'll have a new vm-memory release soon (next week, fingers crossed), so am wondering if we could wait instead until linux-loader can pick that up, instead of doing two releases in quick succession here.

Let's wait vm-memory then 😉

[roypat]

I think because of the validation fix, this needs to be 0.14.0, because its a change in behavior. Since linux-loader is a "leaf" crate in the rust-vmm ecosystem, that should be fine though tbh.
Do you need the new version urgently though? I think we'll have a new vm-memory release soon (next week, fingers crossed), so am wondering if we could wait instead until linux-loader can pick that up, instead of doing two releases in quick succession here.

Let's wait vm-memory then 😉

I think we can do this release now!