Repository navigation
Releases
Releases · EduardSergeev/project-version-action
Update documentation
- Fixed: documentation:
- Fixed: default
versionvalue used in text:
It is now0.0.0.0, not three-parts but four - Added: example of three-part version configuration for Node.js project
- Added:
Output parametersection
- Fixed: default
Fix release creation
- Fix release creation
- Add new badges with links:
build: CI status ofmainbranchrelease: latest released version
Add new `version-file-exists` input parameter
- Add new (optional, default is
true) input parameterversion-file-exists:
Thenversion-file-exists: truespecified byversion-filefile must indeed exist in repository. Otherwise the action fails with[version-file] could not be found but is requirederror - When
version-file-exists: falseand there is noversion-filein repository the action now only setsVERSIONenvironment variable andproject-versionaction output to calculated project version
Fix `latest` and `pre-release` flags calculation
v6.4-pre Fix `latest` and `pre-release` flags calculation
Update documentation
- Add description for new input parameter
version-file-exists - Use latest
v6version in examples
Create release on tag push
- When new git tag is pushed: create new release from corresponding commit
- If it is pussed to
maincreate "latest release" otherwise create pre-release
Documentation update
- Change:
- Update documentation:
- Action input
version-stub:default value is now0.0.0.0 - Action input
leading-zeros:default is nowfalse
- Action input
- Update documentation:
Change default input values
- Change:
- Action input
version-stub:default value is now0.0.0.0 - Action input
leading-zeros:default is nowfalse
- Action input
- Fix:
Output modified version-file
Output version-file content after version-stub in it replaced with current version
Time zone
- Add:
time-zone(optional) input parameter
To set time zone to be used to determine the current date/time
If not set the action runner current date/time is used