Would it be possible to include as much detail as possible on releases?

i.e. in the form...

Contributors (n)
...

Changelog
Issues: n issues resolved.

Changes since 8.x-1.16 (compare):

Bug
[#xxxxxxx] feat: ...

Task
[#xxxxxxx] feat: ...
[#xxxxxxx] feat: ...

Comments

sirclickalot created an issue. See original summary.

sjpagan’s picture

sjpagan commented

Thanks for opening this feature request.

Your request is specifically about improving the level of detail provided in release information, including changelog structure, resolved issues, contributor visibility, and clearer version-to-version comparisons.

This is a valid and useful documentation improvement, and I prefer to keep it separate from the ongoing frontend asset cleanup work.

In parallel, I am working on Stylelint/ESLint and build validation improvements to make the module cleaner and fully compliant with automated validation workflows. However, this effort is not the direct subject of this issue.

I will track release documentation improvements separately from linting and build pipeline work to keep the issue queue clear and consistent.

I will close this issue once I have a clean build pipeline with no validation errors.

sjpagan’s picture

sjpagan commented
Assigned: Unassigned » sjpagan
sjpagan’s picture

sjpagan commented
Status: Active » Fixed

This issue has been fixed and included in the 1.0.4 release.

The problem related to code quality validation and CI pipeline has been resolved, ensuring full compliance with Drupal coding standards.

Special thanks to @sirclickalot for identifying and reporting this issue.

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.