<feed xmlns='http://www.w3.org/2005/Atom'>
<title>mirrors/arti.git/crates/arti-client/semver.md, branch arti-v2.4.0</title>
<subtitle>mirror of https://gitlab.torproject.org/tpo/core/arti
</subtitle>
<id>http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v2.4.0</id>
<link rel='self' href='http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v2.4.0'/>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/'/>
<updated>2026-05-26T16:57:05Z</updated>
<entry>
<title>client: Factor out the "running a client" code into an inner typestate</title>
<updated>2026-05-26T16:57:05Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2026-05-20T15:47:40Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=eba1ad0e0ed1dfc4b793ac5646d147aeabe8bc6d'/>
<id>urn:sha1:eba1ad0e0ed1dfc4b793ac5646d147aeabe8bc6d</id>
<content type='text'>
We'll use this to distinguish "not running" from "running",
in order to make it easier to be sure that non-bootstrapping clients
will definitely not try to connect to the network.
</content>
</entry>
<entry>
<title>Remove `use_obsolete_software`.</title>
<updated>2026-05-14T15:34:15Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2026-05-14T15:34:15Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=cc854340a9d27f60031b0e7bc1c81752e4ba905e'/>
<id>urn:sha1:cc854340a9d27f60031b0e7bc1c81752e4ba905e</id>
<content type='text'>
Discussion on #1960 suggests that this option is not a good idea:
it encourages developers to work around deliberate signals that the
software they're shipping won't work on the network.

Closes #1960.
</content>
</entry>
<entry>
<title>client: revise StreamPrefs methods</title>
<updated>2026-05-13T20:44:51Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2026-05-13T14:06:23Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=a3a033c20820b50e591de9e98566e33ab7399680'/>
<id>urn:sha1:a3a033c20820b50e591de9e98566e33ab7399680</id>
<content type='text'>
The `set_stream_prefs` method was the only one that took a TorClient
as `&amp;mut self`.  But we only expose Arc&lt;TorClient&lt;R&gt;&gt;, that isn't a
reasonable API.

The `clone_with_prefs` method has been renamed, since it no longer
"clones" anything meaningfully.
</content>
</entry>
<entry>
<title>Make TorClient no longer implement Clone.</title>
<updated>2026-05-13T20:44:51Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2026-05-13T14:01:49Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=9872549ad394dcb4307b8aa5d3f82b73c5d37df8'/>
<id>urn:sha1:9872549ad394dcb4307b8aa5d3f82b73c5d37df8</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Make all TorClient constructors wrap the TorClient in an Arc.</title>
<updated>2026-05-13T20:44:51Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2026-05-13T13:33:59Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=3cb880f30a37d8757534b9832fccbf00482508a8'/>
<id>urn:sha1:3cb880f30a37d8757534b9832fccbf00482508a8</id>
<content type='text'>
This is part of rationalizing the structure of TorClient so we can
refactor startup logic, and so that RPC code can reason about object
identity.  See #2469.
</content>
</entry>
<entry>
<title>Remove semver.md files post-release</title>
<updated>2025-12-02T13:27:53Z</updated>
<author>
<name>Gabriela Moldovan</name>
<email>gabi@torproject.org</email>
</author>
<published>2025-12-02T13:27:53Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=e8b06787cfa55ca53b7e86566914652db14c2d05'/>
<id>urn:sha1:e8b06787cfa55ca53b7e86566914652db14c2d05</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Fix semver files.</title>
<updated>2025-11-03T23:06:41Z</updated>
<author>
<name>Wesley Aptekar-Cassels</name>
<email>me@wesleyac.com</email>
</author>
<published>2025-11-03T23:06:41Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=9ce270fcce4e138ab46cffee2f88750b557f61be'/>
<id>urn:sha1:9ce270fcce4e138ab46cffee2f88750b557f61be</id>
<content type='text'>
We don't need to modify semver files for newly added methods.
</content>
</entry>
<entry>
<title>arti(-client|-ureq)/tor-hsservice: semver files v2</title>
<updated>2025-10-21T17:53:46Z</updated>
<author>
<name>hashcatHitman</name>
<email>3924-hashcatHitman@gitlab.torproject.org</email>
</author>
<published>2025-10-21T17:53:46Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=322008a8378406bb3ae48c1e36096bb780825877'/>
<id>urn:sha1:322008a8378406bb3ae48c1e36096bb780825877</id>
<content type='text'>
Combined with the previous commit, this completes my second attempt at
correctly handling the semver files.

tor-hssservice:
I removed the extra bit at the end of the first line explaining the
semantics of the new return type, since the important part is really
just the fact that the return type changed. The semantics are documented
in the methods themselves.

arti-client:
Same as above, but I also removed the `client` module prefix since the
`client` module isn't actually public, so to external crate users the
broken type is directly in the crate root.

Removed old "used in the public API of this crate" line.

Added lines referring to the 2 breaking changes we re-export from
tor-hsservice.

arti-ureq:
Removed old "used in the public API of this crate" line.

Added lines referencing every breaking change in arti-client. This MIGHT
be wrong, but I think this is correct because we re-export arti-client
as a whole.

Signed-off-by: hashcatHitman &lt;3924-hashcatHitman@gitlab.torproject.org&gt;
</content>
</entry>
<entry>
<title>arti(-client|-ureq|-rpcserver): semver files</title>
<updated>2025-10-16T22:48:46Z</updated>
<author>
<name>hashcatHitman</name>
<email>3924-hashcatHitman@gitlab.torproject.org</email>
</author>
<published>2025-10-05T06:25:45Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=a529702bf423220c077123b641a433d8a6d44acd'/>
<id>urn:sha1:a529702bf423220c077123b641a433d8a6d44acd</id>
<content type='text'>
If I understand correctly, the breaking changes propagate like this.

Signed-off-by: hashcatHitman &lt;3924-hashcatHitman@gitlab.torproject.org&gt;
</content>
</entry>
<entry>
<title>arti-client/tor-hsservice: semver files</title>
<updated>2025-10-16T22:48:46Z</updated>
<author>
<name>hashcatHitman</name>
<email>3924-hashcatHitman@gitlab.torproject.org</email>
</author>
<published>2025-10-05T03:08:38Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=1f6f47e5474f618787e9e780203a29f2fbff48b6'/>
<id>urn:sha1:1f6f47e5474f618787e9e780203a29f2fbff48b6</id>
<content type='text'>
Might be too verbose... unsure.

Signed-off-by: hashcatHitman &lt;3924-hashcatHitman@gitlab.torproject.org&gt;
</content>
</entry>
</feed>
