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

[backport -> release/3.7.x] chore(deps): bump lua-resty-events from 0.2.1 to 0.3.0 #13244

Merged
merged 2 commits into from
Jun 28, 2024

Conversation

bungle
Copy link
Member

@bungle bungle commented Jun 20, 2024

Summary

Cherry-pick: #13228

FTI-6008, KAG-4759

@github-actions github-actions bot added the cherry-pick kong-ee schedule this PR for cherry-picking to kong/kong-ee label Jun 20, 2024
@bungle bungle requested review from hanshuebner, gszr, locao and kikito June 20, 2024 17:55
bungle added 2 commits June 21, 2024 10:40
- [style(lib/compat): update module version](Kong/lua-resty-events#57)
- [tests(*): use resty.events.new correctly as documented](Kong/lua-resty-events#59)
- [feat(protocol): send worker info (id and pid) to broker](Kong/lua-resty-events#54)
- [fix(*): option validation of broker id](Kong/lua-resty-events#62)
- [fix(broker): worker id based queues](Kong/lua-resty-events#60)
- [chore(worker): actively close connection to broker on error](Kong/lua-resty-events#63)
- [fix(*): retain events on send failures](Kong/lua-resty-events#61)

Signed-off-by: Aapo Talvensaari <[email protected]>
@bungle bungle force-pushed the chore/lua-resty-events-0.3.0-3.7 branch from 49ea68f to 17c8d8d Compare June 21, 2024 07:40
@bungle bungle removed the cherry-pick kong-ee schedule this PR for cherry-picking to kong/kong-ee label Jun 24, 2024
@bungle bungle merged commit 69d87c0 into release/3.7.x Jun 28, 2024
28 checks passed
@bungle bungle deleted the chore/lua-resty-events-0.3.0-3.7 branch June 28, 2024 08:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants