Repository navigation
v1.1 - Support for Custom Release Tags
Version 1.1.0 - Support for Custom Release Tags
🎉 New Features
- Custom Release Tag Support: Added optional
energyplus-taginput to support EnergyPlus releases with non-standard tags (e.g.,v24.2.0a)- When not specified, defaults to
v{energyplus-version}for backward compatibility - Enables installation of the latest EnergyPlus versions like 24.2.0 that use tags with suffixes
- When not specified, defaults to
📝 Changes
-
Updated action.yml:
- Added new optional input
energyplus-tag - Input is passed to installation script via
ENERGYPLUS_TAGenvironment variable
- Added new optional input
-
Updated install.sh:
- Now accepts
ENERGYPLUS_TAGenvironment variable - Falls back to
v$ENERGYPLUS_VERSIONif tag not provided - Updated download URL construction to use the custom tag
- Now accepts
-
Enhanced Documentation:
- Added comprehensive input descriptions in README
- Included usage examples for both standard and custom tag scenarios
- Provided specific example for EnergyPlus 24.2.0 with
v24.2.0atag
🔄 Backward Compatibility
This release is fully backward compatible. Existing workflows will continue to work without modification as the energyplus-tag input is optional and defaults to the previous behavior (v{energyplus-version}).
📚 Usage Example
- uses: Elementa-Engineering/install-energyplus@v2
with:
energyplus-version: 24.2.0
energyplus-sha: <appropriate-sha>
energyplus-install: 24-2-0
energyplus-tag: v24.2.0a