Support for latest version of library

Created on 14 May 2025, 22 days ago

Problem/Motivation

  • Currently recommended version is 11 versions behind, that's 4 years old
  • I have found a bug, and will be soon reporting a fix, but even if the library fixes the issue, I will have to patch over 3.8.18

Are there any plans to at least support 3.9.*? What are the main roadblocks for providing support (as in the event I can perhaps contribute, if work allows it).

πŸ’¬ Support request
Status

Active

Version

4.1

Component

Code

Created by

πŸ‡ΊπŸ‡ΈUnited States in0ni

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Merge Requests

Comments & Activities

  • Issue created by @in0ni
  • πŸ‡ΊπŸ‡ΈUnited States dcam

    No roadblocks really. I just don't keep up to date on new releases of the JS. Or ever think about it. Do you have any indication if your bug fix will be accepted soon? I can hold off adding a new version until it's ready.

  • πŸ‡ΊπŸ‡ΈUnited States dcam

    Part of the problem is that the repo owner makes new tags, but not new releases. You can't subscribe to new tags as far as I can see.

  • πŸ‡ΊπŸ‡ΈUnited States in0ni

    Ok, I guess there is also concern due to the "(not recommended)" message, which indicates perhaps not properly working.

    I have yet to create a patch for the bug, just found it yesterday once the ticket is created I can share for reference. When I first tried this module, which we had requirements to implement, I remember the latest version not working properly -- so we kept it at the recommended version.

    I would say if support for latest version is possible rather easily, go ahead no need to wait for the fix. As it will be applied on the latest dev and will be minor so there should be no issue

  • πŸ‡ΊπŸ‡ΈUnited States dcam

    Ok, I guess there is also concern due to the "(not recommended)" message, which indicates perhaps not properly working.

    Using the latest version from the CDN is not recommended because the maintainer can and will release backward-incompatible changes. They've done it before. See the release notes for version 4.0.0 of the module β†’ . By all means go ahead and use it, but you do so at your own peril.

  • πŸ‡ΊπŸ‡ΈUnited States in0ni

    Ok, understood -- yes best to keep on the 3.x branch and not use a pointer to any major release.

    I'm a bit stuck with how to move forward with this, and need your assistance to at least get an idea. We have two options:

    OPTION 1 (ideal) I patch the latest release (3.9.7), but this is only worth it if the module will support it.
    OPTION 2 I patch the recommended release (3.8.18), only for this project and host our patched version

    In order to proceed, it would help to know if support for 3.9.x would be feasible and a ball-park estimate as to when. This way we can determine if we just wait for support and go with OPT #1, or if we have to go with OPT #2

  • πŸ‡ΊπŸ‡ΈUnited States in0ni

    Hello @dcam,

    Wondering if you are able to provide a rough estimate so we may decide which route to go with. Greatly appreciate it, again if possible I can try to provide assistance.

  • Merge request !13Support 3.9.7 β†’ (Merged) created by dcam
  • Pipeline finished with Skipped
    16 days ago
    #502531
    • dcam β†’ committed 952d8c35 on 4.x
      Issue #3524525 by dcam: Support for latest version of library
      
  • πŸ‡ΊπŸ‡ΈUnited States dcam

    I added support for 3.9.7. If that doesn't work for you, then you can always download the library and serve it from your local files.

    I'll put out a new release shortly.

  • πŸ‡ΊπŸ‡ΈUnited States in0ni

    This is great, thank you!
    I will work on the patch, if and when accepted, surely will be a minor release and at that point can contribute a simple PR for the minor version.

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

Production build 0.71.5 2024