mirror of
https://github.com/tahoe-lafs/tahoe-lafs.git
synced 2025-02-25 19:21:36 +00:00
Merge pull request #1353 from meejah/4076.prepare-release-1.19.0
4076: prepare release 1.19.0
This commit is contained in:
meejah
GitHub
commit
19538e31f5
@ -147,7 +147,7 @@ they will need to evaluate which contributors' signatures they trust.
|
|||||||
|
|
||||||
- when satisfied, sign the tarballs:
|
- when satisfied, sign the tarballs:
|
||||||
|
|
||||||
- gpg --pinentry=loopback --armor --detach-sign dist/tahoe_lafs-1.16.0rc0-py2.py3-none-any.whl
|
- gpg --pinentry=loopback --armor -u 0xE34E62D06D0E69CFCA4179FFBDE0D31D68666A7A --detach-sign dist/tahoe_lafs-1.16.0rc0-py2.py3-none-any.whl
|
||||||
- gpg --pinentry=loopback --armor --detach-sign dist/tahoe_lafs-1.16.0rc0.tar.gz
|
- gpg --pinentry=loopback --armor --detach-sign dist/tahoe_lafs-1.16.0rc0.tar.gz
|
||||||
|
|
||||||
|
|
||||||
@ -197,13 +197,15 @@ Push the signed tag to the main repository:
|
|||||||
For the actual release, the tarball and signature files need to be
|
For the actual release, the tarball and signature files need to be
|
||||||
uploaded to PyPI as well.
|
uploaded to PyPI as well.
|
||||||
|
|
||||||
- how to do this?
|
- ls dist/*1.19.0*
|
||||||
- (original guide says only `twine upload dist/*`)
|
- twine upload --username __token__ --password `cat SECRET-pypi-tahoe-publish-token` dist/*1.19.0*
|
||||||
- the following developers have access to do this:
|
|
||||||
|
The following developers have access to do this:
|
||||||
|
|
||||||
- warner
|
- warner
|
||||||
|
- meejah
|
||||||
- exarkun (partial?)
|
- exarkun (partial?)
|
||||||
- meejah (partial?)
|
|
||||||
|
|
||||||
Announcing the Release Candidate
|
Announcing the Release Candidate
|
||||||
````````````````````````````````
|
````````````````````````````````
|
||||||
|
|||||||
@ -1 +0,0 @@
|
|||||||
Tahoe-LAFS now includes a new "Grid Manager" specification and implementation adding more options to control which storage servers a client will use for uploads.
|
|
||||||
@ -1 +0,0 @@
|
|||||||
Added support for Python 3.12, and work with Eliot 1.15
|
|
||||||
@ -1,4 +0,0 @@
|
|||||||
Provide better feedback from plugin configuration errors
|
|
||||||
|
|
||||||
Local errors now print a useful message and exit.
|
|
||||||
Announcements that only contain invalid / unusable plugins now show a message in the Welcome page.
|
|
||||||
@ -1 +0,0 @@
|
|||||||
The new HTTPS-based storage server is now enabled transparently on the same port as the Foolscap server. This will not have any user-facing impact until the HTTPS storage protocol is supported in clients as well.
|
|
||||||
@ -1,5 +0,0 @@
|
|||||||
`tahoe run ...` will now exit when its stdin is closed.
|
|
||||||
|
|
||||||
This facilitates subprocess management, specifically cleanup.
|
|
||||||
When a parent process is running tahoe and exits without time to do "proper" cleanup at least the stdin descriptor will be closed.
|
|
||||||
Subsequently "tahoe run" notices this and exits.
|
|
||||||
@ -1 +0,0 @@
|
|||||||
Several minor errors in the Great Black Swamp proposed specification document have been fixed.
|
|
||||||
@ -1 +0,0 @@
|
|||||||
Work with (and require) newer versions of pycddl.
|
|
||||||
@ -1 +0,0 @@
|
|||||||
Uploading immutables will now better use available bandwidth, which should allow for faster uploads in many cases.
|
|
||||||
@ -1 +0,0 @@
|
|||||||
|
|
||||||
@ -1 +0,0 @@
|
|||||||
Downloads of large immutables should now finish much faster.
|
|
||||||
@ -1 +0,0 @@
|
|||||||
The integration test suite now includes a set of capability test vectors (``integration/vectors/test_vectors.yaml``) which can be used to verify compatibility between Tahoe-LAFS and other implementations.
|
|
||||||
@ -1 +0,0 @@
|
|||||||
Mutable objects can now be created with a pre-determined "signature key" using the ``tahoe put`` CLI or the HTTP API. This enables deterministic creation of mutable capabilities. This feature must be used with care to preserve the normal security and reliability properties.
|
|
||||||
@ -1 +0,0 @@
|
|||||||
Python 3.7 is no longer supported, and Debian 10 and Ubuntu 18.04 are no longer tested.
|
|
||||||
@ -1 +0,0 @@
|
|||||||
Fix incompatibility with transitive dependency charset_normalizer >= 3 when using PyInstaller.
|
|
||||||
@ -1 +0,0 @@
|
|||||||
Changes made to mypy.ini to make mypy more 'strict' and prevent future regressions.
|
|
||||||
@ -1 +0,0 @@
|
|||||||
Fixes truthy conditional in status.py
|
|
||||||
@ -1 +0,0 @@
|
|||||||
Fixes variable name same as built-in type.
|
|
||||||
@ -1 +0,0 @@
|
|||||||
Added support for Python 3.11.
|
|
||||||
@ -1 +0,0 @@
|
|||||||
tenacity is no longer a dependency.
|
|
||||||
@ -1 +0,0 @@
|
|||||||
Tahoe-LAFS is incompatible with cryptography >= 40 and now declares a requirement on an older version.
|
|
||||||
@ -1 +0,0 @@
|
|||||||
A bug where Introducer nodes configured to listen on Tor or I2P would not actually do so has been fixed.
|
|
||||||
@ -1 +0,0 @@
|
|||||||
|
|
||||||
@ -1,2 +0,0 @@
|
|||||||
The (still off-by-default) HTTP storage client will now use Tor when Tor-based client-side anonymity was requested.
|
|
||||||
Previously it would use normal TCP connections and not be anonymous.
|
|
||||||
@ -1 +0,0 @@
|
|||||||
tahoe run now accepts --allow-stdin-close to mean "keep running if stdin closes"
|
|
||||||
@ -1 +0,0 @@
|
|||||||
Document the ``force_foolscap`` configuration options for ``[storage]`` and ``[client]``.
|
|
||||||
@ -1 +0,0 @@
|
|||||||
The storage server and client now support a new, HTTPS-based protocol.
|
|
||||||
Some files were not shown because too many files have changed in this diff Show More
Loading…
x
Reference in New Issue
Block a user