Adding file path wildcards

Adding support for file path wildcard configuration, like /folder/*war

Rewrite action to TypeScript and remove Docker requirements

Summary
Rewrote the GitHub Action from a Docker-based implementation to a pure TypeScript/JavaScript implementation. This removes the Docker dependency and enables the action to run on all systems that support Node.js and Java.

Changes

Removed Docker dependency: The action no longer requires Docker, eliminating compatibility issues on runners without Docker (e.g., macOS runners)
TypeScript implementation: Rewrote the shell script logic in TypeScript for better maintainability and type safety
Same functionality: All existing functionality is preserved - downloads the Veracode Java API wrapper, builds the command with all parameters, and executes it securely
Secure execution: Uses Node.js spawn for secure command execution without shell interpretation
Benefits

Broader compatibility: Can now run on all GitHub-hosted runners (including macOS) and self-hosted runners with Node.js and Java installed
No Docker required: Eliminates the need for Docker installation and configuration
Faster execution: No Docker image build/pull overhead
Better maintainability: TypeScript provides better error checking and code organization
Backward Compatibility

All parameters remain unchanged - The action accepts the same inputs as before:
Required parameters: appname, createprofile, filepath, version, vid, vkey
All optional parameters work exactly as before
No changes needed to existing workflows using this action
Technical Details

Uses node20 runtime instead of Docker
Downloads Veracode Java API wrapper from Maven Central (same as before)
Executes Java commands using spawn for secure process execution
All validation logic and parameter conflict checks preserved
⚠️ Migration
Runner Requirements: The action now requires a runner with:

Node.js 20+ (automatically available on GitHub-hosted runners)
Java (required to execute the Veracode Java API wrapper)
For GitHub-hosted runners: No changes needed - all GitHub-hosted runners (ubuntu-latest, windows-latest, macos-latest) support Node.js and Java.

For self-hosted runners: Ensure your runner has Node.js 20+ and Java installed. If your current runner doesn't have these, you'll need to either:

Install Node.js and Java on your existing runner, or
Switch to a runner that supports Node.js and Java
Workflow changes: No changes needed to your workflow YAML files - all parameters and usage remain identical.

Note: The Dockerfile and entrypoint.sh files have been removed as they are no longer needed.

Update Dockerfile

Update Dockerfile base image and add curl to the image

Updates

Use artifact action v4
adding policy parameter

Update for dependabot

Update for dependabot

Initial Release of a Veracode action to perform an Upload and Scan

Initial release of a Veracode action that performs an Upload and Scan using the Veracode Java API wrapper, this can be used to perform a Veracode Static Analysis, as a policy scan, sandbox scan and to scan for software composition analysis.

Added new option for includenewmodules

Added new option for includenewmodules

Minor release: adding "scanpollinginterval" parameter

adding "scanpollinginterval" parameter
Interval, in seconds, to poll for the status of a running scan. Value range is 30 to 120 (two minutes). Default is 120.

Minor release: typo fix

What's Changed

• Fix #28 - typo in action.yml by @tjarrettveracode in #29

Full Changelog: 0.2.3...0.2.4

Minor release: add debug function

This release adds two optional parameters that allow pinning the version of the Veracode Java API Wrapper used by the action, and setting the debug parameter to generate additional troubleshooting output from the action.

What's Changed

• Add ability to specify java wrapper version (Fix #22 by @tjarrettveracode) in #23
• Add debug parameter to github action by @sinat101 in #26
• Updated default value for 'version' parameter. by @sinat101 in #27

Full Changelog: 0.2.2...0.2.3