Skip to content

Releases: Patternslib/dev

Release 3.4.1

11 Aug 18:51
Compare
Choose a tag to compare

3.4.1 (2023-08-11)

Bug Fixes

  • Correct comment in Makefile. (5fb33c6)

Maintenance

Release 3.4.0

27 Jul 23:49
Compare
Choose a tag to compare

3.4.0 (2023-07-27)

Maintenance

  • Depend on the minimum actively maintained Node.js version >= 16. (603a024)

  • Upgrade dependencies. (b3bb92f)

Release 3.3.5

29 May 23:11
Compare
Choose a tag to compare

3.3.5 (2023-05-29)

Bug Fixes

  • Fix hook config from 3.3.4. (b4f02f6)

Release 3.3.4

29 May 22:35
Compare
Choose a tag to compare

3.3.4 (2023-05-29)

Bug Fixes

  • Include the correct bundle version in entry file header comment. (ea32b4d)

    In order to have the correct version specifier in the bundle's entry
    script header comment the bundle must be built after the version bump.
    Use release-it hooks to do that.

Maintenance

Release 3.3.3

28 May 14:53
Compare
Choose a tag to compare

3.3.3 (2023-05-28)

Bug Fixes

  • Add pre-built bundles to the npm distribution again. (c85dbdc)

    This was lost in a previous Makefile update.
    Now you can again reference jsdelivr and and unpkg to include bundles.

  • Change optional chaining babel plugin name. (e57793a)

Maintenance

  • Remove dependency on semver which is not needed since the recent Makefile improvements. (1dd1c3a)

  • Upgrade dependencies. (6d052b7)

Release 3.3.2

11 May 09:05
Compare
Choose a tag to compare

3.3.2 (2023-05-11)

Maintenance

Release 3.3.1

21 Apr 16:25
Compare
Choose a tag to compare

3.3.1 (2023-04-21)

Release 3.3.0

17 Apr 23:39
Compare
Choose a tag to compare

3.3.0 (2023-04-17)

Bug Fixes

  • Simplify release make commands. (49077d2)

    Change the prerelease commands back to pre-3.2.0 names.
    This was necessary because the previous change did create for each
    command a new increment, which was not what we wanted.
    Instead the Makefile is now restructured:

  • First the npm release is done and the package.json written with the
    correct version. If no increment is given (in case of the prerelease
    targets) an interactive prompt asks the user to define one.
  • Second the GitHub release is done. It's no more necessary to guess the
    next version before the npm version was done. Instead we now rely on
    release-it choosing it for us.
    Now we do have again the "prerelease-alpha" and "prerelease-beta"
    Makefile targets.

Release 3.2.0

17 Apr 21:35
Compare
Choose a tag to compare

3.2.0 (2023-04-17)

Features

  • Change prerelease commands to prerelease-INCREMENT-PREID (6b488e1)

    Change the prerelease commands to define the increment level.
    Instead of "prerelease-alpha" there are now "prerelease-major-alpha",
    "prerelease-minor-alpha" and "prerelease-patch-alpha".
    Instead of "prerelease-beta" there are now "prerelease-major-beta",
    "prerelease-minor-beta" and "prerelease-patch-beta".
    This fixes a problem where the first prerelease for major or minor
    increments got only a patch-level increment.

Maintenance

Release 3.1.13

17 Apr 09:11
Compare
Choose a tag to compare

3.1.13 (2023-04-17)

Bug Fixes

  • Improve the release-it commit template to include a newline between each commit and add any commit references to the end. (1603d0b)

  • Improve the release-it commit template to include a newline between header and body text. (14ace2b)

  • Include all changes since last regular release only in GitHub releases. (ec86755)

    When doing regular releases include all the changes since the last
    regular release - including changes from pre-releases in the release
    notes on GitHub, but not in the CHANGES.md file. In the CHANGES.md file
    every change can be seen at once. Including all the changes since the
    previous regular release is useful for the GitHub release page only.

Maintenance