Releases: Orange-OpenSource/floss-toolbox
Version 2.21.0
What's new
Added
- English template for email text generation about GitHub newcomers
- Bug and feature request templates, and other files for the hygiene of the project
Changed
- [Licenses Inventory] Update to v4.0.6 (#160)
Fixed
- [Diver] Missing execution permission for extract-emails-from-history.sh (#171)
- [Diver] Failed to process repositories at path with whitespaces (#172)
Artifacts
LicensesInventory-tests-assets.zip
To run the tests, you must get the assets attached as artificats to the release you got.
For integration tests, get the real_data folder in the integrationtests folder and move it to the same folder in your project.
For unit tests, get the data folder in the unittests folder and move it to the same folder in your project.
Then you will have to update the configuration values defined in all the config files of the data sets.
Indeed, absolute paths are used, so you must look for any "🥜" and replace by the path fragments leading to the folders.
After that, run the dry-run.sh script to check wether or not some files are missing. All tests must pass.
LicensesInventory-samples-results.zip
Just some samples of dependencies files and outputs.
floss-toolbox.wiki.zip
The clone of the wiki associated to the release.
Version 2.20.0
What's new
Added
- [Diver] List all contributions by contributors (#153)
Fixed
- [Utils] Fix missing import in configuration.py
Artifacts
LicensesInventory-tests-assets.zip
To run the tests, you must get the assets attached as artificats to the release you got.
For integration tests, get the real_data folder in the integrationtests folder and move it to the same folder in your project.
For unit tests, get the data folder in the unittests folder and move it to the same folder in your project.
Then you will have to update the configuration values defined in all the config files of the data sets.
Indeed, absolute paths are used, so you must look for any "🥜" and replace by the path fragments leading to the folders.
After that, run the dry-run.sh script to check wether or not some files are missing. All tests must pass.
LicensesInventory-samples-results.zip
Just some samples of dependencies files and outputs.
floss-toolbox.wiki.zip
The clone of the wiki associated to the release.
Version 2.19.0
What's new
Added
- [Diver] Generate CONTRIBUTORS file using Git history (#148)
- [Utils] Apply SPDX headers to sources with REUSE tool (#146)
- [Diver] Check headers of sources files (#101)
Artifacts
LicensesInventory-tests-assets.zip
To run the tests, you must get the assets attached as artificats to the release you got.
For integration tests, get the real_data folder in the integrationtests folder and move it to the same folder in your project.
For unit tests, get the data folder in the unittests folder and move it to the same folder in your project.
Then you will have to update the configuration values defined in all the config files of the data sets.
Indeed, absolute paths are used, so you must look for any "🥜" and replace by the path fragments leading to the folders.
After that, run the dry-run.sh script to check wether or not some files are missing. All tests must pass.
LicensesInventory-samples-results.zip
Just some samples of dependencies files and outputs.
floss-toolbox.wiki.zip
The clone of the wiki associated to the release.
Version 2.18.0
What's new
Changed
- [Utils] Add licenses names for third-party generator and prompt scripts and new licenses (#141)
- [Utils] Add RSALv2 license in third-party generator scripts (#139)
Artifacts
LicensesInventory-tests-assets.zip
To run the tests, you must get the assets attached as artificats to the release you got.
For integration tests, get the real_data folder in the integrationtests folder and move it to the same folder in your project.
For unit tests, get the data folder in the unittests folder and move it to the same folder in your project.
Then you will have to update the configuration values defined in all the config files of the data sets.
Indeed, absolute paths are used, so you must look for any "🥜" and replace by the path fragments leading to the folders.
After that, run the dry-run.sh script to check wether or not some files are missing. All tests must pass.
LicensesInventory-samples-results.zip
Just some samples of dependencies files and outputs.
floss-toolbox.wiki.zip
The clone of the wiki associated to the release.
Version 2.17.0
What's new
Added
- [Licenses Inventory] Upgrade to version v4.0.4 (#136)
Changed
- [Licenses Inventory] Update dependency pytests to v8.1.1
- [Utils] Default values for THIRD_PARTY generator script, shared configuration with prompt script
Artifacts
LicensesInventory-tests-assets.zip
To run the tests, you must get the assets attached as artificats to the release you got.
For integration tests, get the real_data folder in the integrationtests folder and move it to the same folder in your project.
For unit tests, get the data folder in the unittests folder and move it to the same folder in your project.
Then you will have to update the configuration values defined in all the config files of the data sets.
Indeed, absolute paths are used, so you must look for any "🥜" and replace by the path fragments leading to the folders.
After that, run the dry-run.sh script to check wether or not some files are missing. All tests must pass.
LicensesInventory-samples-results.zip
Just some samples of dependencies files and outputs.
floss-toolbox.wiki.zip
The clone of the wiki associated to the release.
Version 2.16.0
What's new
Added
- [Utils] Add metrics and improve outputs for third-party generator scripts
Changed
- [Licenses Inventory] Update dependency pytests to v7.4.4
- [Licenses Inventory] Update dependency beautifulsoup4 to v4.12.3
- [Licenses Inventory] Improve requirements for Python modules in use (#108)
- [Project] Plug Renovate, Gitleaks (#112)
- [Project] Apply REUSE standards (#114)
- [Project] Improve a bit CHANGELOG by leading scope keyword for each line
Security
- [Licenses Inventory] Bump requests from v2.28.1 to v2.31.0 (#3)
Binairies
For integration tests, you must download the archive assets attached in this current release (called "toolbox.LicensesInventory.tests.integrationtests.data.zip"), extract the ZIP folder you got (called toolbox/LicensesInventory/tests/integrationtests/data) and place the data folder in tests/integrationtests folder. Otherwise tests won't work and dry-run script will fail!
Version 2.15.0
Added
- Project - Generate THIRD-PARTY.md based on user inputs (#119)
Binairies
For integration tests, you must download the archive assets attached in this current release (called "toolbox.LicensesInventory.tests.integrationtests.data.zip"), extract the ZIP folder you got (called toolbox/LicensesInventory/tests/integrationtests/data) and place the data folder in tests/integrationtests folder. Otherwise tests won't work and dry-run script will fail!
Version 2.14.0
Added
- Generate template-based text using variables (#84)
Changed
- Make CHANGELOG more compliant (#103)
Binairies
For integration tests, you must download the archive assets attached in this current release (called "toolbox.LicensesInventory.tests.integrationtests.data.zip"), extract the ZIP folder you got (called toolbox/LicensesInventory/tests/integrationtests/data) and place the data folder in tests/integrationtests folder. Otherwise tests won't work and dry-run script will fail!
Version 2.13.0
Features
- #98 Diver - Compute metrics with in parameter URL to clone repo
Bugs
- #96 Project - Broken links in README
Binairies
For integration tests, you must download the archive assets attached in this current release (called "toolbox.LicensesInventory.tests.integrationtests.data.zip", extract the ZIP folder you got called toolbox/LicensesInventory/tests/integrationtests/data and place the data folder in tests/integrationtests folder. Otherwise tests won't work and dry-run script will fail!
Version 2.12.0
Features
- #28 Diver - Lines of codes and useful metrics
Changes
- #87 Project - Add DCO
- #90 Project - Add security policy file
- #85 Project - Split README files
- #86 Licenses Inventory - Move HTML test files to archives of release
- #93 GitHub - Add in dry-run Gemfiles
Binairies
For integration tests, you must download the archive assets attached in this current release (called "toolbox.LicensesInventory.tests.integrationtests.data.zip", extract the ZIP folder you got called toolbox/LicensesInventory/tests/integrationtests/data and place the data folder in tests/integrationtests folder. Otherwise tests won't work and dry-run script will fail!