From 4da07badb1eee5d4f2d5a1faedb76a5f062c5e61 Mon Sep 17 00:00:00 2001 From: Joshua Liebow-Feeser Date: Thu, 3 Oct 2024 12:20:19 -0700 Subject: [PATCH] [POLICIES] Update MSRV policy: multiple crate deps Previously, we incorrectly stated that syn was the only dependency of zerocopy-derive. --- POLICIES.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/POLICIES.md b/POLICIES.md index 474e92277f..a05b3c35c7 100644 --- a/POLICIES.md +++ b/POLICIES.md @@ -100,10 +100,10 @@ will only increase our MSRV during semver-breaking version changes (e.g., 0.1 -> 0.2, 1.0 -> 2.0, etc). For zerocopy with the `derive` feature enabled, and for the zerocopy-derive -crate, we inherit the MSRV of our sole external dependency, syn. As of this -writing (2024-07-02), syn does *not* consider MSRV increases to be -semver-breaking changes. Thus, using the `derive` feature may result in the -effective MSRV increasing within a semver version train. +crate, we inherit the maximum MSRV any of our dependencies. As of this writing +(2024-10-03), at least one dependency (syn) does *not* consider MSRV increases +to be semver-breaking changes. Thus, using the `derive` feature may result in +the effective MSRV increasing within a semver version train. ## Yanking