<feed xmlns='http://www.w3.org/2005/Atom'>
<title>mirrors/arti.git/maint/semver-checks, branch arti-v1.2.7</title>
<subtitle>mirror of https://gitlab.torproject.org/tpo/core/arti
</subtitle>
<id>http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.2.7</id>
<link rel='self' href='http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.2.7'/>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/'/>
<updated>2024-02-05T19:01:36Z</updated>
<entry>
<title>maint/semver-checks: allow overriding CARGO</title>
<updated>2024-02-05T19:01:36Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2024-02-05T13:59:58Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=83c29b0d805f908e98ed1742491f3145f547fb2e'/>
<id>urn:sha1:83c29b0d805f908e98ed1742491f3145f547fb2e</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Replace our old complex semver-checks script.</title>
<updated>2023-06-29T17:22:25Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2023-06-29T13:14:07Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=e98f79617a4e48048e6c5c9e0be570933352c756'/>
<id>urn:sha1:e98f79617a4e48048e6c5c9e0be570933352c756</id>
<content type='text'>
Now with cargo semver-checks &gt;= 0.22.1, we no longer need to
jump through hoops in order to only look at the `full` features.
This, combined with our work on `fixup-features`, lets us be
confident that we're only looking at semver breakage in experimental
code.
</content>
</entry>
<entry>
<title>New script to run cargo-semver-checks with appropriate options.</title>
<updated>2023-05-31T14:04:29Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2023-05-31T13:52:42Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=1f4cd3f38959958be30a3c163f7ee52a9fec8453'/>
<id>urn:sha1:1f4cd3f38959958be30a3c163f7ee52a9fec8453</id>
<content type='text'>
The options are rather complicated; because we do not want to
subject our experimental features to semver, we need to run generate
JSON rustdoc on our own and then pass that JSON to
cargo-semver-checks.  This in turn requires us to use the same
options that cargo-semver-checks uses, including "RUSTC_BOOTSTRAP".

I've left some TODOs here in places where we will likely want to
improve our code in the future.

See #711.
</content>
</entry>
</feed>
