Releases: raven-computing/project-init
Releases · raven-computing/project-init
v1.9.1
v1.9.0
Release notes:
- Added the create_directory() API function.
- Added the PROJECT_INIT_APPLICATION_NAME API global to allow better customization of the app branding via addon code.
- You can now click action buttons in supported desktop notifications when initializing new projects.
- Improvements to C, C++ and Python project source templates.
See Changelog.
v1.8.3
Release notes:
- Updates to project source templates.
- Removed support for the C++14 language standard. New projects should target at least C++17.
- Removed support for Python 3.8 in all Python projects. Python 3.9 is now the new minimum supported Python version.
- Deprecated the usage of license classifiers in Python project source templates. You can instead specify your project's license in the pyproject.toml file.
- Minor internal improvements.
See Changelog.
v1.8.2
v1.8.1
v1.8.0
Release notes:
- Added the write_file(), append_file(), move_file() and remove_file() API functions to facilitate file operations on source template files within the project target directory. We've also added the file_exists() and directory_exists() API functions to allow checking for the existence of files and directories within the project target directory. With this new API introduced it is now recommended to use those functions to do file operations instead of manually assembling absolute file paths.
- The replace_str() API function can now be used to replace regex-matched strings inside project source templates, which is independent from substitution variables.
- Added support for Python 3.13 projects.
- The implementation of the form_python_version() API function was changed to use a selection prompt instead of a text pattern. The newly introduced project property 'python.version.min.default' can be used to specify a Python version to be used by default for the prompt.
- Provided C and C++ source templates now use '#pragma once' compiler directives in source headers instead of header include guards. The old behaviour can still be enabled by setting the 'c.headers.include.guards.enable' and 'cpp.headers.include.guards.enable' project properties to 'true', respectively.
- Various internal improvements.
See Changelog.