Automate and document release process for Rust, Python, Wireshark, and Zeek components #248
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR introduces automated GitHub Actions workflows for releasing the Rust, Python, and Wireshark components of JA4+ via tag-based triggers. It also standardizes the release process for the Zeek package using pure semver tags. Documentation has been updated across the main and language-specific READMEs to:
Releases are now created by pushing tags with specific prefixes (
rust-,python-,wireshark-) or pure semver (for Zeek), with assets automatically attached to the corresponding GitHub release.