<?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 contributing-ci.md</title>
    <description></description>
    <language>en</language>
    <copyright>Copyright 2015</copyright>
    <generator>Java</generator><item>
        <title>a80da753 - Build &quot;min&quot; artifacts on CI (#7315)</title>
        <link>http://172.16.0.5:8080/history/wasmtime-44.0.1/docs/contributing-ci.md#a80da753</link>
        <description>Build &quot;min&quot; artifacts on CI (#7315)* riscv64: Extend distance trampolines can jumpUse a PIC-friendly set of instructions to enable destination of thetrampoline to be more than 4k away from the tail call site of thetrampoline itself.* Build &quot;min&quot; artifacts on CIThis commit updates the binary artifacts produced by CI to include &quot;min&quot;builds where all default features are disabled. Additionally all thestops are pulled in terms of build flags, nightly versions, etc, to geta build that is as small as possible without actual source code changes.This effectively codifies the instructions in #7282 into an easilydownloadable artifact.No new tarballs are created for github releases but instead tarballsthat previously had a `wasmtime` executable for example now have a`wasmtime-min` executable. Furthermore the C API which previously had`libwasmtime.so` for example now has `libwasmtime-min.so`. The intentionis that the minimum-size artifacts are handy for determining a roughsize of Wasmtime but they&apos;re not so important that it seems worthwhileto dedicate entire release entries for.CI is refactored to support these minimum builds with separate builders.This means that a single tarball produced as a final result is actuallytwo separate tarballs merged together, one for the normal build we dotoday plus a new &quot;min&quot; tarball produced on the new &quot;min&quot; builders.Various scripts and CI organization has been adjusted accordingly.While here I went ahead and enabled `panic=abort` and debuginfostripping in our current release artifacts. While this doesn&apos;t affect awhole lot it&apos;s less to upload to GitHub Actions all the time.* Fix Windows unzip

            List of files:
            /wasmtime-44.0.1/docs/contributing-ci.md</description>
        <pubDate>Mon, 23 Oct 2023 16:38:49 +0000</pubDate>
        <dc:creator>Alex Crichton &lt;alex@alexcrichton.com&gt;</dc:creator>
    </item>
<item>
        <title>c43d00fa - doc: link to where oss-fuzz issues are recorded (#2780)</title>
        <link>http://172.16.0.5:8080/history/wasmtime-44.0.1/docs/contributing-ci.md#c43d00fa</link>
        <description>doc: link to where oss-fuzz issues are recorded (#2780)

            List of files:
            /wasmtime-44.0.1/docs/contributing-ci.md</description>
        <pubDate>Fri, 26 Mar 2021 18:01:13 +0000</pubDate>
        <dc:creator>Andrew Brown &lt;andrew.brown@intel.com&gt;</dc:creator>
    </item>
<item>
        <title>a92a31d8 - Rename the `master` branch to `main` (#1924)</title>
        <link>http://172.16.0.5:8080/history/wasmtime-44.0.1/docs/contributing-ci.md#a92a31d8</link>
        <description>Rename the `master` branch to `main` (#1924)* This PR is against a branch called `main`* Internally all docs/CI/etc is updated* The default branch of the repo is now `main`* All active PRs have been updated to retarget `main`Closes #1914

            List of files:
            /wasmtime-44.0.1/docs/contributing-ci.md</description>
        <pubDate>Thu, 25 Jun 2020 19:03:21 +0000</pubDate>
        <dc:creator>Alex Crichton &lt;alex@alexcrichton.com&gt;</dc:creator>
    </item>
<item>
        <title>7e09c4c9 - Fill out CI docs in the contributing section of the book (#1239)</title>
        <link>http://172.16.0.5:8080/history/wasmtime-44.0.1/docs/contributing-ci.md#7e09c4c9</link>
        <description>Fill out CI docs in the contributing section of the book (#1239)* Fill out CI docs in the contributing section of the bookFigured it&apos;d be good to document at least at a high level what in theworld is happening on all our PR runs.* Tweak fuzz test comments

            List of files:
            /wasmtime-44.0.1/docs/contributing-ci.md</description>
        <pubDate>Fri, 06 Mar 2020 19:13:52 +0000</pubDate>
        <dc:creator>Alex Crichton &lt;alex@alexcrichton.com&gt;</dc:creator>
    </item>
<item>
        <title>bf526b62 - Add book documentation skeleton and auto-publish from CI (#435)</title>
        <link>http://172.16.0.5:8080/history/wasmtime-44.0.1/docs/contributing-ci.md#bf526b62</link>
        <description>Add book documentation skeleton and auto-publish from CI (#435)This commit adds the skeleton of a new set of documentation for`wasmtime` in the existing `docs` directory. This documentation isorganized and compiled with [mdbook] which the Rust project uses formost of its own documentation as well. At a previous meeting webrainstormed a rough skeleton of what the documentation in this bookwould look like, and I&apos;ve transcribed that here for an example of howthis is rendered and how it can be laid out. No actual documentation iswritten yet.This commit also additionally adds necessary support to auto-publishboth this book documentation and API documentation every time a commitis pushed to the `master` branch. All HTML will be automatically pushedto the `gh-pages` branch so long as the CI passes, and this should getdeployed to https://cranestation.github.io/wasmtime.I&apos;ve done a few dry-runs and I think this&apos;ll all work, but we&apos;ll likelytweak a few things here and there after running this through CI to makesure everything looks just as we&apos;d like. My hope though is that afterthis lands we can start actually filling out all the documentation andbeing able to review it as well.[mdbook]: https://crates.io/crates/mdbook

            List of files:
            /wasmtime-44.0.1/docs/contributing-ci.md</description>
        <pubDate>Tue, 29 Oct 2019 14:55:51 +0000</pubDate>
        <dc:creator>Alex Crichton &lt;alex@alexcrichton.com&gt;</dc:creator>
    </item>
</channel>
</rss>
