forked from tableau/TabPy
-
Notifications
You must be signed in to change notification settings - Fork 0
/
CHANGELOG
executable file
·60 lines (40 loc) · 1.64 KB
/
CHANGELOG
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
# TabPy Changelog
This file list notable changes for TabPy project releases.
The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/).
## v0.4.1
- Added request context logging as a feature controlled with
TABPY_LOG_DETAILS configuration setting.
- Updated documentation for /info method and v1 API.
- Added integration tests.
## v0.4
### Improvements
- Added basic access authentication (all methods except /info)
- tabpy-tools can deploy models to TabPy with authentication on
- Increased unit tests coverage
- Travis CI for merge requests: unit tests executed, code style checking
## v0.3.2
### Breaking changes
- Logger configuration now is in TabPy config file.
### Improvements
- Remove versioneer and just replace it with VERSION file
- Require Python 3.6.5
- Require jsonschema to be compatible with 2.3.0
- Added setup instructions (known issues) for CentOS
## v0.3.1
- Fixed dependency on tabpy-tools in startup scripts
- Fixed Python version dependency in tabpy-server setup script
## v0.3
### Breaking changes
- The config file is now not just Python code but an actual config
- Tornado config file has a different setting for CORS
- Setup scripts are deleted - setup (if needed) happens with the startup script
- tabpy-client is tabpy-tools now
### Improvements
- Secure connection (HTTPS) is supported with Tableau 2019.2 and newer versions
- Documentation is improved with more examples added
- Versioning is done with Versioneer and github release tags
- Improved logging
- Unit tests are passing now
- Configurations for Postman and Swagger are available to use those against running TabPy
## v0.2
- Initial version