Releases: Materials-Consortia/optimade-validator-action
Releases · Materials-Consortia/optimade-validator-action
v2.7.0
Developer update
This minor release update implements the usage of pre-commit with subsequent style, linting, and minor security updates to the Python code.
Testing has also improved and the BATS system has been updated to the latest version, ensuring the code is up-to-date and stable with regards to the latest environment changes.
Changelog
v2.7.0 (2022-05-16)
v2 (2022-05-16)
Implemented enhancements:
- Update dependabot frequency #104
- Add pre-commit #77 (CasperWA)
- Update dependabot automation #76 (CasperWA)
Fixed bugs:
Closed issues:
Merged pull requests:
- Update frequency for dependencies update PRs #105 (CasperWA)
- Use
ID!
type instead ofString!
#95 (CasperWA) - Update dependencies #91 (CasperWA)
- Update dependencies #88 (CasperWA)
- Use Python tools logic for checking PR body #87 (CasperWA)
- Update dependencies #86 (CasperWA)
- Update dependencies #85 (CasperWA)
- Add steps to install
pre-commit
#83 (CasperWA) - Fix workflow and python-version task #81 (CasperWA)
- Update dependencies #78 (CasperWA)
- Bump CasperWA/push-protected from 2.4.0 to 2.5.0 #74 (dependabot[bot])
* This Changelog was automatically generated by github_changelog_generator
v2.6.0
v2.5.0
v2.4.0
Fixes:
- Ensure the input parameter
validate unversioned path
is uniform throughout the code and the action (#55, @CasperWA) - The
as type
input parameter now ensures the OPTIMADE Validator is run in the expected way (#57, @CasperWA).
The expected way, is that it will take the URL (fromprotocol
,domain
, andpath
) as is, and run the validator with this and the passedas type
value.
The input parametersindex
,all versioned paths
, andvalidate unversioned path
will all be ignored whenas type
is supplied, since they are either not allowed in the validator or are irrelevant.
For more information, see the README.
v2.3.0
v2.2.2
Fixes:
- Action was failing when run without test harness due to a missing directory (#48)
v2.2.1
Fixes:
- The new
helper.py
was not called correctly inentrypoint.sh
, resulting in a failedv2.2.0
release (#44).
Now the Python script is called using its absolute path.
Developer:
- To ensure the BATS tests are still working correctly, another search-and-replace is added to the test-specific
entrypoint.sh
created during setup of the BATS tests run (#44).
v2.2.0
Changes:
- Add input parameter
create output
(default:false
) (#42):
IfTrue
, this will utilize the-j/--json
option in the OPTIMADE Validator and create a JSON output similar to the output from the Validator. However, this output will be a single JSON object, where the keys correspond to the version part of the versioned base URL that is tested. If it's the unversioned base URL the key will be"unversioned"
.
IfFalse
, the output from this action will be an empty JSON object. - Add output parameter
results
(default:{}
) (#42):
This is the parameter with which the collective JSON object can be retrieved. It will only not be empty if the input parametercreate output
istrue
.
Developer:
v2.1.0
Changes:
- Any failures inside the validation script now return an error in the action itself (#28)
validator_versions
below 0.10 are no longer support (#37)- The behavior of the
all_versioned_paths
option has been modified to reflect the necessity of unversioned base URLs according to the v1.0 release of the OPTIMADE specification (#34).
Miscellaneous: