Grimoirelab: 1.8.0 Release

Release date:
November 13, 2024
Previous version:
Could not determine previous release version
Magnitude:
0 Diff Delta
Contributors:
0 total committers
Data confidence:
Commits:

Top Contributors in 1.8.0

Could not determine top contributors for this release.

Directory Browser for 1.8.0

We couldn't find a release before this one

Release Notes Published

GrimoireLab 1.8.0

The following list describes the changes by component:

## grimoirelab-toolkit 1.0.7 - (2024-11-13)

  • Update Poetry's package dependencies

    kidash 1.0.8 - (2024-11-13)

  • Update Poetry's package dependencies

    sortinghat 1.5.1 - (2024-11-13)

  • Update Poetry's package dependencies

    cereslib 1.0.7 - (2024-11-13)

  • Update Poetry's package dependencies

## perceval 1.0.9 - (2024-11-13)

  • Update Poetry's package dependencies ## perceval-mozilla 1.0.9 - (2024-11-13)

Bug fixes:

  • Kitsune resuming feature fixed (#79)\ Kitsune backend resuming feature was broken. It didn't retrieve the updated questions right using the parameter 'offset'. Changing the backend to use 'from-date' parameter instead has fixed the problem.

## perceval-opnfv 1.0.9 - (2024-11-13)

  • Update Poetry's package dependencies

    perceval-puppet 1.0.9 - (2024-11-13)

  • Update Poetry's package dependencies

    perceval-weblate 1.0.9 - (2024-11-13)

  • Update Poetry's package dependencies

    graal 1.1.0 - (2024-11-13)

New features:

  • Compatible namespace package for Python 3.12\ Remove old format to define namespace packages. And use native namespace packages that requires removing the __init__.py file. It is important that every distribution that uses the namespace package omits that file. For more information see https://peps.python.org/pep-0420/

## grimoire-elk 1.3.1 - (2024-11-13)

  • Update Poetry's package dependencies ## sirmordred 1.1.3 - (2024-11-13)

Bug fixes:

  • Panels import bug and Micro Mordred failure\ A bug was causing Panels to fail to import in Kibiter and preventing micro Mordred from working. The issue was in tasks that didn’t require a SortingHat client to run.