v2.0.0

Breaking changes

• Use setup action by @DecimalTurn in #31

  VBA-Build now focuses only on building and testing VBA-enabled files from source.

  Starting with v2.0.0, environment initialization is no longer handled inside this action.
  You must run DecimalTurn/setup-vba before VBA-Build.

  In previous versions, VBA-Build handled setup tasks like:

  • Installing Microsoft Office on the runner
  • Initializing Office applications
  • Configuring VBA security (VBOM access / macro settings)

  In v2.0.0, these responsibilities were removed from VBA-Build and moved to setup-vba.

  This is an intentional separation of concerns:

  • setup-vba = prepare runner/runtime
  • VBA-Build = build documents from source

  See Migration Guide for more details on how to upgrade.

Minor changes

Dependency updates

• Update GitHub Artifact Actions (major) by @renovate[bot] in #25
• Update actions/checkout action to v6 by @renovate[bot] in #26
• Update GitHub Artifact Actions (major) by @renovate[bot] in #27
• Update dawidd6/action-download-artifact action to v12 by @renovate[bot] in #28
• Update dawidd6/action-download-artifact action to v13 by @renovate[bot] in #29
• Update dawidd6/action-download-artifact action to v14 by @renovate[bot] in #30
• chore(deps): update actions/checkout action to v6 by @renovate[bot] in #32

Full Changelog: v1.4.0...v2.0.0

v1.4.0

What's Changed

New features

• Support for building Access files (.accdb) via msaccess-vcs-build by @DecimalTurn in #12 and #22. Big thanks to @josef-poetzl for the help on this one.
• Support for Macro-Enabled Template Files (by @DecimalTurn):
  • .xltm: Excel Macro-Enabled Template Files in #23
  • .potm: PowerPoint Macro-Enabled Template Files in #24
  • .dotm: Word Macro-Enabled Template Files in #24

Security improvements

• Add checksum (sha256) verification for dependancies by @DecimalTurn in #15

Dependencies update

• Update dawidd6/action-download-artifact action to v11 by @renovate[bot] in #20
• Update actions/download-artifact action to v5 by @renovate[bot] in #19
• Update actions/checkout action to v5 by @renovate[bot] in #16
• Update actions/attest-build-provenance action to v3 by @renovate[bot] in #18

Full Changelog: v1.3.0...v1.4.0

v1.3.0

What's Changed

• Add Excel and Word Objects support by @DecimalTurn in #6
• Add PowerPoint .ppam addin file format support by @DecimalTurn in #7

Full Changelog: v1.2.0...v1.3.0

v1.2.0

What's Changed

• Add Excel Binary Workbook (.xlsb) file format support by @DecimalTurn in #3

Full Changelog: v1.1.0...v1.2.0

v1.1.0

What's Changed

• [Experimental] Add support for running VBA unit tests via RubberDuck

Full Changelog: v1.0.0...v1.1.0

v1.0.0

Updated demo: VBA-Build-Demo

What's Changed

This action now supports:

• Word (.docm) and PowerPoint (.pptm) Files
• More Excel File Formats
• Forms (.frm) and Class Modules (.cls) Files
• Custom File Names

Word (.docm) and PowerPoint (.pptm) Files

The CI workflow will auto-detect the Office application needed to generate the file based on the file extension in the name of the folder where your source code is located.

More Excel File Formats

Regarding Excel, the following extensions are now suported:

• .xlsm
• .xlam
  * .xlsb

Forms (.frm) and Class Modules (.cls) Files

Forms (.frm) files can now be imported into the project. Note that the .frx file with the same file name needs to be in the same folder for it to work properly.

Class Modules (.cls) files can now be imported. Note that Excel or Word objects such as Workbooks, Worksheets and Documents exported as .cls files are not yet supported.

Custom File Names

You can now use any file name for the folder that contains source code and it will use the same name for the generated file.

Full Changelog: v0.1.0...v1.0.0

v0.1.0 - Demo Release

A minimal version that showcases how it's possible to build an Excel file from VBA and XML source code.

For the demo see: VBA-Build-Demo