strftime/Changes at master · lestrrat-go/strftime · GitHub

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
Changes
=======

v1.2.0 - 21 May 2026
[New features]
  * Support a no-padding flag for numeric specifiers. A `-` (glibc) or `#`
    (Windows) flag placed between the `%` and the conversion specifier
    suppresses the leading zero/blank padding, e.g. `%-m` -> "1" instead of
    "01". (#91)
  * Add locale support for name-based specifiers (%A, %a, %B, %b, %p, etc.).
    A new `WithLocale` option accepts a `Locale`, with `DefaultLocale()`
    providing the English defaults. Supporting `MonthNames` / `WeekdayNames`
    types and a `LocaleOption` constructor are also exported. (#92)

[Performance]
  * Speed up formatting and pattern compilation. (#93)

[Bug fixes]
  * Fix the locking mechanism in the package-level `Lookup` function. (#76)

[Miscellaneous]
  * Modernize CI and lint infrastructure. (#87)
  * Updated dependencies (testify, GitHub Actions, codecov).

v1.1.1 - 29 Jul 2025
  * Implement %G and %g (#67)

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 - 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
[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`


before v1.0.4

Apparently we have failed to provide Changes prior to v1.0.5 :(