<feed xmlns='http://www.w3.org/2005/Atom'>
<title>mirrors/arti.git/crates/tor-hsrproxy, branch arti-v1.1.11</title>
<subtitle>mirror of https://gitlab.torproject.org/tpo/core/arti
</subtitle>
<id>http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.1.11</id>
<link rel='self' href='http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.1.11'/>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/'/>
<updated>2023-12-04T16:35:23Z</updated>
<entry>
<title>Bump minor versions in preparation for release</title>
<updated>2023-12-04T16:35:23Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2023-12-04T16:22:58Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=fba95e4b4708929ed09554632acd2e9f15e3c086'/>
<id>urn:sha1:fba95e4b4708929ed09554632acd2e9f15e3c086</id>
<content type='text'>
This crate is new, and gets a bump to 0.1.0.

tor-log-ratelim

This crate had a breaking change:

tor-persist

tor-llcrypto had a breaking change.  These crates _are_
tor-llcrypto, or (transitively) depend on it. I am assuming that
they all re-expose something from it in a way that matters:

tor-llcrypto
tor-bytes
tor-hscrypto
tor-socksproto
tor-checkable
tor-cert
tor-linkspec
tor-cell
tor-proto
tor-netdoc
tor-consdiff
tor-netdir
tor-chanmgr
tor-ptmgr
tor-guardmgr
tor-circmgr
tor-dirclient
tor-dirmgr
tor-keymgr
tor-hsclient
tor-hsservice
tor-hsrproxy
arti-client
arti-rpcserver
arti-hyper
</content>
</entry>
<entry>
<title>Bump patchlevel versions in preparation for release</title>
<updated>2023-12-04T16:33:36Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2023-12-04T16:22:58Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=606905bd1fa3307a77a02463fa863f4c2b7cb890'/>
<id>urn:sha1:606905bd1fa3307a77a02463fa863f4c2b7cb890</id>
<content type='text'>
These crates had backward-compatible changes, and get a patchlevel
bump only:

fs-mistrust
tor-error
tor-config
tor-rtcompat
tor-rtmock

This crate exposes no non-CLI APIs, and gets a patchlevel bump only:

arti
</content>
</entry>
<entry>
<title>Merge branch 'msrv-bump-1.70' into 'main'</title>
<updated>2023-11-30T14:40:45Z</updated>
<author>
<name>Ian Jackson</name>
<email>iwj@torproject.org</email>
</author>
<published>2023-11-30T14:40:45Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=7b23daffb5c2e903881c9b2d64a0bccc7b3f698e'/>
<id>urn:sha1:7b23daffb5c2e903881c9b2d64a0bccc7b3f698e</id>
<content type='text'>
Increase our MSRV to 1.70

See merge request tpo/core/arti!1773</content>
</entry>
<entry>
<title>hsrproxy: Allow ports to be specified as integers</title>
<updated>2023-11-30T00:54:53Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2023-11-28T14:53:29Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=095fb2aae33197b3f2ea711630c65dcf3595acb3'/>
<id>urn:sha1:095fb2aae33197b3f2ea711630c65dcf3595acb3</id>
<content type='text'>
Previously, we required the user to specify a pattern matching a
single port as `"80"`, with quotes.  Now we allow the user to omit
the quotes.
</content>
</entry>
<entry>
<title>Revert "hsrproxy: Temporarily change the format of ProxyRule."</title>
<updated>2023-11-30T00:54:41Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2023-11-28T14:07:57Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=5254b808b98a5c6ec2f75ef5a505db3315fbbd6c'/>
<id>urn:sha1:5254b808b98a5c6ec2f75ef5a505db3315fbbd6c</id>
<content type='text'>
This reverts commit 21605d2c9e601c3a5099bfd8d8c887cbb3b36c0a.

We're doing this because we wanted the configuration of proxy rules
to be a 2-tuple, as in `[ "22", "127.0.0.1:22" ]`.  But `config`
couldn't handle that before, so we temporarily changed it to
a string, as in "22 =&gt; 127.0.0.1:22".

Closes #1058.
</content>
</entry>
<entry>
<title>In every crate, change rust-version to 1.70.</title>
<updated>2023-11-28T16:35:51Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2023-11-28T16:35:51Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=1b53c4ca3059fc395c98e2e6d0eb3b58f37c8ec1'/>
<id>urn:sha1:1b53c4ca3059fc395c98e2e6d0eb3b58f37c8ec1</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Merge remote-tracking branch 'public/hs_begin'</title>
<updated>2023-11-16T15:46:49Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2023-11-16T15:46:49Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=e54893693021ab443fcf462365d3ba8e9b8644c6'/>
<id>urn:sha1:e54893693021ab443fcf462365d3ba8e9b8644c6</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Remove semver.md files from arti 1.1.10</title>
<updated>2023-10-31T16:11:03Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2023-10-31T16:11:03Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=c4a2d08c3104f974676df6e3b984dc6f3945654f'/>
<id>urn:sha1:c4a2d08c3104f974676df6e3b984dc6f3945654f</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Remove "publish=false" from tor-hsrproxy.</title>
<updated>2023-10-31T16:00:32Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2023-10-31T16:00:32Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=3d8ac346c6044d9455944aa7a3c10fcc0baf814e'/>
<id>urn:sha1:3d8ac346c6044d9455944aa7a3c10fcc0baf814e</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Patch version bumps in crates without breaking changes</title>
<updated>2023-10-31T13:12:35Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2023-10-31T13:00:42Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=537d98a12eedf5604fe28183ec603dd3609bb070'/>
<id>urn:sha1:537d98a12eedf5604fe28183ec603dd3609bb070</id>
<content type='text'>
```
These crates have new APIs:

tor-async-utils   ADDED
tor-config        ADDED
tor-hscrypto      ADDED
tor-netdoc        ADDED, plus BREAKING-experimental.

These crates have patch-level changes only:

tor-netdir        (bugfix only). (re-exposes netdoc)
arti-rpcserver    (tweaks only, uses nothing that broke.)
arti              1.1.10, no stable public APIs.

```
</content>
</entry>
</feed>
