v2.5.0

feat: print build date on version query

v2.4.1: fix: handle form-urlencoded content type

The default header by curl is application/x-www-form-urlencoded, so when
we send a secret without a specific header this was saved and then
served by the server on secret read.
Set the default content to the requested data when the content type
header was set to form-urlencoded

v2.4.0

add content type to entry creation and reading

v2.3.0

• feat: add base62 flag to enable shorter keys
• fix entry manager tests
• golint: add missing error checks
• golint: fix view issues discovered by golint
• parsers: handle form parse error
• render: respond error if couldn't write the response
• golint: handle for db rollback and commit errors
• golint key.go
• feat: add basex to encode keys to base62
• feat: update entry key accessed time
• feat: handle errors in EntryMigration Alter method
• feat: delete expired entry keys
• refactor: use ticket to delete expired entries periodically
• feat(tests): refactor tests to use testify assertions
• refactor: use key's stringer interface to get keystring
• refactor: use the key.Key type wherever the subject is a key
• refactor: move key string/byte casting to key package
• add hurl tests for reading a secret several times

v2.2.1: fix: handle expired secrets just like non existing secrets

To avoid leaking information the user should not know why she can't read
a secret because it's expired or has no more remaining reads, so return
404.

v2.2.0: Allow to use multiple keys for a single secret (#2)

The entry key concept enables to have multiple keys for a single secret.
That supposed to replace the previous key concept, which was a single key for a
single secret.
The legacy key concept is still supported, but it is not recommended to use it
and it will be removed in the future.

The multiple keys concept is useful to share the same secret with multiple
users, and to be able to revoke access to a single user without affecting the
others.

At the moment the anyone who has access to the secret can add a new key to it.

- Introduced an entrykeymanager service.
- entrykeymanager now returns the Key Encryption Key (KEK) for Data Encryption
  Key (DEK) on creation.
- Added an entry key generator endpoint.
- Shared parser codes have been implemented.
- Introduced a common interface for views.
- Implemented the view interface for entry creation.
- Updated entry delete to implement the views.View interface.
- Updated getentry to implement the views.View interface.
- Fixed an issue with finding keys.
- Refactored services to improve code organization and structure.
- Moved mocks to their respective packages.
- Added support for legacy encryption.
- Updated remaining reads of entry keys.
- Simplified test database and transaction initialization.
- Renamed entrymodel.UpdateAccessed to Use.
- Added a command to generate coverage.
- Improved EntryKeyManager and EntryManager tests.
- Added a coverage clean-up command to the Makefile.
- Handled database operation errors in entrykey tests.

v2.1.11

update github actions

v2.1.8

add tests for delete call

v2.1.7

make postgres queries composable into transaction

Create sub functions which requires sql.Tx as parameters, so they will
run queries in transaction.
The queries can be combined and reused in functions

That's a start to make possible to roll back if we detect that client
can't read the secret (bad decrypt key for example)

v2.1.6

Don't check message if channel receive errored