This project is following Semantic Versioning
0.10.7 - 2018-07-25
dpat bundle-installer .
failure under node 8 with npm 5.6 due to incorrect path resolution
0.10.6 - 2018-07-24
- upgrade jest to version
^23.4.1
- add node_modules folder from the project compiled by apps-dpat to NODE_PATH to allow projects to override packages like for example jest
0.10.5 - 2018-04-23
- package docs from src/main/docs in the application bundle
0.10.4 - 2018-04-03
- upgrade
@deskpro/apps-installer
to versionv0.4.5
0.10.3 - 2018-03-29
- allow storage ACL to override the ACL of the setting with the same name
0.10.2 - 2018-03-27
- schema for apps manifest v2.4.0
0.10.1 - 2018-03-27
- webpack and webpack-dev-server executables not resolved properly when
apps-dpat
is a dependency for node versions 8 and up
0.10.0 - 2018-03-08
-
new
dpat travis pr-comment
command that adds a comment with a link to the build artifact to a pull requests (only github supported at the moment) -
ability to set the build artifact file name after the package name instead of using the default one
0.9.7 - 2018-02-09
- default
process.env.NODE_ENV
toproduction
when packaging the app for distribution with webpack
0.9.6 - 2017-11-24
- upgrade apps-installer to v0.4.2
0.9.5 - 2017-11-23
- upgrade apps-installer to v0.4.1
0.9.4 - 2017-11-20
- upgrade apps-installer to v0.4.0
- upgrade dependencies
0.9.3 - 2017-11-03
- incorrect path to default installer bundle
- upgrade apps-installer to v0.3.2
0.9.2 - 2017-10-27
- detection of a customized app installer takes into consideration the project directory
0.9.1 - 2017-10-24
- updates INSTALLER_VER in package.json
0.9.0 - 2017-10-24
- renames @deskproapps references to @deskpro
0.8.0 - 2017-10-11
- add a command to bundle the default app installer together with the app
- regenerate npm-shrinkwrap.json
0.7.1 - 2017-10-09
- removed obsolete property named
enabled
from the custom field manifest definition - add required property named
title
to the custom field manifest definition
0.7.0 - 2017-10-05
- support for manifest version 2.3.0
0.6.0 - 2017-09-18
- support for validating multiple manifest versions
- schema for manifest version 2.2.0 which renames the top-level key "state" to "storage"
- made
appVersion
a required key from versions 2.1.0 and up - SyntaxValidator returns more helpful error messages
- changelog using keep a changelog format
- babel support for async/await
- create NODE_PATH variable if not set
- dpat test command to help with running tests
- add dpat's node_modules dir to NODE_PATH env variable
- add travis publishing options to package.json
- enable travis automated builds and deploys
- make all dependencies run-time dependencies to be able to run jest tests directly when dpat is installed
- dpat failure to run on travis ci because of incomplete environment in spawned child processes
- add missing state key schema definitions
- add validation using schema for the state access rules entry from the app's manifest
- Development server fails to start due to missing return value
- update links after transferring the repository to the
Deskpro
organization - enable travis ci integration
- The algorithm that resolves the source for the application manifest does not choose manifest.json when that file is present
- Manifest validation error prevents dev server from starting
- Use deskpro key in package.json to generate app manifest
- Improved error messages from cli commands
- Version bump due to previous version blocked by npm (un-published)
- New build module which exports all the tools for building apps
- Webpack executables not found if dpat installed globally
- Failure to resolve dpat root path
- In dev mode, copy sdk distributions only if they have been added as dependencies
- Add options to resolve babel plugins and presets relative to dpat installation root
- Add possibility to collect all dependencies from package.json in a vendor bundle
- Adjust webpack build scripts
- more build commands
- more webpack plugins
- fix app manifest validation
- Add
dpat compile
command
- Fail packaging, compiling and deploying with a descriptive error if node_modules folder is missing
- Use published version of deskproapps-sdk-react
- Distribution assets use standard file names
- Resolving deskpro react sdk in webpack configuration is using wrong file paths
- Allow projects to override the webpack configuration for distribution and development
- Enable CORS for development server
- Added first online documentation
- Add package and deploy commands
- Initial public release