Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CEXT-2784: Release commerce eventing and webhook modules #145

Closed
wants to merge 2 commits into from
Closed
Show file tree
Hide file tree
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 14 additions & 0 deletions src/pages/events/release-notes.md
Original file line number Diff line number Diff line change
Expand Up @@ -12,6 +12,20 @@ These release notes describe the latest version of Adobe I/O Events for Adobe Co

See [Update Adobe I/O Events for Adobe Commerce](installation.md#update-adobe-io-events-for-adobe-commerce) for upgrade instructions.

## Version 1.5.0

### Release date

February 7, 2024

### Enhancements

* Added support of field converters. Now you can specify converter class that will be applied to fields in the event payload. <!--- CEXT-1699 -->

* Added event tracking ID field for better tracking of the event delivery process. <!--- CEXT-2759 -->

* Increased test coverage of eventing modules <!--- CEXT-2640 -->

## Version 1.4.1

### Release date
Expand Down
14 changes: 14 additions & 0 deletions src/pages/webhooks/release-notes.md
Original file line number Diff line number Diff line change
Expand Up @@ -9,6 +9,20 @@ keywords:

These release notes describe the latest version of Adobe Commerce Webhooks.

## Version 1.2.0

### Release date

February 7, 2024

### Enhancements

* Added a new module `AdobeCommerceWebhooksAdminUi` for managing webhooks from the Admin UI

* Added an ability to modify and create webhooks from the Admin UI
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Wondering if we should mention xml-defined webhooks specifically just to make it clearer that the admin UI can be used to extend/override xml config

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks, updated it. But don't know how to rephrase it in a better way. @keharper please take a look


* Added an ability to modify and create webhooks rules, headers and fields from the Admin UI

## Version 1.1.0

### Release date
Expand Down
Loading