Problem/Motivation

TarteAuCitron version 1.20.1 has been released.

Issue fork tacjs-3516931

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

About issue forks

Comments

mably created an issue. See original summary.

mably opened merge request !46

mably’s picture

mably commented
Assigned: mably » Unassigned
Status: Active » Needs review

Waiting for the release on asset packagist:
https://asset-packagist.org/package/npm-asset/tarteaucitronjs

mably’s picture

mably commented
Title: Update tarteaucitron library to version 1.20.0 when released » Update tarteaucitron library to version 1.20.1
mably’s picture

mably commented
Issue summary: View changes

  • mably committed 7ec9f8fd on 7.x 
    Issue #3516931 by mably: Update tarteaucitron library to version 1.20.1
mably’s picture

mably commented
Status: Needs review » Fixed
prudloff’s picture

prudloff commented

Wouldn't it make sense to use a Composer constraint like ^1.20.1?
This way we don't have to update the module every time a new release of tarteaucitron is published.

mably’s picture

mably commented

People are still free to upgrade the TarteAuCitron library as they wish.

I'm just a bit scared that some TarteAuCitron release will break the TacJS module.

But may be we could try to loosen the version requirement and see how it goes.

What do you think?

And the content.json file still needs to be updated manually.

The 1.19 version was released 10 months ago, it's not that frequent.

But I just realized that the 1.20.2 has been released a few hours ago ;)

mably’s picture

mably commented

Updated the version requirement to ~1.20 for now.

prudloff’s picture

prudloff commented

I guess using ~ would be an acceptable compromise.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.