Release v0.12.4 #214
Merged
Release v0.12.4 #214
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
yaselc
commented
Apr 15, 2021
yaselc
commented
- (PR build(deps): bump requests from 2.23.0 to 2.25.1 #195, 2021-04-15) build(deps): bump requests from 2.23.0 to 2.25.1
- (PR config: Update Python version used in CI jobs to 3.8.9 #212, 2021-04-14) config: Update Python version used in CI jobs to 3.8.9
- (PR rtc.data_models_aec: remove validation for the progression of 'monto_cesion' across the 'cesiones' #210, 2021-04-13) rtc.data_models_aec: remove validation for the progression of 'monto_cesion' across the 'cesiones'
- (PR build(deps): bump virtualenv from 20.0.31 to 20.4.3 #207, 2021-04-08) build(deps): bump virtualenv from 20.0.31 to 20.4.3
- (PR rtc.data_models_aec: remove match validation for 'fecha_firma_dt' and 'fecha_cesion_dt' #208, 2021-04-08) rtc.data_models_aec: remove match validation for 'fecha_firma_dt' and 'fecha_cesion_dt'
- (PR build(deps): bump lxml from 4.6.2 to 4.6.3 #205, 2021-03-26) build(deps): bump lxml from 4.6.2 to 4.6.3
- (PR requirements: Upgrade 'Django' #204, 2021-03-24) requirements: Upgrade 'Django'
Upgrade Django 2.2.10 -> 2.2.18 with fixes to some knows vulnerabilities - GHSA-fvgf-6h6h-3322 - GHSA-m6gj-h9gm-gw44 - GHSA-fr28-569j-53c4
requirements: Upgrade 'Django'
Bumps [lxml](https://github.com/lxml/lxml) from 4.6.2 to 4.6.3. - [Release notes](https://github.com/lxml/lxml/releases) - [Changelog](https://github.com/lxml/lxml/blob/master/CHANGES.txt) - [Commits](lxml/lxml@lxml-4.6.2...lxml-4.6.3) Signed-off-by: dependabot[bot] <support@github.com>
…4.6.3 build(deps): bump lxml from 4.6.2 to 4.6.3
… 'fecha_cesion_dt' The coincidence between the fields 'fecha_firma_dt' and 'fecha_cesion_dt' in a 'cesion' is not mentioned among the validations that the SII performs to accept an AEC XML Document, in fact, there are known cases of valid AEC XML Documents where these fields do not have the same date, with a slight difference of a few seconds, but still, the AEC is valid for the SII. Ref. Instructivo Técnico Registro Público Electrónico de Transferencia de Crédito Source: (https://github.com/cl-sii-extraoficial/archivos-oficiales/blob/master/src/docs/rtc/README.md#instructivo-t%C3%A9cnico)
…tion rtc.data_models_aec: remove match validation for 'fecha_firma_dt' and 'fecha_cesion_dt'
Bumps [virtualenv](https://github.com/pypa/virtualenv) from 20.0.31 to 20.4.3. - [Release notes](https://github.com/pypa/virtualenv/releases) - [Changelog](https://github.com/pypa/virtualenv/blob/main/docs/changelog.rst) - [Commits](pypa/virtualenv@20.0.31...20.4.3) Signed-off-by: dependabot[bot] <support@github.com>
build(deps): bump virtualenv from 20.0.31 to 20.4.3
…cesion' across the 'cesiones' Although the validation of the progression of the value 'monto_cesion' through the 'cesiones' in an AECXml seems to make a lot of sense, there are known SII-approved AECs where the 'monto_cesion' of a 'cesion' exceeds the value of its predecessor. This validation is not documented among those carried out by the SII at the time of uploading an AEC Ref. Instructivo Técnico Registro Público Electrónico de Transferencia de Crédito Source: (https://github.com/cl-sii-extraoficial/archivos-oficiales/blob/master/src/docs/rtc/README.md#instructivo-t%C3%A9cnico)
…on-validator rtc.data_models_aec: remove validation for the progression of 'monto_cesion' across the 'cesiones'
config: Update Python version used in CI jobs to 3.8.9
Bumps [requests](https://github.com/psf/requests) from 2.23.0 to 2.25.1. - [Release notes](https://github.com/psf/requests/releases) - [Changelog](https://github.com/psf/requests/blob/master/HISTORY.md) - [Commits](psf/requests@v2.23.0...v2.25.1) Signed-off-by: dependabot[bot] <support@github.com>
build(deps): bump requests from 2.23.0 to 2.25.1
jtrh
approved these changes
Apr 16, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.