Repository navigation
feat(events): give a session an event envelope carrying run lifecycle - #730
Closed
justintime4tea wants to merge 2 commits into
Closed
justintime4tea wants to merge 2 commits into
justintime4tea wants to merge 2 commits into
Mezmo Org GitHub App for Jenkins / Commitlint
succeeded
Oct 8, 2026 in 5s
Commitlint
🟢 All commits follow the conventional commit style. Great work!
Details
🟢 commit (${\color{blue}e5ce350}$ ) refactor(agents): name a run by its RunId
🟢 commit (${\color{blue}ae7b128}$ ) feat(events): give a session an event envelope carrying run lifecycle
🟢 commit (${\color{blue}513f1ec}$ ) refactor(agent): separate a prepared agent from its runs
🟢 commit (${\color{blue}697ccd1}$ ) fix(orchestration): cap artifact listings in recovery hints
🟢 commit (${\color{blue}78234cc}$ ) feat(orchestration): list available artifacts on a read miss
🟢 commit (${\color{blue}276509b}$ ) fix(orchestration): don't restate attached artifacts in tasks
🟢 commit (${\color{blue}52b3945}$ ) fix(orchestration): harden coordinator artifact handoff
🟢 commit (${\color{blue}54f3704}$ ) feat(orchestration): attach validated artifacts to plan tasks
🟢 commit (${\color{blue}cfa7903}$ ) feat(orchestration): add write_artifact tool for the coordinator
🟢 commit (${\color{blue}40b75ed}$ ) doc: note the slack socket idle deadline
🟢 commit (${\color{blue}1f2f600}$ ) fix(web-server): reconnect the slack socket when it goes silent
⚠️ commit footer must have a blank line before it [${\color{red}footer-leading-blank}$ ]- ℹ️ Add a blank line between the body and footer content
🟢 commit (${\color{blue}162dad3}$ ) doc(web-server): state only the unit on POSTS_PER_RUN
🟢 commit (${\color{blue}c5735da}$ ) doc: trim the slack post tool paragraph to the overview
🟢 commit (${\color{blue}64cba5e}$ ) fix(web-server): tell the agent what a failed slack post delivered
⚠️ commit footer must have a blank line before it [${\color{red}footer-leading-blank}$ ]- ℹ️ Add a blank line between the body and footer content
🟢 commit (${\color{blue}183ced5}$ ) fix(web-server): post trimmed text and name both posting scopes
⚠️ commit footer must have a blank line before it [${\color{red}footer-leading-blank}$ ]- ℹ️ Add a blank line between the body and footer content
🟢 commit (${\color{blue}466e11d}$ ) doc: describe the slack post tool and its opt-in
🟢 commit (${\color{blue}2e98899}$ ) feat: list the tools the server grants an agent in /aura/info
⚠️ commit footer must have a blank line before it [${\color{red}footer-leading-blank}$ ]- ℹ️ Add a blank line between the body and footer content
🟢 commit (${\color{blue}907fa1d}$ ) feat(web-server): attach the slack post tool on http and a2a runs
⚠️ commit footer must have a blank line before it [${\color{red}footer-leading-blank}$ ]- ℹ️ Add a blank line between the body and footer content
🟢 commit (${\color{blue}2cbbb71}$ ) feat(web-server): add a slack post tool gated by an agent opt-in
⚠️ commit footer must have a blank line before it [${\color{red}footer-leading-blank}$ ]- ℹ️ Add a blank line between the body and footer content
🟢 commit (${\color{blue}4b6aa00}$ ) doc(aura): describe RunToolFactory as the value it is
🟢 commit (${\color{blue}e976f84}$ ) doc(aura): drop the stale line above get_all_tool_schemas
🟢 commit (${\color{blue}0762386}$ ) fix(aura): let the coordinator inspect the run's tools
⚠️ commit footer must not be empty [${\color{red}footer-empty}$ ]- ℹ️ Add references, breaking changes, or issue numbers in the footer
Footer items should be in standard Git Trailer Format
ex. See: https://datatracker.ietf.org/doc/html/rfc6749
- ℹ️ Add references, breaking changes, or issue numbers in the footer
⚠️ commit references must not be empty [${\color{red}references-empty}$ ]- ℹ️ Add issue references or PR numbers in the footer
ex. Fixes: #1234
ex. Ref: LOG-4321
- ℹ️ Add issue references or PR numbers in the footer
🟢 commit (${\color{blue}6ad30f3}$ ) fix: show run tools to the planner and carry the run prompt to workers
⚠️ commit footer must not be empty [${\color{red}footer-empty}$ ]- ℹ️ Add references, breaking changes, or issue numbers in the footer
Footer items should be in standard Git Trailer Format
ex. See: https://datatracker.ietf.org/doc/html/rfc6749
- ℹ️ Add references, breaking changes, or issue numbers in the footer
⚠️ commit references must not be empty [${\color{red}references-empty}$ ]- ℹ️ Add issue references or PR numbers in the footer
ex. Fixes: #1234
ex. Ref: LOG-4321
- ℹ️ Add issue references or PR numbers in the footer
🟢 commit (${\color{blue}dd2c08f}$ ) feat: give orchestration workers the run's own tools and a search budget
⚠️ commit footer must not be empty [${\color{red}footer-empty}$ ]- ℹ️ Add references, breaking changes, or issue numbers in the footer
Footer items should be in standard Git Trailer Format
ex. See: https://datatracker.ietf.org/doc/html/rfc6749
- ℹ️ Add references, breaking changes, or issue numbers in the footer
⚠️ commit references must not be empty [${\color{red}references-empty}$ ]- ℹ️ Add issue references or PR numbers in the footer
ex. Fixes: #1234
ex. Ref: LOG-4321
- ℹ️ Add issue references or PR numbers in the footer
🟢 commit (${\color{blue}49acf5e}$ ) fix(web-server): tell slack runs where the message came from
⚠️ commit footer must not be empty [${\color{red}footer-empty}$ ]- ℹ️ Add references, breaking changes, or issue numbers in the footer
Footer items should be in standard Git Trailer Format
ex. See: https://datatracker.ietf.org/doc/html/rfc6749
- ℹ️ Add references, breaking changes, or issue numbers in the footer
⚠️ commit references must not be empty [${\color{red}references-empty}$ ]- ℹ️ Add issue references or PR numbers in the footer
ex. Fixes: #1234
ex. Ref: LOG-4321
- ℹ️ Add issue references or PR numbers in the footer
🟢 commit (${\color{blue}e067d59}$ ) doc: name the manifest fields slack enforces for the search token
🟢 commit (${\color{blue}5017aee}$ ) feat(web-server): give slack runs a search tool that acts as the asker
⚠️ commit footer must not be empty [${\color{red}footer-empty}$ ]- ℹ️ Add references, breaking changes, or issue numbers in the footer
Footer items should be in standard Git Trailer Format
ex. See: https://datatracker.ietf.org/doc/html/rfc6749
- ℹ️ Add references, breaking changes, or issue numbers in the footer
⚠️ commit references must not be empty [${\color{red}references-empty}$ ]- ℹ️ Add issue references or PR numbers in the footer
ex. Fixes: #1234
ex. Ref: LOG-4321
- ℹ️ Add issue references or PR numbers in the footer
🟢 commit (${\color{blue}9aba534}$ ) feat(aura): accept per-run tools on the streaming agent builder
⚠️ commit footer must not be empty [${\color{red}footer-empty}$ ]- ℹ️ Add references, breaking changes, or issue numbers in the footer
Footer items should be in standard Git Trailer Format
ex. See: https://datatracker.ietf.org/doc/html/rfc6749
- ℹ️ Add references, breaking changes, or issue numbers in the footer
⚠️ commit references must not be empty [${\color{red}references-empty}$ ]- ℹ️ Add issue references or PR numbers in the footer
ex. Fixes: #1234
ex. Ref: LOG-4321
- ℹ️ Add issue references or PR numbers in the footer
🟢 commit (${\color{blue}7279251}$ ) feat(web-server): carry slack action tokens and call the search api
⚠️ commit footer must not be empty [${\color{red}footer-empty}$ ]- ℹ️ Add references, breaking changes, or issue numbers in the footer
Footer items should be in standard Git Trailer Format
ex. See: https://datatracker.ietf.org/doc/html/rfc6749
- ℹ️ Add references, breaking changes, or issue numbers in the footer
⚠️ commit references must not be empty [${\color{red}references-empty}$ ]- ℹ️ Add issue references or PR numbers in the footer
ex. Fixes: #1234
ex. Ref: LOG-4321
- ℹ️ Add issue references or PR numbers in the footer
🟢 commit (${\color{blue}544afb4}$ ) fix(web-server): log messages the slack accept rules ignore at debug
⚠️ commit footer must not be empty [${\color{red}footer-empty}$ ]- ℹ️ Add references, breaking changes, or issue numbers in the footer
Footer items should be in standard Git Trailer Format
ex. See: https://datatracker.ietf.org/doc/html/rfc6749
- ℹ️ Add references, breaking changes, or issue numbers in the footer
⚠️ commit references must not be empty [${\color{red}references-empty}$ ]- ℹ️ Add issue references or PR numbers in the footer
ex. Fixes: #1234
ex. Ref: LOG-4321
- ℹ️ Add issue references or PR numbers in the footer
🟢 commit (${\color{blue}3e8b624}$ ) doc: say that thread follow-ups are opted into by the slack app's events
🟢 commit (${\color{blue}5e981e7}$ ) feat(web-server): log why the slack ingress answers or ignores a message
⚠️ commit footer must not be empty [${\color{red}footer-empty}$ ]- ℹ️ Add references, breaking changes, or issue numbers in the footer
Footer items should be in standard Git Trailer Format
ex. See: https://datatracker.ietf.org/doc/html/rfc6749
- ℹ️ Add references, breaking changes, or issue numbers in the footer
⚠️ commit references must not be empty [${\color{red}references-empty}$ ]- ℹ️ Add issue references or PR numbers in the footer
ex. Fixes: #1234
ex. Ref: LOG-4321
- ℹ️ Add issue references or PR numbers in the footer
🟢 commit (${\color{blue}60b505b}$ ) fix(web-server): test turn eligibility without building the turn
⚠️ commit footer must not be empty [${\color{red}footer-empty}$ ]- ℹ️ Add references, breaking changes, or issue numbers in the footer
Footer items should be in standard Git Trailer Format
ex. See: https://datatracker.ietf.org/doc/html/rfc6749
- ℹ️ Add references, breaking changes, or issue numbers in the footer
⚠️ commit references must not be empty [${\color{red}references-empty}$ ]- ℹ️ Add issue references or PR numbers in the footer
ex. Fixes: #1234
ex. Ref: LOG-4321
- ℹ️ Add issue references or PR numbers in the footer
🟢 commit (${\color{blue}f0b2104}$ ) fix(web-server): trim a prefetched thread by turns, not raw messages
⚠️ commit footer must not be empty [${\color{red}footer-empty}$ ]- ℹ️ Add references, breaking changes, or issue numbers in the footer
Footer items should be in standard Git Trailer Format
ex. See: https://datatracker.ietf.org/doc/html/rfc6749
- ℹ️ Add references, breaking changes, or issue numbers in the footer
⚠️ commit references must not be empty [${\color{red}references-empty}$ ]- ℹ️ Add issue references or PR numbers in the footer
ex. Fixes: #1234
ex. Ref: LOG-4321
- ℹ️ Add issue references or PR numbers in the footer
🟢 commit (${\color{blue}69901d5}$ ) fix(web-server): let the probe's participation verdict stand
⚠️ commit footer must not be empty [${\color{red}footer-empty}$ ]- ℹ️ Add references, breaking changes, or issue numbers in the footer
Footer items should be in standard Git Trailer Format
ex. See: https://datatracker.ietf.org/doc/html/rfc6749
- ℹ️ Add references, breaking changes, or issue numbers in the footer
⚠️ commit references must not be empty [${\color{red}references-empty}$ ]- ℹ️ Add issue references or PR numbers in the footer
ex. Fixes: #1234
ex. Ref: LOG-4321
- ℹ️ Add issue references or PR numbers in the footer
🟢 commit (${\color{blue}1e2362c}$ ) fix(web-server): trim a prefetched thread before queueing the reply
⚠️ commit footer must not be empty [${\color{red}footer-empty}$ ]- ℹ️ Add references, breaking changes, or issue numbers in the footer
Footer items should be in standard Git Trailer Format
ex. See: https://datatracker.ietf.org/doc/html/rfc6749
- ℹ️ Add references, breaking changes, or issue numbers in the footer
⚠️ commit references must not be empty [${\color{red}references-empty}$ ]- ℹ️ Add issue references or PR numbers in the footer
ex. Fixes: #1234
ex. Ref: LOG-4321
- ℹ️ Add issue references or PR numbers in the footer
🟢 commit (${\color{blue}d825eef}$ ) fix(web-server): reuse the probe's thread read when answering
⚠️ commit footer must not be empty [${\color{red}footer-empty}$ ]- ℹ️ Add references, breaking changes, or issue numbers in the footer
Footer items should be in standard Git Trailer Format
ex. See: https://datatracker.ietf.org/doc/html/rfc6749
- ℹ️ Add references, breaking changes, or issue numbers in the footer
⚠️ commit references must not be empty [${\color{red}references-empty}$ ]- ℹ️ Add issue references or PR numbers in the footer
ex. Fixes: #1234
ex. Ref: LOG-4321
- ℹ️ Add issue references or PR numbers in the footer
🟢 commit (${\color{blue}c5aec95}$ ) fix(web-server): probe thread participation before queueing a reply
⚠️ commit footer must not be empty [${\color{red}footer-empty}$ ]- ℹ️ Add references, breaking changes, or issue numbers in the footer
Footer items should be in standard Git Trailer Format
ex. See: https://datatracker.ietf.org/doc/html/rfc6749
- ℹ️ Add references, breaking changes, or issue numbers in the footer
⚠️ commit references must not be empty [${\color{red}references-empty}$ ]- ℹ️ Add issue references or PR numbers in the footer
ex. Fixes: #1234
ex. Ref: LOG-4321
- ℹ️ Add issue references or PR numbers in the footer
🟢 commit (${\color{blue}6d07d5a}$ ) fix(web-server): answer thread replies, bound slack calls and waiting
⚠️ commit footer must not be empty [${\color{red}footer-empty}$ ]- ℹ️ Add references, breaking changes, or issue numbers in the footer
Footer items should be in standard Git Trailer Format
ex. See: https://datatracker.ietf.org/doc/html/rfc6749
- ℹ️ Add references, breaking changes, or issue numbers in the footer
⚠️ commit references must not be empty [${\color{red}references-empty}$ ]- ℹ️ Add issue references or PR numbers in the footer
ex. Fixes: #1234
ex. Ref: LOG-4321
- ℹ️ Add issue references or PR numbers in the footer
🟢 commit (${\color{blue}c0a5db5}$ ) doc: fix the slack ingress call count and name the messages tab setting
🟢 commit (${\color{blue}c62a36b}$ ) fix(web-server): answer top-level slack dms inline with dm history
⚠️ commit footer must not be empty [${\color{red}footer-empty}$ ]- ℹ️ Add references, breaking changes, or issue numbers in the footer
Footer items should be in standard Git Trailer Format
ex. See: https://datatracker.ietf.org/doc/html/rfc6749
- ℹ️ Add references, breaking changes, or issue numbers in the footer
⚠️ commit references must not be empty [${\color{red}references-empty}$ ]- ℹ️ Add issue references or PR numbers in the footer
ex. Fixes: #1234
ex. Ref: LOG-4321
- ℹ️ Add issue references or PR numbers in the footer
🟢 commit (${\color{blue}ecb3889}$ ) fix(web-server): keep the bot's own replies in slack thread history
⚠️ commit footer must not be empty [${\color{red}footer-empty}$ ]- ℹ️ Add references, breaking changes, or issue numbers in the footer
Footer items should be in standard Git Trailer Format
ex. See: https://datatracker.ietf.org/doc/html/rfc6749
- ℹ️ Add references, breaking changes, or issue numbers in the footer
⚠️ commit references must not be empty [${\color{red}references-empty}$ ]- ℹ️ Add issue references or PR numbers in the footer
ex. Fixes: #1234
ex. Ref: LOG-4321
- ℹ️ Add issue references or PR numbers in the footer
🟢 commit (${\color{blue}02f89ea}$ ) doc: describe the slack ingress and the server's ingress paths
🟢 commit (${\color{blue}a5fa172}$ ) feat(web-server): answer slack mentions and dms with an agent
⚠️ commit footer must not be empty [${\color{red}footer-empty}$ ]- ℹ️ Add references, breaking changes, or issue numbers in the footer
Footer items should be in standard Git Trailer Format
ex. See: https://datatracker.ietf.org/doc/html/rfc6749
- ℹ️ Add references, breaking changes, or issue numbers in the footer
⚠️ commit references must not be empty [${\color{red}references-empty}$ ]- ℹ️ Add issue references or PR numbers in the footer
ex. Fixes: #1234
ex. Ref: LOG-4321
- ℹ️ Add issue references or PR numbers in the footer
🟢 commit (${\color{blue}b510c09}$ ) feat(web-server): add slack socket mode connection loop
⚠️ commit footer must not be empty [${\color{red}footer-empty}$ ]- ℹ️ Add references, breaking changes, or issue numbers in the footer
Footer items should be in standard Git Trailer Format
ex. See: https://datatracker.ietf.org/doc/html/rfc6749
- ℹ️ Add references, breaking changes, or issue numbers in the footer
⚠️ commit references must not be empty [${\color{red}references-empty}$ ]- ℹ️ Add issue references or PR numbers in the footer
ex. Fixes: #1234
ex. Ref: LOG-4321
- ℹ️ Add issue references or PR numbers in the footer
🟢 commit (${\color{blue}ce3f7fb}$ ) feat(web-server): add slack web api client and event types
⚠️ commit footer must not be empty [${\color{red}footer-empty}$ ]- ℹ️ Add references, breaking changes, or issue numbers in the footer
Footer items should be in standard Git Trailer Format
ex. See: https://datatracker.ietf.org/doc/html/rfc6749
- ℹ️ Add references, breaking changes, or issue numbers in the footer
⚠️ commit references must not be empty [${\color{red}references-empty}$ ]- ℹ️ Add issue references or PR numbers in the footer
ex. Fixes: #1234
ex. Ref: LOG-4321
- ℹ️ Add issue references or PR numbers in the footer
🟢 commit (${\color{blue}22551a1}$ ) fix(orchestration): honor [agent].turn_depth for the coordinator
🟢 commit (${\color{blue}70d2ca7}$ ) Merge branch 'main' into nightly
🟢 commit (${\color{blue}1188185}$ ) fix(skills): scope skill invocation records to the serving agent
⚠️ commit footer must not be empty [${\color{red}footer-empty}$ ]- ℹ️ Add references, breaking changes, or issue numbers in the footer
Footer items should be in standard Git Trailer Format
ex. See: https://datatracker.ietf.org/doc/html/rfc6749
- ℹ️ Add references, breaking changes, or issue numbers in the footer
⚠️ commit references must not be empty [${\color{red}references-empty}$ ]- ℹ️ Add issue references or PR numbers in the footer
ex. Fixes: #1234
ex. Ref: LOG-4321
- ℹ️ Add issue references or PR numbers in the footer
🟢 commit (${\color{blue}837cf05}$ ) fix(config): match tool-name glob patterns with globset
🟢 commit (${\color{blue}cb8b5a4}$ ) fix(orchestration): reject an unflattenable plan instead of panicking
⚠️ commit footer must not be empty [${\color{red}footer-empty}$ ]- ℹ️ Add references, breaking changes, or issue numbers in the footer
Footer items should be in standard Git Trailer Format
ex. See: https://datatracker.ietf.org/doc/html/rfc6749
- ℹ️ Add references, breaking changes, or issue numbers in the footer
⚠️ commit references must not be empty [${\color{red}references-empty}$ ]- ℹ️ Add issue references or PR numbers in the footer
ex. Fixes: #1234
ex. Ref: LOG-4321
- ℹ️ Add issue references or PR numbers in the footer
🟢 commit (${\color{blue}86e15fe}$ ) chore(globpattern): stop emiiting Regex debug info
⚠️ commit footer must not be empty [${\color{red}footer-empty}$ ]- ℹ️ Add references, breaking changes, or issue numbers in the footer
Footer items should be in standard Git Trailer Format
ex. See: https://datatracker.ietf.org/doc/html/rfc6749
- ℹ️ Add references, breaking changes, or issue numbers in the footer
⚠️ commit references must not be empty [${\color{red}references-empty}$ ]- ℹ️ Add issue references or PR numbers in the footer
ex. Fixes: #1234
ex. Ref: LOG-4321
- ℹ️ Add issue references or PR numbers in the footer
🟢 commit (${\color{blue}30bb181}$ ) feat(examples): add Checkly incident response example config
⚠️ commit footer must not be empty [${\color{red}footer-empty}$ ]- ℹ️ Add references, breaking changes, or issue numbers in the footer
Footer items should be in standard Git Trailer Format
ex. See: https://datatracker.ietf.org/doc/html/rfc6749
- ℹ️ Add references, breaking changes, or issue numbers in the footer
⚠️ commit references must not be empty [${\color{red}references-empty}$ ]- ℹ️ Add issue references or PR numbers in the footer
ex. Fixes: #1234
ex. Ref: LOG-4321
- ℹ️ Add issue references or PR numbers in the footer
🟢 commit (${\color{blue}a4dec71}$ ) fix(web-server): let a zero streaming timeout disable the bound
🟢 commit (${\color{blue}e552288}$ ) feat(events): name the agent on orchestrated content
🟢 commit (${\color{blue}212b69e}$ ) feat(events): carry response content on the run's event stream
🟢 commit (${\color{blue}2956e86}$ ) refactor(agents): cancel a run through its own token
🟢 commit (${\color{blue}25086ed}$ ) refactor(events): approvals reach the run's observer
🟢 commit (${\color{blue}70b8e5a}$ ) refactor(events): send a run's events to its observer
🟢 commit (${\color{blue}51c9eed}$ ) feat(agents): give the run its own tool-call queue
🟢 commit (${\color{blue}c530ee4}$ ) feat(agents): make hooks an extension point
🟢 commit (${\color{blue}5b7e15b}$ ) feat(agents): carry run identity in task-local scope
🟢 commit (${\color{blue}5f37ae8}$ ) feat(agents): give StreamingAgent one entry point returning a run handle
🟢 commit (${\color{blue}1f29185}$ ) test(sre): add coverage for default window and override query args
🟢 commit (${\color{blue}a8d25f7}$ ) feat(orchestration): add default 5m telemetry lookback policy
🟢 commit (${\color{blue}e54d2bc}$ ) feat(skills): persist and rehydrate skill invocations across turns
🟢 commit (${\color{blue}6bc6065}$ ) refactor(events): define the conversation agent id once
🟢 commit (${\color{blue}cd986ea}$ ) fix(config): end a literal run at a character class
🟢 commit (${\color{blue}acb6251}$ ) fix(config): measure a class as one character and report the full run
🟢 commit (${\color{blue}50eadd4}$ ) fix(config): enforce the mcp_filter literal cap and name it in the error
🟢 commit (${\color{blue}4956199}$ ) test(events): state the worker-id parse case as current behavior
🟢 commit (${\color{blue}c323c5c}$ ) fix(events): carry the worker id into the tool-completion frame
🟢 commit (${\color{blue}84d2d98}$ ) fix(orchestration): attribute tool completions to the worker
🟢 commit (${\color{blue}3a49ac4}$ ) test(ci): cover the dvp jwt refresh and hogql retry, clean up on failure
🟢 commit (${\color{blue}da6f957}$ ) fix(ci): refresh the docker jwt per dvp report and harden hogql reads
🟢 commit (${\color{blue}bf5ced8}$ ) fix(mcp): warn if multiple servers use same tool name
🟢 commit (${\color{blue}9033711}$ ) feat(mcp): add namespace tracking for mcp tools
🟢 commit (${\color{blue}4424967}$ ) feat(events): approvals emit the agent event schema
🟢 commit (${\color{blue}30c5f84}$ ) feat(events): orchestration emits the agent event schema
🟢 commit (${\color{blue}f227357}$ ) refactor(events): define orchestration SSE frames once
🟢 commit (${\color{blue}f3bdbd6}$ ) feat(events): single-agent producers emit the agent event schema
🟢 commit (${\color{blue}6ea85b4}$ ) feat(events): add agent event schema and broker adapter
🟢 commit (${\color{blue}3883d36}$ ) fix(cli): flush telemetry on sigterm in standalone mode
🟢 commit (${\color{blue}c74a5f0}$ ) fix(orchestration): fail safe on dropped cancel watcher
🟢 commit (${\color{blue}1222763}$ ) fix(web-server): abort stragglers before otel shutdown
🟢 commit (${\color{blue}0088768}$ ) fix(mcp): bound connect/initialize/discovery with a timeout
🟢 commit (${\color{blue}f7c9900}$ ) feat(mcp): identify aura to mcp servers with a configurable user agent
🟢 commit (${\color{blue}fea725e}$ ) fix(ci): keep channel branches from releasing off a stale baseline
⚠️ commit footer must not be empty [${\color{red}footer-empty}$ ]- ℹ️ Add references, breaking changes, or issue numbers in the footer
Footer items should be in standard Git Trailer Format
ex. See: https://datatracker.ietf.org/doc/html/rfc6749
- ℹ️ Add references, breaking changes, or issue numbers in the footer
⚠️ commit references must not be empty [${\color{red}references-empty}$ ]- ℹ️ Add issue references or PR numbers in the footer
ex. Fixes: #1234
ex. Ref: LOG-4321
- ℹ️ Add issue references or PR numbers in the footer
🟢 commit (${\color{blue}926a409}$ ) Merge pull request #692 from mezmo/main
A Conventional Commit
feat(api)!: add oauth2 support
──┬─ ─┬─ ┬ ─┬────────────────
│ │ │ └─ SUBJECT: Clear description
│ │ └───── BREAKING CHANGE: The "!" bang (optional)
│ └──────── SCOPE: The module/area (optional)
└──────────── TYPE: feat, fix, chore, etc.
[BODY]
Detailed explaination of the the changes and why they are being made.
The body must contain a description at minimum 20 characters and lines
are expected to wrap at 72 characters.
BREAKING CHANGE: breaking changes should be highlighted here.
BREAKING CHANGE: Multiple breaking changes can be placed on separate lines.
[FOOTER]
Co-authored-by: @peer
See: http://some.example.com
Closes: #1224
───┬── ┬ ─┬─
│ │ └────── ISSUE NUMBER: The numerical value of a related issue
│ └───────── ISSUE PREFIX: The identifiable issue prefix (e.g., #, GH-, LOG-)
└────────────── ISSUE ACTION: The key (e.g., Closes, Fixes, See)
Get help: https://github.com/mezmo/commitlint-config
Conventional Commit Specification: https://www.conventionalcommits.org/en/v1.0.0/#summary
Loading