Problem/Motivation

In Drupal 11.2.5, I ran the composer update for this theme. It changed the composer.json configuration for this theme to 1.12. I cleared cache entirely. I ran database updates. I verified with drush ev that 1.12 is being used. Everything in CLI and codebase points to 1.12 being used.

I am using a subtheme so I don't know if there is a separate process for updating a subtheme. If I switch to Civic as default, however, it still thinks it's 1.11.

When I open Drupal, there is a site warning that I need to update this theme to 1.12. On Available Updates page, it shows that 1.11 is installed and 1.12 needs to be installed.

Steps to reproduce

In a local dev. environment, install Drupal 11.2.5. First install Civic Theme 1.11, then create a subtheme. Enable the subtheme as default. Update to 1.12 using composer.

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

Comments

ronraney created an issue. See original summary.

ronraney’s picture

ronraney commented

Inspecting my subtheme info.yml file, I found this:

# Information added by Drupal.org packaging script on 2025-05-27
version: '1.11.0'
project: 'civictheme'
datestamp: 1748306509

I don't know how it was added. It may be part of the process of creating a subtheme.

By removing this section of code, it resolved the issue.

richardgaunt’s picture

richardgaunt commented
Related issues: +#3554124: CivicTheme 1.11 does not include its version number
richardgaunt’s picture

richardgaunt commented

Now I understand. I thought it was not present at all.

But it seems the packaging system for CivicTheme adds the packaging version information to every `.info.yml` and so when you create a sub-theme this carries across.

The fix would be to remove this version information from the civictheme_starter.info.yml file when sub-theme is generated.

richardgaunt’s picture

richardgaunt commented
Related issues: -#3554124: CivicTheme 1.11 does not include its version number
richardgaunt’s picture

richardgaunt commented

Added a PR which will filter out this information on creation of sub-theme.

https://github.com/civictheme/monorepo-drupal/pull/1445

Your manual fix (of removing it from your sub-theme) will suffice for your purposes. Thanks for creating the issue.

richardgaunt’s picture

richardgaunt commented
Status: Active » Needs review
fionamorrison23’s picture

fionamorrison23 commented
Assigned: Unassigned » cb
cb’s picture

cb
Location Sydney
commented
Assigned: cb » richardgaunt
Status: Needs review » Reviewed & tested by the community

Downloaded CivicTheme zip from DO.
Ran the script to create a new subtheme.
Confirmed presence of build info in the subtheme info.yml
Replaced the CivicTheme subtheme script with this one from this PR.
Ran the script to create a new subtheme.
Confirmed absense of build info in the subtheme info.yml
Perfect.

This looks good.

  • 5a35e1aa committed on 1.x 
    [#3554770] Added feature to remove drupal packaging information in...
richardgaunt’s picture

richardgaunt commented
Version: 1.12.0 » 1.x-dev
Issue tags: +civictheme-1.12.2
richardgaunt’s picture

richardgaunt commented
Version: 1.x-dev » 1.12.2
Status: Reviewed & tested by the community » Fixed

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.

Status: Fixed » Closed (fixed)

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