v1.1.0

v1.1.0 - 28 Aug 2024
[Miscellaneous]
  * github.com/pkg/errors has been removed (it has been two years :)
  * Updated build/test actions
  * Updated minimum required go version to go 1.21
  * Fix week number handling

v1.0.6

v1.0.6 - 20 Apr 2022
[Miscellaneous]
  * Minimum go version is now go 1.13
  * github.com/pkg/errors is going to be phased out in steps. In this release,
    users may opt-in to using native errors using `fmt.Errorf("%w")` by
    specifying the tag `strftime_native_errors`. In the next release, the default
    will be to use native errors, but users will be able to opt-in to using
    github.com/pkg/errors using a tag. The version after will remove github.com/pkg/errors.

    This is something that we normally would do over a major version upgrade
    but since we do not expect this library to receive API breaking changes in the
    near future and thus no v2 is expected, we have decided to do this over few
    non-major releases.

v1.0.5

v1.0.5
[New features]
  * `(strftime.Strftime).FormatBuffer([]byte, time.Time) []byte` has been added.
    This allows the user to provide the same underlying `[]byte` buffer for each
    call to `FormatBuffer`, which avoid allocation per call.
  * `%I` formatted midnight as `00`, where it should have been using `01`

v1.0.4

• move benchmark to its own directory so users pulling in this packages do not also
  pull in benchmark dependencies

v1.0.3

This time really fix %r, which was not fixed in v1.0.2

v1.0.2

Buf fixes:

• Correctly format zero-padded hours

Features:

• Add microseconds in extra specifications (you must explicitly enable this)
• Add unix epoch seconds in extra specifications (you must explicitly enable this)

v1.0.1

v1.0.0 had a problem when multiple verbatim sections existed (e.g. "foo%Ybar", where "foo" and "bar" are the verbatim sections). This has been fixed.

v1.0.0

Well, I'm going to bite the bullet and tag a release.

This version introduces a new concept of configurable specifications, which will pave the way for future improvements. Meanwhile, most everything else remains the same old trusty code, so I feel confident in giving it a v1.0.0 name.

Thanks for everyone using my library, and if you like what I do, please consider sponsoring me!