[new release] syslog-message (0.0.3)

[verbosemode]

Syslog message parser

• Project page: https://github.com/verbosemode/syslog-message
• Documentation: https://verbosemode.github.io/syslog-message/doc

CHANGES:

• Warning: encode function no longer truncates messages to 1024 bytes by default
• split message part into tag and content (extend type t to contain tag and message (both type string), fixes #18 verbosemode/syslog-message#20, by @hannesm)
• use result types instead of option (extend type t to contain tag and message (both type string), fixes #18 verbosemode/syslog-message#20, by @hannesm)
• remove transport-dependent length check from encode (extend type t to contain tag and message (both type string), fixes #18 verbosemode/syslog-message#20, by @hannesm)
• switch build system to Dune (Switch build system to Dune verbosemode/syslog-message#19, by @dra27)
• add encode_local for sending to local syslog (Add Syslog_message.encode_local verbosemode/syslog-message#17, by @dra27)
• forgot to thank @hannesm, @Leonidas-from-XIV for past contributions

[mseri]

Looks good. Waiting for camelus before merging

[camelus]

☀️ All lint checks passed d2091b9

• These packages passed lint tests: syslog-message.0.0.3

---

☀️ Installability check (9789 → 9790)

• new installable packages (1): syslog-message.0.0.3

[dra27]

Small point, but shouldn’t it really be 0.1.0 rather than 0.0.3? Or even take the plunge to 1.0.0, given the interface changes?

[verbosemode]

Small point, but shouldn’t it really be 0.1.0 rather than 0.0.3? Or even take the plunge to 1.0.0, given the interface changes?

You're right. It should have been at least a 0.1.0 due to the interface changes. I could still change it, since @hannesm is using >= "0.0.2" as version constraint in his logs-syslog library.

[hannesm]

I'm actually using = "0.0.2" in logs-syslog, so I don't mind.

[kit-ty-kate]

@verbosemode what do you want to do?

[verbosemode]

@verbosemode what do you want to do?

I went for option three now and made a 1.0.0 release in PR #12809. I didn't know how to properly edit this one, sorry.