Comvent v0.5.2

• Dependency upgrades, including @actions/core and @actions/github
• Upgrade json5 to v1.0.2 for security fix

Comvent v0.5.1

• Dependency upgrades, including @actions/core

Comvent v0.5.0

• Upgrade the Node version to use v16
• Dependency upgrades, including @actions/core and @actions/github

Comvent v0.4.5

Minor update to get the latest versions of dependencies

Comvent v0.4.4

Dependency updates, including node-fetch vulnerability fixes

Comvent v0.4.3

Minor update to get the latest versions of dependencies

Comvent v0.4.2

Dependency updates, including @actions/github and other vulnerability fixes

(v0.4.1 was not including the fixes due to missed step in release)

Comvent v0.4.1

Dependency updates, including @actions/github and other vulnerability fixes

Comvent v0.4.0

Minor update from Comvent v0.3, with the following update.

✨ New RegExp Group Support

With v0.3, when Comvent finds a match, it returns a GitHub Action output of found as the value. This worked for most of basic cases, but once you wanted to build more setup, it meant that you had to have very similar entries in Comvent configuration. This also led that GitHub Action definition which uses Comvent to become bloated really quickly, because you need separate if statement for every single match.

This new feature adds support of RegExp "non-named" group for Comvent configuration, allowing you to write a single entry for multiple subcommands.

For example, before v0.4, you needed to have the following Comvent configurations:

# BEFORE v0.4
keywords:
  - name: hello-world
    value: '^\/hello-world$'
  - name: hello-there
    value: '^\/hello-there$'

Now, you can bundle them together if you want to make it like a subcommand.

# WITH v0.4
keywords:
  - name: hello
    value: '^\/hello-(\S+)$'

Ref: About RegExp group https://developer.mozilla.org/en-US/docs/Web/JavaScript/Guide/Regular_Expressions/Groups_and_Ranges

NOTE: Known Limitations

There are some limitations in this approach, and some underlying behaviour change.

• You can only use the first group as of now. If you provide multiple groups, Comvent does not keep the other groups for further processing.
• When the RegExp is a match but the first group is an empty string, Comvent falls back to use the entire line string it used to match against. This is to ensure the truthy-ness is not broken from the v0.3 behaviour.

---

ℹ️ Note about Comvent Configuration File

Because v0.4 does not have any change to the configuration file setup, Comvent configuration file stays with v0.2.0. This may change in the future, especially at v1 release, but for the time being, please stick to using v0.2.0 for the version, or simply omit the field so that Comvent will default to use the latest available from the version used.

Comvent v0.3.0

Minor update from Comvent v0.2, with the following update.

New Output Support

When Comvent finds a match for any of the provided keywords, it would provide comvent-found-any-match output field with value found. This allows having a single flag to check against when multiple keywords are about related setup. This is especially useful when you need to run some preparatory step such as installing tools for ChatBot experience.

---

ℹ️ Note about Comvent Configuration File

Because v0.3 does not have any change to the configuration file setup, Comvent configuration file stays with v0.2.0. This may change in the future, especially at v1 release, but for the time being, please stick to using v0.2.0 for the version, or simply omit the field so that Comvent will default to use the latest available from the version used.