Release v2.0.0-beta.4

chore: bump versions

Release v2.0.0-beta.3

fix: Fix handling of variable operations in URL paths

This commit fixes an issue where variable operations with paths like
/functions/by-name/FunctionName/variables/varName were not being properly
processed. The handleFunctionResource method now checks for paths that
start with 'variables/' and extracts the variable name for processing.

Added implementation to handle renaming of decompiler-generated variables.

Release v2.0.0-beta.2

Prepare CHANGELOG for 2.0.0

Release v1.4.0

Added

• Structured JSON communication between Python bridge and Java plugin
• Consistent response format with metadata (timestamp, port, instance type)
• Comprehensive test suites for HTTP API and MCP bridge
• Test runner script for easy test execution
• Detailed testing documentation in TESTING.md
• Origin checking for API requests
• Mutating tests for API functionality

Changed

• Improved error handling in API responses
• Enhanced JSON parsing in the Java plugin
• Updated documentation with JSON communication details
• Standardized API responses across all endpoints
• Improved version handling in build system

Fixed

• Build complete package in package phase
• Versioning and naming of JAR files
• GitHub Actions workflow permissions
• Extension ZIP inclusion in complete package
• ProgramManager requirement
• Git tag fetching functionality
• MCP bridge test failures

Release v2.0.0-beta.1

docs: Update README for v2.0.0-beta.1

- Add comprehensive description of v2.0.0 features and capabilities
- Update API reference to include all available tools and operations
- Document HATEOAS architecture and response format
- Add detailed examples of using the new data manipulation API
- Update installation instructions for v2.0.0-beta.1

Release v1.4.0-beta6

fix: build complete package in `package` phase

Release v1.4.0-beta5

fix: We don't need destName, we can keep the version info

Release v1.4.0-beta4

fix: ensure extension zip included in complete package

Moved plugin assembly execution to prepare-package phase to ensure
the extension zip artifact is created before the package phase.

Added maven-resources-plugin execution (copy-plugin-zip) to the
package phase to copy the generated extension zip into a reliable
'target/staging' directory.

Updated complete-package.xml assembly descriptor to use a fileSet
referencing 'target/staging' instead of relying on dependencySets
or potentially unstable property expansion for artifact inclusion.

This resolves the issue where the complete package artifact was
missing the Ghidra extension zip.

Release v1.4.0-beta3

fix: Correct GHA complete package assembly

Updated complete-package.xml to use correct properties
(${git.commit.id.abbrev}-${maven.build.timestamp}) for including the
Ghidra extension zip artifact, resolving the incomplete package issue
in GHA builds.

Release v1.4.0-beta2

fix: Add permissions key to GHA workflow