<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="/rss.xsl.xml"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
    <title>Changes in cache_write_default_config.rs</title>
    <description></description>
    <language>en</language>
    <copyright>Copyright 2015</copyright>
    <generator>Java</generator><item>
        <title>4c8edb95 - More clearly flag internal crates as such (#10963)</title>
        <link>http://172.16.0.5:8080/history/wasmtime-44.0.1/crates/cache/tests/cache_write_default_config.rs#4c8edb95</link>
        <description>More clearly flag internal crates as such (#10963)* More clearly flag internal crates as suchThis commit is an attempt to more clearly flag internal crates in thisproject as internal and not intended for external use. Specifically:* Many crates are renamed from `wasmtime-foo` to  `wasmtime-internal-foo`.* All of these crates now have `INTERNAL: ...` in their crates.io  description.* All of these crates now have a warning at the top of their  documentation discouraging use.This change is a result of rustsec/advisory-db#1999 where the goal is tobe crystal clear from a project perspective that usage of these cratesare highly discouraged and not supported. We&apos;ll still probably get suchadvisories but we won&apos;t be considering them CVEs from the project itselfdue to the internal nature of these crates and the discouragingwarnings.Some concrete changes used here are:* Inter-crate dependencies still use `wasmtime_foo` for naming and do  so with Cargo&apos;s package-renaming features.* Crate renames are specified at the workspace level so the rename is  only in one locations and all other inherit it.* Contribution documentation now has some brief guidelines about crate  organization.* Update vet config* Update checks for wasmtime-fiberprtest:full* Update publish script* Another fiber rename* Fix some doc tests

            List of files:
            /wasmtime-44.0.1/crates/cache/tests/cache_write_default_config.rs</description>
        <pubDate>Fri, 06 Jun 2025 21:13:36 +0000</pubDate>
        <dc:creator>Alex Crichton &lt;alex@alexcrichton.com&gt;</dc:creator>
    </item>
<item>
        <title>08f9eb17 - Making caching support optional in Wasmtime (#2119)</title>
        <link>http://172.16.0.5:8080/history/wasmtime-44.0.1/crates/cache/tests/cache_write_default_config.rs#08f9eb17</link>
        <description>Making caching support optional in Wasmtime (#2119)This commit moves all of the caching support that currently lives in`wasmtime-environ` into a `wasmtime-cache` crate and makes it optional. Thegoal here is to slim down the `wasmtime-environ` crate and clearly separateboundaries where caching is a standalone and optional feature, not intertwinedwith other crates.

            List of files:
            /wasmtime-44.0.1/crates/cache/tests/cache_write_default_config.rs</description>
        <pubDate>Fri, 07 Aug 2020 20:42:40 +0000</pubDate>
        <dc:creator>Alex Crichton &lt;alex@alexcrichton.com&gt;</dc:creator>
    </item>
</channel>
</rss>
