v4.0.0

⚠ BREAKING CHANGES

• remove generators package (#140)

Features

• check that ids exist under a filter when resolving. (a2c1173)
• CON-3568: check that ids exist under a filter when resolving. (#136) (a2c1173)

Bug Fixes

• sort field errors not only by message, but by key (if any) and then by message (#138) (515dc65)

Miscellaneous Chores

• remove generators package (#140) (d7a47a1)

go-base v3.7.0

a2c1173 : feat(CON-3568): check that ids exist under a filter when resolving. (#136) (by Tino Rusch)
b1e6541 : chore: release 3.6.1 (#134) (by Contiamo Bot)
d001321 : fix: do not parse body if ouput dest is nil (#135) (by Lucas Roesler)
1722606 : chore: bump github.com/cenkalti/backoff/v4 from 4.1.0 to 4.1.1 (#132) (by dependabot[bot])
5d65695 : ci: Run release please during builds on master (#133) (by Lucas Roesler)

v3.6.1

Bug Fixes

• do not parse body if ouput dest is nil (#135) (d001321)
• make API errors more informative, no empty strings (#130) (1b7e53d)

go-base v3.6.0

Features

• Add error handling for Unsupported Media Type (#126) (a6670c6)

go-base v3.5.0

Features

• add monitoring server setup utility (49a4344)
• Set logger context in logging middleware (#120) (49a4344)

v3.4.1

fix: Do not throw errors for idle transactions during migration (#118)

Catch and ignore `pq: unexpected transaction status idle` errors when we
commit the migrations transaction.  We have not see the error in
practice when testing the recent changes to the migrations _but_ we do
see this in the unit tests for Hub. This error indicates that a
transaction has started, ie `BEGIN;` but that nothing has happened in
the transaction yet. A similar (but resolved) issue happened in the pq
driver, but the culprit (unclosed Rows) does not apply to our method,
all possible Row objects are automatically closed for us by the sql
methods. See https://github.com/lib/pq/issues/225

See also
https://www.postgresql.org/message-id/[email protected]

Signed-off-by: Lucas Roesler <[email protected]>

Fixed linting issues, stricter linter

fix: Introduce stricter linter and fixes (#117)

Lots of issues fixed.

v3.3.2

fix: Use named return to ensure migration commit err is returned (#116)

Use a named return in the `migrate` method so that the error from
`err = tx.Commit()` is correctly ghosting the return value and therefore
actually returned to the calling method

Signed-off-by: Lucas Roesler <[email protected]>

v3.3.1

fix: Add more logging during db migrations (#115)

* fix: Add more logging during db migrations

**What**
- Add more logging so that users can see the run or skip message for all
  migration statements. Additionally, add a few more log statements to
  ensure all possible errors are logged as soon as possible
- Log affected rows during migrations

Signed-off-by: Lucas Roesler <[email protected]>

Add `BaseAPIClient`

Add `BaseAPIClient` (#113)

Can be used to easily perform HTTP requests to various JSON
APIs. Also, it's going to be used in the code generator.