Changelogs » Ing-ynab

PyUp Safety actively tracks 266,461 Python packages for vulnerabilities and notifies you when to upgrade.

Ing-ynab

1.1.0

Fixed
  * Duplicate imports due to same date, applicant, purpose and amount
  * Only prompt for YNAB Access Token if not in debug mode
  
  ⚠️ Upgrading will break state once, so before upgrading make sure `START_DATE` is set to today or unset. Once you've upgraded you will have some duplicates from today. A later release will introduce versioning to the hash sum so we can do these changes without breaking state (https://github.com/bahlo/ing-ynab/issues/8).

1.0.2

Fixed
  * Bug where YNAB would return 400 because the transaction date is in the future
  
  Added
  * Exception handling for YNAB

1.0.1

Fixed
  * Docker image was not working due to a change in the build setup

1.0.0

ing-ynab is now considered stable. :rocket: I've been running it over a week while improving the codebase and CI setup without any major bugs.
  
  Added
  * FAQ section on the README.md
  * Dependabot configuration
  
  Changed
  * Renamed the project {ing_ynab => ing-ynab} to match the binary

0.5.0

Added
  * PyPI package deployment step and documentation

0.4.0

Added
  * Types
  * Basic tests
  * CI
  * License
  * `setup.py`
  
  Changed
  * Renamed most of the `FINTS_` env vars to `ING_`
  * Split code in multiple modules
  
  Fixed
  * Fixes a bug where new transactions were imported multiple times

0.3.1

This release fixes a bug where the application would not prompt for the YNAB access token until there are new transactions and always prompt for the FinTS password but only use it if the env was empty.

0.3.0

This release adds the option to color all imported transactions with `YNAB_FLAG_COLOR`.

0.2.0

* Added prompt fallback for YNAB Access token (2ed7a1e)
  * Added licence (GPL-3.0)
  * Improved documentation

0.1.0

This is the first release. It needs some testing before `v1.0.0`