Version stuck to 8.x-1.4

Created on 12 June 2023, over 1 year ago
Updated 13 June 2023, over 1 year ago

Is anyone else still seeing version 8.x-1.4 after to update to version 8.x-1.5 ?

Problem/Motivation

./composer.json has been updated
Running composer update drupal/glyphicons
Loading composer repositories with package information
Info from https://repo.packagist.org: #StandWithUkraine
Updating dependencies
Lock file operations: 3 installs, 0 updates, 0 removals
- Locking drupal-ckeditor-libraries-group/colordialog (4.20.1)
- Locking drupal/colordialog (1.3.0)
- Locking drupal/glyphicons (1.5.0)
Writing lock file
Installing dependencies from lock file (including require-dev)
Package operations: 3 installs, 0 updates, 0 removals
- Downloading drupal/colordialog (1.3.0)
- Downloading drupal-ckeditor-libraries-group/colordialog (4.20.1)
- Downloading drupal/glyphicons (1.5.0)
0/3 [>---------------------------] 0%
2/3 [==================>---------] 66%
3/3 [============================] 100%
- Installing drupal/colordialog (1.3.0): Extracting archive
- Installing drupal-ckeditor-libraries-group/colordialog (4.20.1): Extracting archive
- Installing drupal/glyphicons (1.5.0): Extracting archive
0/3 [>---------------------------] 0%
3/3 [============================] 100%
Package doctrine/reflection is abandoned, you should avoid using it. Use roave/better-reflection instead.
Package symfony/debug is abandoned, you should avoid using it. Use symfony/error-handler instead.
Generating autoload files
Hardening vendor directory with .htaccess and web.config files.
48 packages you are using are looking for funding.
Use the `composer fund` command to find out more!
Cleaning installed packages.

Steps to reproduce

php81 /usr/local/bin/composer require 'drupal/glyphicons:^1.5'

πŸ’¬ Support request
Status

Closed: won't fix

Version

1.5

Component

Miscellaneous

Created by

πŸ‡ΊπŸ‡ΈUnited States joshuautley

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

Comments & Activities

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

    I had this occur on a second site and decided to delete the composer.lock file and run update.php which seems to have resolved the issue.

    Is this just an issue with my composer -or- is there an issue in the update code for the module? Other modules did not require this step.

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

    Update, having deleting the composer.lock file did NOT resolve this issue.

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

    Got it. I'm a dork. I had an old version outside of the contrib directory. Deleted it and boom, all is good.

  • Status changed to Closed: won't fix over 1 year ago
  • πŸ‡ΊπŸ‡¦Ukraine aleevas

    @joshuautley Thank you that you've left your comments about your solution. It did save a lot of my time.

Production build 0.71.5 2024