All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog and this project adheres to Semantic Versioning.
- Added support of Ubuntu Noble (24.04).
- Added
rws_files
tool.
- Changed deployment mode back to
buildpack
.
- Fixed an issue with the
Werkzeug
dependency.
- Added support of Fedora 39.
- Added support of AlmaLinux 8, 9.
- Added support of Astra Linux 1.7.
- Added support of Debian Bookworm and Fedora 37, 38.
- Added support of static repositories.
- Added
Dockerfile
to build Docker images. - Added
docker-compose.yml
for setting up a test stand.
- Fixed broken paths to images in
templates/index.html
.
- Now the
.ddeb
files are simply skipped and all other files in the package continue to be processed. Previously, this caused fail package uploading.
- Changed the version of dokku deploy action to patched one which supports deploying to multiple environments.
- Updated checkout action to a newer version.
- Updated required version of
mkrepo
to 1.0.2. The new release ofmkrepo
contains several improvements and bug fixes. The most significant of them are auto-installation of required package dependencies, fixing Python 3.6 compatibility, and bumpingboto3
version to 1.17.5.
- Updated required version of
mkrepo
to 1.0.0. The new release ofmkrepo
contains several improvements and bug fixes for handling rpm repository metainformation. The most significant of these is the addition of the ability to remove information about a removed package.
- Added support of RedOS 7.3.
- Updated required version of
mkrepo
to 0.1.10. The new version ofmkrepo
contains major bug fixes related to the processing of rpm repository metadata.
- Added the
zstd
deb package as a dependency that is needed for themkrepo
library. The dependency is stored in the special filesapt-packages
andAptfile
that can be read by Dokku and Heroku services correspondingly to install required packages while RWS deployment.
- Updated required version of "mkrepo" to 0.1.7. The new version of mkrepo fixes the parsing of signed dsc files and the processing of rpm repository metainformation.
- Displaying the contents of deb/rpm repositories located on S3 via HTTP.
- Uploading a package (creating/updating the metainformation of the related repository) to the deb/rpm repository located on S3, via HTTP with authentication.
- Multi-threaded synchronization of all repositories under RWS control, at the start of the service.
- Force synchronization mode, when enabled RWS ignores malformed packages
during repository synchronization (information about malformed packages will
be saved in the
malformed_list.txt
file). - The ability to set different GPG keys to sign `tarantool' and module repositories.
- The `anchors' mechanism that allows to upload a package to multiple repositories using a single URL.
- All necessary files to start the service on the heroku/dokku platforms.
- Utility for backup repositories to/from S3.
- GHA to automatically deploy the service to the dokku platform.