mox/apidiff
Mechiel Lukkien 69a4995449
move func PartStructure from webhook to queue, so it isn't tracked anymore for apidiff changes
the types in webhook should be subjected to apidiff'ing, this was a shared
function. it is better off in package queue. also change the apidiff script so
it leaves apidiff/next.txt empty when there aren't any changes. makes it easier
to rotate the files after releases where nothing changed (a common occurrence).
2024-12-07 13:57:07 +01:00
..
next.txt move func PartStructure from webhook to queue, so it isn't tracked anymore for apidiff changes 2024-12-07 13:57:07 +01:00
packages.txt add a webapi and webhooks for a simple http/json-based api 2024-04-15 21:49:02 +02:00
README.txt keep track of the exposed api for reusable packages using apidiff 2023-12-14 15:39:47 +01:00
v0.0.9.txt change javascript into typescript for webaccount and webadmin interface 2023-12-31 12:05:31 +01:00
v0.0.10.txt queue: deliver to multiple recipients in a single smtp transaction 2024-03-07 10:07:53 +01:00
v0.0.11.txt rotate apidiff/next.txt before release 2024-04-30 20:52:50 +02:00
v0.0.12.txt add upcoming release to website, and rotate apidiff 2024-10-06 12:48:56 +02:00

This directory lists incompatible changes between released versions for packages
intended for reuse by third party projects, as listed in packages.txt. These
files are generated using golang.org/x/exp/cmd/apidiff (see
https://pkg.go.dev/golang.org/x/exp/apidiff) and ../apidiff.sh.

There is no guarantee that there will be no breaking changes. With Go's
dependency versioning approach (minimal version selection), Go code will never
unexpectedly stop compiling. Incompatibilities will show when explicitly
updating a dependency. Making the required changes is typically fairly
straightforward.